Artifacts >
Project Management Artifact Set >
Status Assessment
Artifact:
|
![]() Status Assessment |
One of the objectives of the process is to ensure that the expectations of all parties are synchronized and consistent. The periodic status assessment provides a mechanism for managing everyone's expectations throughout the lifecycle. |
Role: | Project Manager |
Template: | |
Examples: | |
|
Input to Activities: | Output from Activities: |
Status assessments provide a mechanism for addressing, communicating, and resolving management issues, technical issues, and project risks. Continuous open communication with objective data derived directly from ongoing activities, and the evolving product configurations are mandatory in any project. These project snapshots provide the heartbeat for management attention. While the period may vary, the forcing function needs to capture the project history.
Note that status assessments are different from milestone reviews.
(hyperlinks into HTML template in a new window)
Created periodically, typically at the end of an iteration, sometimes more often for very large projects where iterations last several months.
Not maintained or updated.
A project manager is responsible for the status assessment.
The Status Assessment may be combined with the Iteration Assessment if the iterations are frequent (one each month). If iterations are lengthy, there will be a need for intermediate Status Assessments.
A lot of the information in the status assessment is copied from other
sources, to provide a comprehensive source of information for the people
assessing the project. Because the status assessment is not maintained, there is
no concern about keeping the information consistent with the evolving system.
Rational Unified
Process
|