Prioritize work
Define the iteration goals
Near the end of the current iteration, the Project Manager starts defining the goals of the next iteration.
These goals are usually based on the following factors:
-
Critical risks not yet mitigated: Iteration goals often include driving down the
most critical risks.
-
The time allocated to the iteration: Iterations are usually timeboxed, so the Project Manager
must ensure that the work planned for the iteration will fit the time and the resources allocated to the
iteration.
-
The features required: requirements are prioritized to ensure that the critical features of
the application will be developed, and tested, early on.
This scope is usually defined in terms of scenarios that need to be implemented and tested during the iteration.
|
Allocate work items to iteration
When detailing the plan for the next iteration, the Project Manager identifies the work items from the Work Items List to be addressed in the next iteration.
|
Identify system elements to be tested
As every iteration includes testing, the Project Manager will need also to identify what will be tested, and to what
extent, during the iteration.
Tested elements can include:
-
scenarios developed during the iteration
-
change requests implemented during the iteration
-
a critical interface with an external system
-
supplemental requirements, such as loading, response time, and so on.
|
|