Skip to main content

Notice: This Wiki is now read only and edits are no longer 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"

(New page: == Aperi requirements planning - Roadmap development == A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap. === Timeline: === ...)
 
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Aperi requirements planning - Roadmap development ==
+
<big>
−
A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap.  
+
== 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.    
  
−
=== Timeline: ===
+
=== Process: ===
−
* 8/6: Announce that we are starting work on a new roadmap (aperi-dev, 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.
−
* 8/13: Include draft requirements process in Community Meeting agenda
+
# Review the process to gather requirements with the community and make appropriate updates to the process.     
−
* 8/16: Community Meeting - Propose process for building the roadmap and gain consensus 
+
# Requirements gathering
−
** Requirements collection
+
## Review the following artifacts with the community in order to understand our current backlog:
−
** Use of Bugzilla to enter requirements - instructions on how to use
+
##* [http://wiki.eclipse.org/images/1/1f/AperiTechnicalRoadmap6.pdf Existing roadmap],
−
** Use of aperi-news as communication vehicle during process 
+
##* [http://wiki.eclipse.org/Release_Planning Current release line items]
−
** Use of wiki as placeholder for process, schedule, minutes, static items, Bugzilla reports
+
##* [http://wiki.eclipse.org/Release_Planning Carry over line items from the previous release]
−
** Prioritization process
+
##* [http://wiki.eclipse.org/Release_Planning Enhancement Bugzillas]
−
** Schedule
+
##* Other items
−
* 8/17-29: Collect requirements
+
## 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/27-29: Remind team members to provide input
+
# Requirements Prioritization
−
* 8/30: Community Meeting - Review received requirements with community and rank/prioritize
+
## Assign a priority value to each requirement (High, Medium, Low)
−
* 8/31:Send out prioritized list
+
##* Use ''Priority'' field in Bugzilla?  (P1-P5, P1 being the highest priority)
−
* 8/31 - 9/5: Review prioritized list, collect new requirements
+
##** Checking with Eclipse to see if feasible   
−
* 9/6: Community Meeting - Review prioritized list, discuss timing, lay out on new roadmap
+
## Organize the requirement list by priority
−
* 9/7: Send out roadmap draft
+
# Assign resource for higher priority items
−
* 9/8-19: Roadmap review, discussion on communication vehicle, roadmap revisions (on wiki)  
+
#* May need to re-prioritize items if resource is not secured
−
* 9/20: Community Meeting - Obtain consensus on roadmap and gain approval.
+
# 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
  
−
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>

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 Eclipsepedia anonymous user Unnamed Poltroon.

Back to the top