Identify and manage risks
Define phases and milestones
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, by the project team, and by the
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.
|
Define number, length and objectives for iterations
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; in later iterations, goals are more focused on functional completion and
quality.
|
Validate staffing of the project
The Project Manager needs to ensure that the right team is in place. That means:
-
There are enough people on the team,
-
The people have all the necessary skills.
If the right people are not available, the project manager needs to change this by hiring people,
requesting reassignments, by training people that are available, or by adapting the scope or duration to fit the
available personnel.
|
Prioritize work
|