Directing a Project is mainly about ensuring the benefits and business value of the project. This is similar to the responsibility of a Product Owner in Scrum. So, care should be taken not to create conflicts here. The key is the normal PRINCE2 Manage by Exception Principle: to keep the directing level focused only on the high-level aspects.
There are different ways of scaling Scrum; in one method, there's a chief Product Owner working with a number of local Product Owners. The Executive would be similar to this kind of chief Product Owner; directing the local Product Owners who are working with the teams.
- 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.
- Directing a Project Process at PRINCE2 wiki