The objective of defining the project phases and milestones is to define the project's important stages, not to detail
how it will reach them. This plan can then be used as a roadmap by the project manager, project team, and stakeholders.
For each phase, the project manager needs to define its start and end dates, its objectives and its milestones. The end
of each phase usually corresponds to a milestone, but the project manager can decide also to have intermediary
milestones, during long phases for example.When the lengths of the phases are determined, the project manager will need
to define the length, number, and objectives of the phase iterations.
Each iteration produces an actionable result (e.g. executable subsystem) that is used to assess progress and quality.
Because each iteration has a different focus, the functionality and completeness of the iteration deliverable will
vary. Iteration goals must be specific enough to be assessed at the end of the iteration. Goals in early iterations
usually focus on risk mitigation and architectural concerns; in later iterations, goals are more focused on functional
completion and quality.
Milestones are used for evaluating if the goals were achieved by the project team. Therefore goals need to be
prioritized and balanced with stakeholders to be in line with the milestone, project plan and work item list.
|