PRINCE2 Agile - Starting Up a Project process

Question 1

In PRINCE2 Agile, what are the five aims of the SU process?

Answer 1

1. Understand the level of complexity of the project and product
2. Understand the current level of Agile integration and understanding. Is any training needed? How Agile-mature are they?
3. Scoping of requirements or building an MVP/POC before the start of the MDP process
4. Create an epic for each requirement of the customer and split this out into work packages or user stories to show the details
5. Focusing on detail and start to populate sprints

Question 2

In PRINCE2 Agile, what are the other names for the SU phase? How can it be modified in PRINCE2?

Answer 2

The SU process can be called emergence, sprint 0, chartering, or visioning.

In PRINCE2 Agile, the SU and IP processes can be blended into one phase.

Question 3

What are the six differences between PRINCE2 and PRINCE2 Agile in the SU process?

Answer 3

1. In PRINCE2 Agile, the exact end product isn’t defined at the start
2. In PRINCE2 Agile, the whole Delivery team can speak to the customer
3. In PRINCE2 Agile, the Delivery team is involved from the start of the project and is strongly encouraged to get involved
4. Project planning focuses on features and intended releases
5. Stage-level planning is conducted with the customer to suit their needs
6. Plans consists of timeboxes, either with set times or a plan to act on a flow-basis