Summary

:
Summary of the iterative project planning
When in the project the project manager and his staff does not knows about the full features of
the project then the traditional approach will not work the iterative planning will work in these
conditions.
Iterative project planning is useful when the uncertainty is high, and the risk to shipping all
requested features at the requested ship date is high. The iterative planning and scheduling
technique provides:
• sense of urgency for the development team.
• The ability to plan and adapt the critical path for the gradual unfolding of knowledge
about the project.
• planned preplanning effort. !ost projects replane , this technique sets the
e"pectations that the preplanning will occur.
• #se of the critical path to define priorities and motivate and inform the staff to the
realities of the project.
Initially fi"ing the milestones but not the tasks allows for studiously and continuously shifting
the critical path to make the most progress in a project. Then, even if the original dates are
based on nothing but senior management$s wishes, the project manager can use a rational
approach to plan and manage the project.
Background
The project management is required to manage and include the features it is
activity of bringing all the participant to complete the product .Iterative planning and the
tracking is used to avoid to choose between the reducing the number of the features or
e"tending the schedule.
Introduction
Iterative project planning is useful when the uncertainty is high, and the risk to
shipping all requested features at the requested ship date is high. The iterative planning and
scheduling technique provides:
• sense of urgency for the development team.
• The ability to plan and adapt the critical path for the gradual unfolding of knowledge
about the project.
• planned preplanning effort. !ost projects replan , this technique sets the e"pectations
that the replanning will occur.
• #se of the critical path to define priorities and motivate and inform the staff to the
realities of the project.
Initially fi"ing the milestones but not the tasks allows for studiously and continuously shifting
the critical path to make the most progress in a project. Then, even if the original dates are
based on nothing but senior management$s wishes, the project manager can use a rational
approach to plan and manage the project.
Iterative planning
It is used when the knowledge of the product or the project is
imperfect it allows a company to get the started working on the project when only major issues
are understood .This is used for developing a number of small independent features and
frequent replanning.
Initial project planning
The senior management frequently fi"es the ship dates without
having the good knowledge of the features to be produced .This is the not good habit but the
commercial companies have significant market forces which prevent them understanding the
what they are requesting from the developers.
Critical path
Their are multiple critical path in the project the most important part of the
critical path are as under
 Task %are event that are planned &
 'eoples %number of the peoples that are hired to work on the project&
 (esources%machines, net work etc&
In the project where the project manager and technical staff do not have enough knowledge
the traditional approach will not work in these types of cases here the iterative approach
will be useful. the traditional approach will not guaranteed the success. When the
knowledge about the project is imperfect then an iterative approach will be helpful. In the
following ways
• 'lan the major miles stones %feature free)e code free)e beta ship etc&
• 'lan each segment of the project as it crystalli)es
• When the segment completed the technical staff will understood about the
project.
The comple" project functionality may be grouped as that part of the product is ready for code
free)e
!ilestones planning and criteria
The effective manager and software engineers
* requirement planning
+ feature definition
, design and implementation
-erification and validation
In the iteratively planned project the team should knows about each milestone if the team does
not understand the milestones the project will not be successful. The project manager planned
the milestones.
Iterative software project planning is valuable when the improbability is high, and the risk to
distribution all requested features at the requested distribute date is high. The iterative software
planning and scheduling technique provides:
 sense of urgency for the development team.
 The planned re planning effort. !ost projects re plan, this technique sets the
e"pectations that the re.planning will occur.
 'lan and adapt the critical path for the gradual relating of knowledge about the project.
 #se of the critical path to define priorities and motivate and inform the staff to the
realities of the project.
Initially fi"ing the milestones but not the tasks allows for studiously and continuously shifting
the critical path to make the most progress in a project. Then, even if the original dates are
based on nothing but senior management$s wishes, the project manager can use a rational
approach to plan and manage the project.
Real World Example Of Project Planning and Tracking:-
Machine i!ion Product Example:
/ontrast these product criteria with a machine vision product in its mainstream phase:
Shipment "riteria:
 ll system tests e"ecuted %012 percent passed&.
 3uccessful e"ecution of any 45etting 3tarted4 sequence.
 (esults of e"ecuted tests must be discussed with product management team.
 3uccessful generation of e"ecutable images for all appropriate platforms.
 /ode is completely fro)en.
 6ocumentation review is complete.
 There are )ero showstopper bugs.
 There are fewer than four major bugs, and *7 minor bugs.
These defect.focused criteria %especially numbers 8 and 9& are focused on defects as a primary
definition of quality. These numbers were chosen based on previous product releases, and the
assumption that the severity of each the e"isting defects would be assessed. The ship date is
still important, otherwise the defect levels would be lower and system test pass results would
be higher.