Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Requirements Process"

 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== 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 [http://wiki.eclipse.org/Voting_Process Voting Process], we are required to vote on road map changes.   
 
 
<big>
 
<big>
 +
== Aperi Requirements Process ==
 +
This is a process 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.  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: ===
 
=== 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.
+
# 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.
−
# At a community meeting, the Project Lead will review the process to gather requirements and make the appropriate updates.       
+
# Review the process to gather requirements with the community and make appropriate updates to the process.       
−
# Requirements gathering - Review the existing roadmap, review the list At a community meeting
+
# Requirements gathering
−
** Propose process for building the roadmap and gain consensus 
+
## Review the following artifacts with the community in order to understand our current backlog:
−
** Requirements collection
+
##* [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Existing roadmap],
−
** Use of Bugzilla to enter requirements - instructions on how to use
+
##* [http://wiki.eclipse.org/Release_Planning Current release line items]
−
** Use of aperi-news as communication vehicle during process 
+
##* [http://wiki.eclipse.org/Release_Planning Carry over line items from the previous release]
−
** Use of wiki as placeholder for process, schedule, minutes, static items, Bugzilla reports
+
##* [http://wiki.eclipse.org/Release_Planning Enhancement Bugzillas]
−
** Prioritization process
+
##* Other items
−
** Schedule
+
## Solicit requests for [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Aperi&bug_severity=enhancement new requirements] that are not on the list
−
* 8/17-29: Collect requirements
+
# Requirements Prioritization
−
* 8/27-29: Remind team members to provide input
+
## Assign a priority value to each requirement (High, Medium, Low)
−
* 8/30: Community Meeting - Review received requirements with community and rank/prioritize
+
##* Use ''Priority'' field in Bugzilla?  (P1-P5, P1 being the highest priority)
−
* 8/31:Send out prioritized list
+
##** Checking with Eclipse to see if feasible   
−
* 8/31 - 9/5: Review prioritized list, collect new requirements
+
## Organize the requirement list by priority
−
* 9/6: Community Meeting - Review prioritized list, discuss timing, lay out on new roadmap
+
# Assign resource for higher priority items
−
* 9/7: Send out roadmap draft
+
#* May need to re-prioritize items if resource is not secured
−
* 9/8-19: Roadmap review, discussion on communication vehicle, roadmap revisions (on wiki)  
+
# Obtain time frame for completion of higher priority items
−
* 9/20: Community Meeting - Obtain consensus on roadmap and gain approval.
+
# Map line items across time in road map
 +
# Obtain final agreement from team on road map
  
−
=== 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
+
=== 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 
  
  
−
Current Aperi Roadmap:
+
=== Reference info: ===
 +
* [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Current Aperi Road Map]
 +
* [http://wiki.eclipse.org/Road_map_update_timeline timeline to update road map]
 +
* Requirements process for other Eclipse projects:
 +
** [http://wiki.eclipse.org/ALF/Requirements_Management ALF]
 +
** [http://wiki.eclipse.org/index.php/WTP_Requirements_Main WTP]
 +
** [http://www.eclipse.org/tptp/home/project_info/devplans/Eclipse%20TPTP%20Project%204.4%20Release%20Planning%20Process.htm TPTP Planning Process]
 +
** Several projects had ''Requirements Councils'' (e.g.,DTP), but specific documented processes could not be found
 
</big>
 
</big>

Latest revision as of 12:49, 24 August 2007

Aperi Requirements Process

This is a process 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:
    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


Reference info:

Retrieved from "https://wiki.eclipse.org/index.php?title=Requirements_Process&oldid=47801"

This page was last modified 12:49, 24 August 2007 by Tom Guinane.

Back to the top