pines:feature_request_procedure
Differences
This shows you the differences between two versions of the page.
pines:feature_request_procedure [2007/04/09 14:56] – created phasefx | pines:feature_request_procedure [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | <meta http-equiv=" | ||
+ | < | ||
+ | </ | ||
+ | <body revision=' | ||
+ | <p align=center class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | Procedure</ | ||
+ | </p> | ||
+ | <p align=center class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | progresses towards the Beta and Production releases, the need for a formal | ||
+ | feature request process has become evident. The purpose of the Evergreen | ||
+ | Feature Request Procedure is to streamline this process, and to provide a | ||
+ | clear and equitable route for any additions to, or suggestions relative to, | ||
+ | the Evergreen software. It is paramount that each feature request is judged | ||
+ | fairly on its relative merits and priority, by both the Evergreen Software | ||
+ | Development Team and the PINES Subcommittees.</ | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | |||
+ | <font face=" | ||
+ | Software Development Team and the PINES Subcommittees to determine < | ||
+ | and < | ||
+ | software. </ | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | |||
+ | </p> | ||
+ | <ol> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | do not currently exist on the Evergreen development road map shall be | ||
+ | submitted to:</ | ||
+ | </p> | ||
+ | </li> | ||
+ | </ol> | ||
+ | <p class=western style=" | ||
+ | <font face=" | ||
+ | </ | ||
+ | |||
+ | </ | ||
+ | </p> | ||
+ | <p class=western style=" | ||
+ | <font face=" | ||
+ | </p> | ||
+ | <p class=western style=" | ||
+ | <font face=" | ||
+ | </ | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | |||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <ol start=2> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | accompanied by two sets of information:</ | ||
+ | </p> | ||
+ | </li> | ||
+ | |||
+ | </ol> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <ul> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | target audience of the requested feature. The type of the audience will be | ||
+ | one of < | ||
+ | < | ||
+ | of the number of users that the feature will directly serve or a | ||
+ | percentage of the audience type that the feature will directly serve. | ||
+ | These estimates will be vetted by both the Evergreen Software Development | ||
+ | Team and the PINES subcommittees.</ | ||
+ | |||
+ | </p> | ||
+ | </li> | ||
+ | </ul> | ||
+ | <p class=western style=" | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=" | ||
+ | <br> | ||
+ | </p> | ||
+ | <ul> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | |||
+ | <font face=" | ||
+ | </ | ||
+ | success of the feature request process. Without realistic use cases, the | ||
+ | development team will be unable to design a useful and integrated process | ||
+ | around the request, and the PINES Subcommittees will be unable to | ||
+ | determine the true merit and priority of the request. This also allows the | ||
+ | requesters to evaluate their requests, and can help them to add their own | ||
+ | view of the priority of the feature request.</ | ||
+ | </p> | ||
+ | </li> | ||
+ | </ul> | ||
+ | <p class=western style=" | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=" | ||
+ | <br> | ||
+ | |||
+ | </p> | ||
+ | <ol start=3> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | Team will evaluate each request, in the order received, to determine if | ||
+ | the use cases are already covered by an existing feature and to determine | ||
+ | the software development costs. If the Evergreen Software Development Team | ||
+ | believes the feature is already covered by existing functionality in the | ||
+ | software, the original requester will be contacted to explain that the | ||
+ | feature is believed to be implemented in an alternative fashion and to | ||
+ | confirm that the alternate implementation does indeed cover the requested | ||
+ | feature. Also, if the Evergreen Software Development team does not have | ||
+ | enough information to make a determination regarding the development cost | ||
+ | or priority of the requested feature, they will attempt to solicit enough | ||
+ | information from the requester to make such a determination. If the | ||
+ | software development team believes the request is minor, easily | ||
+ | incorporated, | ||
+ | will simply be inserted into the appropriate position in the development | ||
+ | timeline. </ | ||
+ | </p> | ||
+ | </li> | ||
+ | </ol> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | |||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <ol start=4> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | Development Team has evaluated the feature request, it will be sent to the | ||
+ | PINES subcommittees for evaluation. Along with the original feature | ||
+ | request, the development team will supply a summary of the technical | ||
+ | evaluation including the development team's estimation of the development | ||
+ | cost of the requested feature and any further comments the development | ||
+ | team may have.</ | ||
+ | </p> | ||
+ | </li> | ||
+ | |||
+ | </ol> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <ol start=5> | ||
+ | <li> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | consultation with the PINES staff and Evergreen Software Development Team, | ||
+ | will then determine, by discussion, vote, or acceptable alternative means, | ||
+ | the relative usefulness and priority of the request feature. If the | ||
+ | feature request is determined to require extra funds to complete, a budget | ||
+ | estimate and request will be sent by the Evergreen Software Development | ||
+ | Team to the PINES Program Director. If the feature request is accepted, | ||
+ | and the needed funds are available and approved, the Evergreen Software | ||
+ | Development Team will insert the feature into the appropriate position in | ||
+ | the software development timeline. </ | ||
+ | |||
+ | </p> | ||
+ | </li> | ||
+ | </ol> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <br> | ||
+ | </p> | ||
+ | <p class=western style=MARGIN-BOTTOM: | ||
+ | <font face=" | ||
+ | followed by all interested parties, will not only streamline the process of | ||
+ | accepting and prioritizing feature requests, but will help to provide clear | ||
+ | and easily understood reasoning behind the relative prioritization, | ||
+ | any misunderstandings surrounding the implementation, | ||
+ | later release, if applicable, of all features that users would like to | ||
+ | propose.</ | ||
+ | |||
+ | </ | ||
+ | </ |