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.
Option A, the end of the pre-project stage, is too early, as no meaningful delivery has occurred to assess benefits. Option B, the end of initiation, focuses on planning and setup rather than value realization. Option D, the end of the final delivery stage, is too late because it limits opportunities to adapt if benefits are not being realized as expected.
Agile Foundation documents stress the importance of frequent inspection and adaptation. By reviewing and updating the project canvas at the end of each delivery stage, teams can make informed decisions about continuing, pivoting, or stopping work. This supports effective governance while preserving agility. Regular benefit assessment ensures that the project remains aligned with business objectives and continues to justify investment, reinforcing Agile’s focus on value delivery rather than simply completing planned activities.
