PRINCE2 Agile - Directing a Project

Question 1

What are the differences between PRINCE2 Agile and pure PRINCE2 related to the DP process?

Answer 1

In relation to the DP process, PRINCE2 Agile differs from pure PRINCE2 in three ways:

1. In PRINCE2, the PB receive information from the PM via reports. In PRINCE2 Agile, there is less reporting and the PB is encouraged to check the information themselves via Information Radiators (e.g. Jira boards, joining daily stand-ups).
2. One can still have standard documentation and some PRINCE2 documentation is still needed, but one principle of the Agile manifesto “working software” and “customer collaboration” over “documentation”.
3. Agile very much leans into the PRINCE2 principle of “Manage by Exception”. Teams and leadership with low Agile experience need to understand that features can be dropped to stick to time and cost.

Question 2

What expectations need to be set at the start of the project?

Answer 2

• PB is expected to be more involved, but not controlling as per manage by exception
• PB is also expected to find information themselves instead of relying on the PM to send reports
• PB needs to understand that Agile optimises for time
• Decisions can be made in meetings and demos, and based on information pulled from information radiators as opposed to from reports.

Question 3

Where else can the PM seek guidance in PRINCE2 Agile

Answer 3

In PRINCE2 Agile, some direction, particularly related to the customer or product, may be given by the Product Owner.