0% found this document useful (0 votes)
98 views3 pages

Iteration Plan Template

Uploaded by

Alia Diab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
98 views3 pages

Iteration Plan Template

Uploaded by

Alia Diab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Iteration Plan Document Format

COMP 413W Semester Project


Penn State Harrisburg Fall 2007

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.

2.1 Schedule of Iteration Workflows


A summary of the activities in each workflow participating in this iteration is given here. Any risks or
events that could cause slippage in the dates should be given here. Provide a breakdown tabular form,
listing only the workflows relevant to this iteration.

Workflow Start Date End Date Duration


(days)
Business Modeling
Requirements

Page 1 of 3
Analysis and Design
Implementation
Testing
Configuration and Change Management

Table 1 : Iteration Workflow Schedule

2.2 Iteration Schedule Breakdown


Provide a list of tasks for each workflow given in Table 1. A format for this list is given in Table 2. Note: If
you are using a project management tool such as Microsoft Project ®, you can export the information
provided in Table 2 below. Otherwise—especially if you keep your iterations short—you can just fill in the
information by hand.

Task Name Start Finish Assigned To


Business Modeling
<Task1> <date> <date> <name >
<Task2> <date> <date> <name>
<Task n> <date> <date> <name>

Requirements
<Task1> <date> <date> <name >
<Task2> <date> <date> <name>
<Task n> <date> <date> <name>

Analysis and Design


Etc. , etc… <date> <date> <name>

Table 2: Iteration Plan Task Breakdown by Workflow

2.3 Iteration Artifacts


Provide a description of the artifacts that are the deliverables that are affected by this iteration. You may
choose to include only those that are finished in this iteration, if you are "managing by deliverables." If you
are managing by tasks, you may include the deliverables within your tasks, and omit this section. (The
particular option chosen is usually determined by the project manager or the client.) If you have a large
number of artifacts, you may find it helpful to list them in tabular form as shown in Table 3 below. Again,
use only the parts that are relevant and correspond to the Workflow Breakdown

Task Name Deliverable Responsible


Business Modeling
<Task1> <artifact1> <name>
<Task2> <artifact2> <name>
<Task n> <artifact3> <name>

Requirements
<Task1> <artifact1> <name>
<Task n> <artifact2> <name>

Analysis and Design


Etc. , etc…

Table 3: Artifacts to be Delivered in this Iteration

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.

4.0 Quality Assurance


Describe the quality assurance strategy that will be applied to this iteration. Also include anything that is
exceptional, or outside the bounds of the detailed quality assurance activities specific to each artifact. (A component
of each artifact is its quality assurance activities.). An introductory paragraph, placed here, outlines the basic
approach to the testing. The paragraphs below should answer the question, "How will I know when each
artifact/deliverable is acceptable to the approving authority?" The column labeled "QA Strategy" reflects the QA
component of each deliverable.

Deliverable QA Strategy Responsible


Business Modeling
<artifact1> <E.g., Document walkthrough with client.> <name>
<artifact2> <name>
<artifact3> <name>

Requirements
< Artifact1> <E.g., Document inspection using template.> <name>

Analysis and Design


Etc. , etc… <E.g., Technical design walkthrough.> <name>

Page 3 of 3

You might also like