Artifacts > Project Management Artifact Set > Status Assessment > rup_stass.htm
<Project Name>
Status Assessment
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
Date |
Version |
Description |
Author |
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms and Abbreviations
6. Total Project/Product Scope
7. Action Items and Follow-Through
9. Process Improvement Opportunities
Status Assessment
[The introduction of the Status Assessment should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Status Assessment.]
[Specify the purpose of this Status Assessment.]
[A brief description of the scope of this Status Assessment; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Status Assessment. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Status Assessment. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Status Assessment contains and explain how the document is organized.]
[Status of personnel. Report any issues or concerns.]
[Current costs and revenue compared to the plan.]
[Report the status of the top 10-risks.]
[Report technical progress using metrics snapshots, etc.]
[Report the status of project milestones to date.]
[Report status of project or product scope.]
[A list of action items, rework required, and their current status.]
[For example, changes in requirements, new user's needs, and competitor's plan.]
[A list of process improvement actions suggested by the project team.]