Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Requirements Process"
| Line 1: | Line 1: | ||
| − | == Aperi requirements planning - | + | == Aperi requirements planning - Road map development == |
| − | A draft high level 'process' and | + | A draft high level 'process' and time line for obtaining requirements and developing an updated Aperi road map. Per our [http://wiki.eclipse.org/Voting_Process Voting Process], we are required to vote on road map changes. |
<big> | <big> | ||
| + | |||
| + | === Process: === | ||
| + | # Project Lead will announce that we will start to gather requirements and work to update the [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Aperi Technical road map]. This announcement will be done at Development, Architecture and Community meetings as well as posted to aperi-dev and aperi-news. | ||
| + | # At a community meeting, the Project Lead will review the process to gather requirements and make the appropriate updates. | ||
| + | # Requirements gathering - Review the existing roadmap, review the list At a community meeting | ||
| + | ** Propose process for building the roadmap and gain consensus | ||
| + | ** Requirements collection | ||
| + | ** Use of Bugzilla to enter requirements - instructions on how to use | ||
| + | ** Use of aperi-news as communication vehicle during process | ||
| + | ** Use of wiki as placeholder for process, schedule, minutes, static items, Bugzilla reports | ||
| + | ** Prioritization process | ||
| + | ** Schedule | ||
| + | * 8/17-29: Collect requirements | ||
| + | * 8/27-29: Remind team members to provide input | ||
| + | * 8/30: Community Meeting - Review received requirements with community and rank/prioritize | ||
| + | * 8/31:Send out prioritized list | ||
| + | * 8/31 - 9/5: Review prioritized list, collect new requirements | ||
| + | * 9/6: Community Meeting - Review prioritized list, discuss timing, lay out on new roadmap | ||
| + | * 9/7: Send out roadmap draft | ||
| + | * 9/8-19: Roadmap review, discussion on communication vehicle, roadmap revisions (on wiki) | ||
| + | * 9/20: Community Meeting - Obtain consensus on roadmap and gain approval. | ||
| + | |||
=== Timeline: === | === Timeline: === | ||
* 8/6: Announce that we are starting work on a new roadmap. | * 8/6: Announce that we are starting work on a new roadmap. | ||
Revision as of 16:39, 15 August 2007
Aperi requirements planning - Road map development
A draft high level 'process' and time line for obtaining requirements and developing an updated Aperi road map. Per our Voting Process, we are required to vote on road map changes.
Process:
- Project Lead will announce that we will start to gather requirements and work to update the Aperi Technical road map. This announcement will be done at Development, Architecture and Community meetings as well as posted to aperi-dev and aperi-news.
- At a community meeting, the Project Lead will review the process to gather requirements and make the appropriate updates.
- Requirements gathering - Review the existing roadmap, review the list At a community meeting
- Propose process for building the roadmap and gain consensus
- Requirements collection
- Use of Bugzilla to enter requirements - instructions on how to use
- Use of aperi-news as communication vehicle during process
- Use of wiki as placeholder for process, schedule, minutes, static items, Bugzilla reports
- Prioritization process
- Schedule
- 8/17-29: Collect requirements
- 8/27-29: Remind team members to provide input
- 8/30: Community Meeting - Review received requirements with community and rank/prioritize
- 8/31:Send out prioritized list
- 8/31 - 9/5: Review prioritized list, collect new requirements
- 9/6: Community Meeting - Review prioritized list, discuss timing, lay out on new roadmap
- 9/7: Send out roadmap draft
- 9/8-19: Roadmap review, discussion on communication vehicle, roadmap revisions (on wiki)
- 9/20: Community Meeting - Obtain consensus on roadmap and gain approval.
Timeline:
- 8/6: Announce that we are starting work on a new roadmap.
- 8/13: Include requirements process in Community Meeting agenda
- 8/16: Community Meeting
- Propose process for building the roadmap and gain consensus
- Requirements collection
- Use of Bugzilla to enter requirements - instructions on how to use
- Use of aperi-news as communication vehicle during process
- Use of wiki as placeholder for process, schedule, minutes, static items, Bugzilla reports
- Prioritization process
- Schedule
- 8/17-29: Collect requirements
- 8/27-29: Remind team members to provide input
- 8/30: Community Meeting - Review received requirements with community and rank/prioritize
- 8/31:Send out prioritized list
- 8/31 - 9/5: Review prioritized list, collect new requirements
- 9/6: Community Meeting - Review prioritized list, discuss timing, lay out on new roadmap
- 9/7: Send out roadmap draft
- 9/8-19: Roadmap review, discussion on communication vehicle, roadmap revisions (on wiki)
- 9/20: Community Meeting - Obtain consensus on roadmap and gain approval.
Aperi community meetings: 8/16, 8/30, 9/6, 9/20, 10/4
Current Aperi Roadmap: