Work Product (Artifact): Iteration Plan
var defaultQueryStr = '?proc={EA0C1D32-E39A-4D96-B956-E178DB776A96}&path={EA0C1D32-E39A-4D96-B956-E178DB776A96},{8040B743-6467-4067-8C0F-E62C3DE99414},_Cbh5Ehi2Edq_uI8xTPML6g';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);
Work Product (Artifact): Iteration Plan
This artifact is a time-sequenced set of activities and tasks, with assigned resources, containing task dependencies, for the iteration; a fine-grained plan.
Purpose
The following people use the Iteration Plan:
The project manager, to plan the iteration tasks, 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.
Relationships
RolesResponsible:
Project Manager
Modified By:
Project Manager
Input ToMandatory:
Iteration Plan Review
Optional:
None
External:
None
Output From
Develop Iteration Plan
Main Description
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 will be used. 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, 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.
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.
Properties
Optional
Planned
Illustrations
Templates
Iteration Plan (Informal)
Examples
CSPS Iteration Plan - Construction Phase
CSPS Iteration Plan - Elaboration Phase
CSPS Iteration Plan - Inception Phase
CSPS Iteration Plan - Transition Phase
Tailoring
Representation Options
More Information
Guidelines
Iteration Plan
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
contentPage.processPage.fixDescriptorLinks();
Wyszukiwarka
Podobne podstrony:
rup iteration assessment?108D56rup iteration planb3AFF7Frup iteration plan?42C99Erup iteration planu7AEFD1więcej podobnych podstron