Loading

 

2.1.6.2 Iteration Plan

The iteration plan is a fine-grained plan with a time-sequenced set of activities and tasks, with assigned resources, containing task dependencies, for the iteration.

There are typically two iteration plans active at any point in time.

  • The current iteration plan is used to track progress in the current iteration.
  • The next iteration plan is used to plan the upcoming iteration. This plan is prepared toward the end of the current iteration.

2.1.6.2.1 Inception Phase Iteration Plan - Completed before the Phase I NIH Grant Funding

2.1.6.2.2 Elaboration Phase Iteration Plan - Completed with NIH Phase I Funding

2.1.6.2.3 Construction Phase Iteration Plan

2.1.6.2.4 Transition Phase

To define the contents of an iteration you need:

  • the project plan
  • the current status of the project (on track, late, large number of problems, requirements creep, etc.)
  • a list of scenarios or use cases that must be completed by the end of the iteration
  • a list of risks that must be addressed by the end of the iteration
  • a list of changes that must be incorporated in the product (bug fixes, changes in requirements)
  • a list of major classes or packages that must be completely implemented

These lists must be ranked. The objectives of an iteration should be aggressive so that when difficulties arise, items can be dropped from the iterations based on their ranks.

Therefore there is a set of supported work products (deliverables)  that help in measuring and building each iteration plan.

Work Products (deliverable with which time spent will be reported?) are:

  • The Iteration Assessment captures the result of an iteration, the degree to which the evaluation criteria were met, lessons learned, and changes to be done.
  • The project measurements is the project's active repository of metrics data. It contains the most current project, resources, process, and product measurements at the primitive and derived level.
  • The periodic Status Assessment provides a mechanism for managing everyone's expectations throughout the project lifecycle to ensure that the expectations of all parties are synchronized and consistent.
  • The work order is the Project Manager's means of communicating with the staff about what is to be done and when it is to be completed.