Every iteration in Agile methods outputs an Increment, which is a potentially releasable deliverable. It's not necessary to release all increments, but it's a good practice to have frequent releases.
keeping the iterations potentially releasable is required to enable useful feedback; incomplete deliverables do not create a real experience. Even a real release creates a more realistic experience compared to a potentially releasable output, and that's why it's preferred.
Besides the role of frequent releases in adaptation, they also help the customer by bringing early value. They don't have to wait until the project is finished, to enjoy its benefits.
Each PRINCE2 Stage includes one or more releases in PRINCE2 Agile, and each release contains one or more iterations. In simple environments, each Stage can be only one release. Based on this structure, it is not possible to have more than one delivery stage when the project is not supposed to have releases.
Both the Project Plan and Stage Plans should include information on releases. PRINCE2 Agile states that: A Project Plan would need to clearly show how many releases were expected throughout the project, when they will take place and what features are intended to be releases. The same applies to a Stage Plan, albeit with a shorter horizon.
This should be kept high-level; otherwise, adaptation/Agility would be too limited.
- SU: Starting up a Project Process
- IP: Initiating a Project Process
- SB: Managing a Stage Boundary Process
- CP: Closing a Project Process
- (DP): Directing a Project Process (note that not all activities in this process are shown in this diagram)
- The above image assumes that Scrum is used in the delivery level, which is not necessary.
- The number of stages, releases, and Sprints are just examples, as well as the exception in the third stage.
- The diagram is schematic and many details are not shown.