Wednesday, November 25, 2015

The PRINCE2 Agile Organization

Organization is one of the seven PRINCE2 Themes and includes definitions of roles and responsibilities at different levels of the project organization. One of the most challenging dimensions of combining PRINCE2 and Agile is to design the organizational interface between the two. PRINCE2 Agile gives us some clear advice on the governance structure and some interface options to choose from. Let us have a closer look at these recommendation and the options.

First the recommendations:
  • There should always be a project board and it should represent the three project interests: User, Supplier and Business.
  • There should always be a project manager. In small PRINCE2 Agile projects, the project manager and team manager roles can be combined.
  • There should be one or several Agile delivery teams reporting to the Project Manager. If Scrum is applied, the Agile delivery team will be a Scrum team.
  • If a Team Manager role is applied, the Team Manager(s) should be included as a member of the Agile delivery team. It should not be a role sitting on the outside.
The interface between Project Manager and an Agile Delivery Team is important, but it not always straight forward to define. PRINCE2 Agile gives us three options:
  1. No-one is referred to as a Team Manager and the Project Manager is will liaise directly with the whole team. 
  2. Create a single point of contact in the team. In most cases this could be the Scrum master or the Product Owner.
  3. Create a Team Manager role in the Agile delivery team. 
The advice in the PRINCE2 Agile method is to make a choice from the three options according to the circumstances. It should be documented in the Project Initiation Document and approved by the Project Board.


It can be beneficial to set on one of the options above as the default PRINCE2 Agile standard for your company. You can then evaluate for each PRINCE2 Agile project if there is a reason to divert from the default.


For option 2, the Scrum Master can be a good choice as point of contact if there is no or little rotation of the Scrum Master role in the scrum team. The Product Owner is less likely to represent the supplier side of the project interests.


Read more about PRINCE2 Agile

Related articles:
What is PRINCE2 Agile?
 PRINCE2 Agile - Stage vs Sprint.

No comments:

Post a Comment