Database Reference
In-Depth Information
• Project health: Summary of the project's health status (e.g., Cost, Schedule,
Scope, resource); this is derived from the individual status reports submitted
by the team members to the team lead or project manager.
• Project Progress Assessments: narrative overview of project status including
accomplishments, future plans, and barriers to completion (e.g., the Executive
Summary).
• Issues: Summary of any issues that have been identified, are open, have been
resolved, or have been rejected.
• risks: Summary of any risks pertaining to the project(s).
• Change requests: Summary of any change requests that have been identified,
have been resolved or have been rejected.
• Deliverables: Summary of any deliverables that have been created, completed,
or removed from the scope of the project.
• milestones: Summary of any progress milestones, such as milestones descrip-
tion, milestone status, milestone due date, and milestones estimate to complete.
• Project metrics: Summary of any progress metrics, such as earned value, SPI,
CPI, and projected completion date, and effort specific metrics, such as hours
per program, lines of code, system down time, and fatal errors on development
projects (as applicable).
• Expense to budget report and graph with stoplight features:
• green is used when the project or key area is on track and in control
• yellow is used when the project or key area is not on track but in control
• red is used when the project or key area is not on track and not in control
11.7.12.2 Risks, Assumptions, Issues, and Dependencies (RAID) Log
It is standard fare to
keep an issues log during a project. The rAID log might seem like overkill in a small
project, but it is one of the key tools in managing critical issues. A rAID log records
the decisions made on the project, serves as a good reference when future decisions are
being considered, and is a source of information when the project is reviewed. typically,
issues arise in one or more of the following areas: budget, schedule, resources, or qual-
ity of work. In the rAID log (Figure 11.3), every issue must be dated, described, and
assigned to a person who has the responsibility for its resolution. At the end of the
Figure 11.3
Sample RAID log.
