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 4: | Line 4: | ||
=== Process: === | === Process: === | ||
| − | # | + | # Announce the start of requirements gathering with the intent to update the [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Aperi Technical Road Map]. Announcement should happen at Development, Architecture and Community meetings as well as posted to aperi-dev and aperi-news. |
| − | # | + | # Review the process to gather requirements with the community and make appropriate updates to the process. |
# Requirements gathering | # Requirements gathering | ||
| − | ## Review the following artifacts | + | ## Review the following artifacts with the community in order to understand our current backlog: |
##* [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Existing roadmap], | ##* [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Existing roadmap], | ||
| − | ##* Current release | + | ##* [http://wiki.eclipse.org/Release_Planning Current release line items] |
| − | ##* Carry over line items from the previous release | + | ##* [http://wiki.eclipse.org/Release_Planning Carry over line items from the previous release] |
| − | ##* [http:// | + | ##* [http://wiki.eclipse.org/Release_Planning Enhancement Bugzillas] |
##* Other items | ##* Other items | ||
| − | ## Solicit requests for new requirements that are not on the list | + | ## Solicit requests for [http://www.eclipse.org/aperi/ new requirements] that are not on the list |
# Requirements Prioritization | # Requirements Prioritization | ||
## Assign a priority value to each requirement (High, Medium, Low) | ## Assign a priority value to each requirement (High, Medium, Low) | ||
## Organize the requirement list by priority | ## Organize the requirement list by priority | ||
| − | # | + | # Assign resource for higher priority items |
| − | # Obtain | + | #* May need to re-prioritize items if resource is not secured |
| + | # Obtain time frame for completion of higher priority items | ||
# Map line items across time in road map | # Map line items across time in road map | ||
| − | # Obtain final agreement from team on | + | # Obtain final agreement from team on road map |
* Requirements management - Use Bugzilla to collect, prioritize and track requirements. | * Requirements management - Use Bugzilla to collect, prioritize and track requirements. | ||
Revision as of 17:21, 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:
- Announce the start of requirements gathering with the intent to update the Aperi Technical Road Map. Announcement should happen at Development, Architecture and Community meetings as well as posted to aperi-dev and aperi-news.
- Review the process to gather requirements with the community and make appropriate updates to the process.
- Requirements gathering
- Review the following artifacts with the community in order to understand our current backlog:
- Solicit requests for new requirements that are not on the list
- Requirements Prioritization
- Assign a priority value to each requirement (High, Medium, Low)
- Organize the requirement list by priority
- Assign resource for higher priority items
- May need to re-prioritize items if resource is not secured
- Obtain time frame for completion of higher priority items
- Map line items across time in road map
- Obtain final agreement from team on road map
- Requirements management - Use Bugzilla to collect, prioritize and track requirements.
- Process management - Use Aperi wiki for process, schedule, minutes, static items, Bugzilla reports
- Team communication - Execute requirements / road map process via community meetings/minutes and use aperi-news as communication vehicle in-between meetings
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: