Difference between revisions of "Requirements Process"

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. This process is intended to define outstanding requirements and line items, prioritize them, assign resources, arrange line items across time in the road map, and obtain agreement from the community.

Process:

1. 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.
2. Review the process to gather requirements with the community and make appropriate updates to the process.
3. Requirements gathering
   1. Review the following artifacts with the community in order to understand our current backlog:
      • Existing roadmap,
      • Current release line items
      • Carry over line items from the previous release
      • Enhancement Bugzillas
      • Other items
   2. Solicit requests for new requirements that are not on the list
4. Requirements Prioritization
   1. Assign a priority value to each requirement (High, Medium, Low)
      • Use Priority field in Bugzilla? (P1-P5, P1 being the highest priority)
        • Checking with Eclipse to see if feasible
   2. Organize the requirement list by priority
5. Assign resource for higher priority items
   • May need to re-prioritize items if resource is not secured
6. Obtain time frame for completion of higher priority items
7. Map line items across time in road map
8. Obtain final agreement from team on road map

Logistics:

• Requirements management - Use Bugzilla to collect, prioritize and track requirements.
• Process management - Use Aperi wiki to store process, project schedule, meeting minutes, static items, Bugzilla reports
• Team communication - Use community meetings and minutes as well as aperi-news as communication vehicle for this process

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
  • 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
  • Schedule
  • Requirements collection
• 8/17-29: Collect requirements
• 8/27-29: Remind team members to provide input
• 8/30: Community Meeting - Review received requirements with community, rank/prioritize, accept volunteers for items
• 8/31:Send out prioritized list
• 8/31 - 9/5: Review prioritized list, accept assignments, 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.

Reference info:

• Aperi community meetings: 8/16, 8/30, 9/6, 9/20, 10/4
• Current Aperi Road Map
• Other projects requirements processes:
  • ALF
  • WTP
  • TPTP Planning Process
  • Several projects had Requirements Councils (e.g.,DTP), but specific documented processes could not be found