PRINCE2 Agile 2016
Previous Section   Next Section

23.3 Report products

Reports are management products providing a snapshot of the status of certain aspects of the project. In Table 23.3, the numbered reports refer to the numbers used in the PRINCE2 manual for the PRINCE2 management products (see also Table 16.2).

Image 23.1 Adapting and reworking the PRINCE2 products

Image 23.1 Adapting and reworking the PRINCE2 products

Reports Overview of the tailoring required and further considerations

3. Checkpoint report

An important product that would typically be in the form of an information radiator and/or a burn chart (see Figure 15.1). Could be replaced by a daily stand-up or Scrum meeting with the agreement of the delivery team but would need to avoid being seen as a ‘reporting to’ mechanism. If the information is transparent then this can be extracted (or ‘pulled’) by the project manager when required.

8. End project report

An assessment of the use of agile is likely to be included in this with reference to the judgements made when using the Agilometer.

9. End stage report

May be built incrementally throughout a stage depending on the frequency of timeboxes or releases. May be part of a release review.

10. Exception report

Most likely to occur due to the expected amount to be delivered being forecast to exceed tolerance. This could be triggered by a burn chart (at the sprint or release level) showing how progress has gone outside tolerance. This may result in an immediate meeting where options are discussed before raising it with the project board.

11. Highlight report

An important product that may contain additional information on releases (e.g. what has been released and what benefits have been enabled). May be delivered verbally.

Could be in the form of an information radiator and/or a burn chart. If the information is transparent then this can be extracted (or ‘pulled’) by the project board when required.

13. Issue report

May be low-tech and produced or updated during a sprint review or release review.

15. Lessons report

May be low-tech and handed to project support informally.

18. Product status account

These may need to cater for high degrees of change due to the regular iteration of products under configuration management.

Table 23.3 Tailoring report products

Previous Section   Next Section