21.2 Agile ways of working that may already exist
The Managing a Stage Boundary process is primarily about checking the ongoing viability of a project and stopping the project if this is no longer the case. In agile there is a similar concept of stopping the regular delivery cycle of releases when the value being delivered drops off, becomes marginal to the amount of effort involved or there is an opportunity cost to other work or projects. In agile this is usually determined as and when it happens (e.g. at the end of a sprint or release), whereas in PRINCE2 a stage end and a formal check on ongoing project viability is determined well in advance and the planned delivery of features needs to fit into this.
The project board should determine how long a stage should last before deciding what goes into it. They may wish to adjust this in a collaborative manner in the light of what is planned, but they should not be driven by this.
There is a similarity between a major review of a release (e.g. one that took 3 months) and the Managing a Stage Boundary process. In both, progress can be reviewed with respect to how much value or benefit has been delivered, how the team is performing, how the processes are working, and how the project is progressing with regard to quality and product delivery, planning the next release and assessing the project’s exposure to issues and risks.