Having derived the project's progress and quality indicators, the project manager compares these against the expected
state of the project as defined by the Software Development Plan and Iteration Plans. At this point the project manager
will evaluate the following:
Have all planned tasks been completed?
Have all work products been published as planned?
Is the estimated effort to complete tasks that are "in progress" within plan?
Are quality metrics (e.g. open defect counts) within planned tolerances?
The project manager will also review the risk indicators identified for each risk on the Risk List to decide whether
any risk mitigation strategies should be activated at this time.
The project manager, in reviewing progress against the Iteration Plan, should always have in mind that an iteration is
timeboxed, and start to consider and report what functionality can be omitted from
an iteration, if it appears the original plan cannot be achieved, rather than reporting a schedule slip for the
Any issues that have been reported are captured on the project's Issues List (which will be reported in the Status Assessment). Issues that fall within the project manager's
authority should be resolved directly, as part of Task: Handle Exceptions and Problems; it may sometimes be necessary
to raise the profile of an issue, for example, by raising a Change Request to track it, or by updating the Risk List, if the issue is important, or of wider interest.
Issues arising that require escalation to the Project Review Authority are included in the Status Assessment and
forwarded to the PRA for resolution. Often this is done during the PRA Project Review task.