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"

(New page: == Aperi requirements planning - Roadmap development == A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap. === Timeline: === ...)
 
Line 1: Line 1:
 
== Aperi requirements planning - Roadmap development ==
 
== Aperi requirements planning - Roadmap development ==
 
A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap.   
 
A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap.   
 
+
<big>
 
=== Timeline: ===
 
=== Timeline: ===
 
* 8/6: Announce that we are starting work on a new roadmap (aperi-dev, aperi-news).   
 
* 8/6: Announce that we are starting work on a new roadmap (aperi-dev, aperi-news).   
Line 26: Line 26:
  
 
Current Aperi Roadmap:
 
Current Aperi Roadmap:
 +
</big>

Revision as of 16:25, 15 August 2007

Aperi requirements planning - Roadmap development

A draft high level 'process' and timeline for obtaining requirements and developing an updated Aperi roadmap.

Timeline:

  • 8/6: Announce that we are starting work on a new roadmap (aperi-dev, aperi-news).
  • 8/13: Include draft 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:

Back to the top