PRINCE2 Agile - Initiating a Project process

Question 1

In the Initiating a Project process, how does PRINCE2 Agile differ from pure PRINCE2?

Answer 1

1. In PRINCE2 Agile, one should focus on the product in terms of features and intended releases over controls and processes.
2. The entire Development team is involved in scoping and estimating.
3. The Development team can speak to the customer and customer engagement to plan the stage and scope features is encouraged.
4. Plans are split into timeboxes with the view to populate rigid sprints or implement a flow-based strategy
5. PID may be created in a workshop with the Development team and customer

Question 2

How can the Project Approach incorporate Agile behaviours?

Answer 2

The Project Approach can set out a customer-centric, self-organising team structure. It can also specify the use of Agile methodologies such as Kanban or Scrum.

In IP, we also decide the level of Agile integration as part of selecting the Project Approach.

Question 3

How does the PPD differ in PRINCE2 Agile?

Answer 3

PPD should be split into user stories with outcome focused acceptance criteria. it should also show which requires are mandatory and which are not

Question 4

What document shows which features are mandatory in a project?

Answer 4

The PPD.

Question 5

How does the BMA differ in PRINCE2 Agile?

Answer 5

The BMA focuses on providing value as early as possible. It also specifies when a benefit will be delivered and when the value will be realised.

Question 6

How does the CMA differ in PRINCE2 Agile?

Answer 6

The CMA outlines the minimum amount of communication that needs to happen, focusing specifically on regular meetings and information radiators.

Instead of documentation, Agile prefers information radiators and informal, face-to-face communication.