Artifacts > Project Management Artifact Set > Iteration Plan


Iteration Plan

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

Role: Project Manager
More Information:

Input to Activities: Output from Activities:






Templates, Case-Study, Report.. To top of page

The Word template can be bought through a template package. Case studies and reports are freely available in the table below.

Word
Template
Case
Study
Report

   (Doc)
   (Gantt Diagrams)
---

Purpose To top of page

The following people use the Iteration Plan:

  • The project manager, to plan the iteration tasks and activities, to schedule resource needs, and to track progress against the schedule
  • Project team members, to understand what they need to do, when they need to do it, and what other activities they are dependent upon

Timing To top of page

The Iteration Plan for the upcoming iteration is planned in the current iteration. It is modified as needed during the iteration.

One Iteration Plan is input to the next Iteration Plan. An Iteration Plan is obsolete after the iteration.

Responsibility To top of page

The Project Manager is responsible for the integrity of the Iteration Plans.

Tailoring To top of page

The Iteration Plan needs to detail what is to be done in a fine-grained way, so that there is little room for fuzziness about the true position or responsibilities at any time. Usually some kind of project planning tool (such as Microsoft® Project) will be used.

Additional Information To top of page

This is a fine-grained plan for one iteration. There are often two such plans: one for the current iteration and one under construction for the next iteration.

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, and so on.)
  • 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.

Evaluation Criteria

Each iteration is concluded by an assessment. For this iteration assessment you assess the results of the iteration relative to the evaluation criteria that were established for the Iteration Plan.

The evaluation criteria are established prior to each iteration and establish goals for the feature set, quality, and performance to be achieved in the iteration. Actual achievement of these goals will vary. For example, on a given iteration, the feature set may be exceeded, quality barely achieved, and performance lacking.

Also, goals may be expressed as minimal and desirable goals. For example, there may be a required feature set and some desirable features that will be attempted in this iteration if the speed of development and staffing levels make it feasible.