PRINCE2, SCRUM and Agile

PRINCE2 is often perceived as a methodology which lends itself to waterfall approaches only, but this is a huge misconception. PRINCE2 has the flexibility to support Agile development and the two frameworks are highly complementary.

In June 2015, AXELOS launched PRINCE2 Agile — official guidance for combining PRINCE2 with Agile methods.

Definitions

Agile Management

An iterative and incremental method of managing the design and build activities.

Agile Software Development

A group of software development methods in which requirements and solutions evolve through collaboration between self-organising, cross-functional teams.

Scrum

An iterative and incremental agile software development framework for managing product development.

PRINCE2

A structured project management method. PRINCE2 is a project management method whereas Scrum is a development method used by teams. PRINCE2 says nothing about delivery methods.

The Agile Manifesto (Four Principles)

1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

The Seven PRINCE2 Principles

1. Continued business justification
2. Learn from experience
3. Defined roles and responsibilities
4. Manage by Stages
5. Manage by Exception
6. Focus on products
7. Tailor to suit the project context

These two sets of principles are not in conflict — they operate at different levels.

Scrum Roles in a PRINCE2 Context

• Product Owner — represents the stakeholders and is the voice of the customer. In PRINCE2 terms, the Product Owner often takes on aspects of the Senior User role.
• Development Team — responsible for delivering potentially shippable increments (PSIs) at the end of each Sprint. Typically 3–9 cross-functional individuals.
• Scrum Master — accountable for removing impediments to the team's ability to deliver. In PRINCE2 terms, the Scrum Master typically takes on Team Manager responsibilities.

PRINCE2 Stage versus Scrum Sprint

A PRINCE2 stage can contain one or several Sprints, where the stage's time tolerance is zero and tolerance is given on scope. This means:

• Sprint: 1–4 weeks (short, time-boxed)
• Release: One or more sprints
• PRINCE2 Stage: One or more releases
• Project: One or more stages

12 Integration Recommendations

1. Project Planning — The Project Plan in PRINCE2 is a high-level plan; detail develops in Stage Plans in a just-in-time manner.
2. Stage Plans — Product Descriptions now include backlog details.
3. Work Packages — Include backlog items and completion criteria.
4. Daily Scrum Meetings — Used for raising and resolving impediments.
5. Burndown Charts — Provided at frequency determined by the Project Manager.
6. Sprint Completion — Products returned with handover artefacts.
7. Sprint Retrospectives — Teams review and record lessons learned.
8. Issue Recording — All impediments recorded from daily scrums.
9. Escalation — Unresolved impediments escalated to Project Board.
10. Highlight Reports — Include sprint and release burndown charts.
11. End Stage Reports — Incorporate Sprint Review Reports.
12. Next Stage Planning — Work with Scrum Master to allocate backlog elements.

PRINCE2 offers great control at the project level. Scrum and Agile brings freedom and "agility" at the team level. Used together, they provide governance without bureaucracy.