When should the project canvas be BOTH updated and used to assess whether the intended benefits have been or will be realized?

Question

Options

• AAt the end of the pre-project stage
• BAt the end of the initiation stage
• CAt the end of each delivery stage
• DAt the end of the final delivery stage

• A
  9% (2)
• C
  86% (19)
• D
  5% (1)

Explanation

Agile Foundation guidance describes the project canvas as a living, lightweight artifact that supports alignment, transparency, and ongoing benefit realization throughout the project lifecycle. It should not be treated as a one-time planning document. The correct point at which the project canvas should be both updated and used to assess whether intended benefits have been or will be realized is at the end of each delivery stage, making option C the correct answer. Agile and PRINCE2 Agile approaches emphasize incremental delivery and continuous validation of value. Each delivery stage produces usable outputs or increments that can be reviewed against expected outcomes and benefits. Updating the project canvas at the end of each delivery stage allows the team and stakeholders to reflect on what has actually been delivered, what has changed, and whether assumptions made earlier are still valid. This includes reassessing benefits, risks, stakeholders, and priorities based on real evidence rather than predictions.

No community discussion yet for this question.