Benefits Review Plan
The key difference is that the product of a predictive project is usually put into operation only after the project is finished, and therefore the Benefits Review Plan is mainly used to explains the post-project period. In adaptive environments however:
- There are usually Frequent Releases that bring early value to the business, and should be planned in the Benefits Review Plan, and
- The result of reviewing the benefits (business value) is the main tool for adaptation: it allows the product to evolve in a way that maximizes value. So, the Benefits Review Plan should also explain how the results will be incorporated into the project and affect the product.
- 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.
- Benefits Review Plan at PRINCE2 wiki