This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Align Plans

This scenario involves aligning what (requirement) with 'when' (plan). It includes the alignment of requirements with development and test efforts.


  1. Team agrees to the iteration/project goals.
  2. Team agrees to iteration/project length.
  3. Prioritized requirements are reviewed by the team to ensure joint understanding.
  4. Requirements are sized for implementation effort.
  5. Requirements are sized for test effort.
  6. The team agrees to a subset of the requirements and adds them to the plan.
    1. Development plan links to requirements
    2. Test plan links to requirements
  7. Look for existing assets to consume / use.
  8. The development team creates tasks required to implement
  9. The test team creates a test plan, test suite/cases required to test.
  10. Consolidated plan forms the basis for the iteration / project.


  • Requirements are captured & prioritized
  • Process is decided
  • A plan is in place with full requirements coverage by development & test.


-- CarolynPampino - 21 Jan 2009

Topic revision: r2 - 01 Sep 2009 - 20:01:01 - SteveSpeicher
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback