Which TWO statements about the typical tailoring of a checkpoint report in an agile environment are CORRECT?
1. It should be replaced by the project manager attending a daily stand-up.
2. It should be displayed in the form of an information radiator in a team room.
3. It should be produced when the amount to be delivered will result in tolerance being exceeded.
4. It should be produced in a product backlog in the form of prioritized user stories.
In an agile environment, a checkpoint report is typically tailored to suit the needs of the team and the project. Replacing it by the project manager attending a daily stand-up is valid as it allows for regular updates without the need for formal reports (statement 1). Displaying it in the form of an information radiator empowers the team by making progress visible and easily accessible in the team room (statement 2). Statements 3 and 4 involve more formal and structured documentation, which is less common in agile practices focused on flexibility and continuous delivery, making them less appropriate.
https://prince2agile.wiki/management-products/reports/checkpoint-report/
Checkpoint reports are usually informal and they may also appear on information radiators. They may be replaced by standup meetings if the delivery team is happy for the project manager to attend.
im sure about point 2... not 3 Table 23.3 Tailoring report products page 197 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