Iteration Plan Template
Iteration Plan Template
Note: A key feature of this document is its brevity. Use only the relevant parts. Provide just enough verbiage to keep
everyone focused on the objectives of the iteration. If this document is too large, it is possible that your iteration is
too ambitious.
Title Page
Contains the name of project, the words "Iteration Plan #", iteration plan number, date, and document
version number.
Abstract
A one-to-three paragraph summary of the problem solved by this project.
Document History
List the various revisions of this document along with a brief summary of they changes. It is often helpful
to state why the revisions were made if those revisions were for some other reason than accuracy or
refinement.
Approvals
Provide a signature block for each of the key stakeholders who have signatory approval for the project.
These roles are spelled out in the project charter.
Project Team
List project team members and their roles.
Table of Contents
Provide major headings and page numbers. The page footer should contain the page number ("Page x of
y,")
1.0 Introduction
State the purpose of this entire document in high-level terms.
1.1 Purpose
The completion of an iteration comprises some defined portion of a phase. The completion of a phase is a
milestone. Describe the contribution that this iteration provides toward the completion of the milestone.
1.2 Context
Provide a brief description of how this iteration plan fits into the overall project plan. You may refer to the
project plan, development case, or any other relevant artifacts. List the particular use cases that will be
addressed in this iteration.
2.0 Plan
State the basic goals for this iteration along with a summary of the start and end dates for this iteration. If a
GANTT or PERT chart is available, include it here.
Page 1 of 3
Analysis and Design
Implementation
Testing
Configuration and Change Management
Requirements
<Task1> <date> <date> <name >
<Task2> <date> <date> <name>
<Task n> <date> <date> <name>
Requirements
<Task1> <artifact1> <name>
<Task n> <artifact2> <name>
Page 2 of 3
3.0 Resource Summary
Provide a list of resources needed to complete this iteration. Resources include people, equipment,
facilities, software, etc. These resources should be confined to those people or things that are limited in
nature, or are unavailable at the time of writing of this iteration plan. For example, if a server is to be
installed during this iteration, you would not necessarily include it as a resource in the next iteration, unless
there is some problem with its availability or performance. This section is intended to be a management
tool, not an inventory.
Requirements
< Artifact1> <E.g., Document inspection using template.> <name>
Page 3 of 3