Overview

Performed as near to the end of a stage as possible, the End Stage Report is prepared by the Project Manager for the Project Board. It is done as a precursor to presenting the next Stage Plan.

This process should include:

• Comparing results with agreed Tolerances
• An assessment of overall risk and ability to meet the objectives of the Business Case
• A review of the quality control activities
• An audit of the Configuration Item Record
• Updating the Lessons Learned Log
• Reviewing the Communications Plan.

Although the Project Manager controls the overall creation of the End Stage Report they are assisted by the Project Support and the Configuration Librarian (for the Configuration Audit). An informal agreement should be sought from Project Assurance that the reported data and conclusions are correct.

Method links

Tips

• At each 'Reporting Stage End' confirm that each product has been:
  • Produced
  • Quality checked
  • Accepted by the Customer if completed.
• Where appropriate update the Lessons Learned Log with any:
  • Changes to be carried through to the next stage
  • Degree of risk management required when going further
  • Omissions, strengths or weaknesses of standards used.
  • Discrepancies on the Configuration Item Records.
• If triggered by an Exception Report include details about what triggered the Exception Plan.

Notes

• Occurs when a stage is nearing an end or an Exception Plan is created
• Present to the Project Board with the original Stage Plan and a summary of the Issue Log.

Case studies and examples

Related links

• Search our forum for 'SB5 Reporting Stage End'
• Take our SB - Managing Stage Boundaries - Quiz
• Exception Plan.