PRINCE2 Agile 2016
Previous Section   Next Section

A.11 Highlight report

A.11.1 Purpose

A highlight report is used to provide the project board (and possibly other stakeholders) with a summary of the stage status at intervals defined by them. The project board uses the report to monitor stage and project progress. The project manager also uses it to advise the project board of any potential problems or areas where the project board could help.

A.11.2 Composition

  • Date The date of the report
  • Period The reporting period covered by the highlight report
  • Status summary An overview of the status of the stage at this time
  • This reporting period:
    • Work packages – pending authorization, in execution, and completed in the period (if the work packages are being performed by external suppliers, this information may be accompanied by purchase order and invoicing data)
    • Products completed in the period
    • Products planned but not started or completed in the period (providing an early-warning indicator or potential breach of time tolerance)
    • Corrective actions taken during the period
  • Next reporting period:
    • Work packages – to be authorized, in execution, and to be completed during the next period (if the work packages are being performed by external suppliers, this information may be accompanied by purchase order and invoicing data)
    • Products to be completed in the next period
    • Corrective actions to be completed during the next period
  • Project and stage tolerance status How execution of the project and stage are performing against their tolerances (e.g. cost/time actuals and forecast)
  • Requests for change Raised, approved/rejected and pending
  • Key issues and risks Summary of actual or potential problems and risks
  • Lessons report (if appropriate – see section A.15) A review of what went well, what went badly, and any recommendations for corporate or programme management consideration.
Previous Section   Next Section

Expand