PRINCE2 Agile® Process Blending

Mandate usually
in the form of:
Terms of Reference

DP
Directing a Project Servant Leaders
PRINCE2 Process Flow

OK Celebrate the
PID is OK OK and Resources Final Demo

SU
to IP
to CS Regular Escalated with the TEAM
Progress Issues and
From Blockers

SB CP
Starting Up

IP CS
Information for Board
a Project Radiator to resolve PRINCE2 project

PRINCE2 thinking
direction
Servant Leader

Agile thinking
®

Initiating Managing a Closing

Work Controlling a Stage PRINCE2 project
a Project Stage Boundary Package a Project management

Regular Escalated Agile product

progress Issues and delivery

MPD
from Burn Blockers
Agree Team Charts & from Daily Work
Project Brief PID Stage Plan
Plan Daily Stand-ups Package End Project Report
Why? What? Who? Release Plan
How?
- Strategies Sprint Planning Stand-ups Done Final Demo

On-going Benefits
Review and update: (Follow on Actions)
- Registers
- Business Case Sprint Goal
- Project Plan
- Detailed Business
Value - Project Plan Managing
B - Project Team etc.
Product Delivery
Case
U S - Benefits Review Plan - Release Demo
- End Stage Report

1st Time 1st 1st 1st

Project Timebox
Stage Timebox 1 Stage Timebox 2 T’box n Final Stage Timebox
On-going
Initiation Product
Stage Plan Prioritised PRINCE2
Product Backlog Backlog
Agile Project Timeline

into CPI
EPICs
Cynefin Cynefin
User Stories Prioritised
Stage
Prioritised Product
Project Backlog
Product
Backlog
Top Level
Product Sprint Sprint Sprint Sprint
Backlog
Cynefin Prioritised Prioritised Prioritised Prioritised
Cynefin READY
Sprint
READY
Sprint
READY
Sprint
Sprint READY
Sprint
Backlog Backlog Backlog Backlog
Prioritised
READY Prioritised
Quick
Cynefin Agilometer
Agilometer Sprint
Backlog
Product
Backlog Kanban - MPD
On-going WIP
Prioritised Prioritised Key
Product Product

Quick Initial
Backlog Backlog Potentially Shippable
Agilometer Sprint Sprint Sprint Sprint Sprint Sprint Product
Retrospective
Prioritised Prioritised Prioritised Prioritised Prioritised Prioritised
Visioning or Sprint Zero READY
Sprint
READY
Sprint
READY
Sprint
READY
Sprint
READY
Sprint
READY
Sprint Done
Backlog Backlog Backlog Backlog Backlog Backlog
Sprint Review
Pre-Project Initiation Stage Delivery Stage Delivery Stage Final Delivery Stage
T: UK +44 (0)1270 611600
T: AUS 13 0045 9459
T: NZ + 64 9 363 9777
T: UAE + 971 (0) 4 362 4295
PRINCE2 Agile®, PRINCE2® are registered trade marks of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. © ILX Group plc E: contactus@ilxgroup.com
 Rich Self-
Transparency Collaboration communication organisation Exploration
Scrum 24

PRINCE2 Agile®
Development
Hours Team

SM 2 to 4
Weeks
PO Useful References
Development Team Sprint SM
Backlog
Sprint Sprint Term Examples Similar terms
PO The Sprint Behaviours Being collaborative, Self-organizing, Customer Principles. Values.
Product focused, Empowered, Trusting not blaming. Mind-set.
Backlog Sprint Planning

Pr
Meeting Concepts Prioritising what we delivered, Working Fundamentals

m
SM

in
PO

ru
iteratively and incrementally, Not delivering

ci
Sc
Development Team

pl
es
everything. Time focused, Inspect and adapt.
We are uncovering better ways of developing
PRINCE2 Role Agile equivalent Kaizen. Limiting WIP.
software by doing it and helping others do it.
Executive None, but someone needs to pay for the development Techniques Burn charts, User Stories, Retrospectives, Practices. Tools.
Through this work we have come to value:
Senior Supplier(s) None, but someone needs to agree the Agile Contract Timeboxing, Measuring flow.
Senior User(s) Product Owner(s) or CSME(s) working closer to the teams Individuals over processes
Business Assurance None, but someone should check that value for money and interactions and tools
User Assurance Customer Representative(s) has some overlap Working comprehensive
over
Supplier Assurance Supplier Representative(s) role has some overlap software documentation

Roles
Change Authority Product Owner makes the key prioritising decisions Customer contract Time Fix Cost Don’t
over
Project Manager Pastor of Fun (possibly scrum of scrum master) collaboration negotiation flex

Tolerances
Project Support None
Responding to over following
Team Manager Often the Supplier Subject Matter Expert(s) change a plan

That is, while there is value in the items in the right

Project The final output we value the items on the left more. Fix or May
Benefits Risk
product from the project Flex flex
Is composed of description Re
(Composition) HIGH

in t
Po gh
qu

ts
y Ei
ire
Rich Communication

Ke he
m
en

T
Product Product Product
Fix &
ts
group group group Quality Scope Flex
(Criteria) Flex
High level
requirements (epic)
Product* Product
description description Key point
GOAL 1 PRINCE2 (2009 edition) is already enabled for use with Agile
(Intermediate?) Deliver the project 2 PRINCE2 is suitable for any style of project and is not a ‘traditional’ project

Effort
(A) (B) by the end of the year management approach as is typically constrained to Agile
_______ As a ______ To do In progress Done 3 PRINCE2 Agile is for any project and not just IT projects
_______ I want to __
_______ 4 ‘IT only’ frameworks and techniques are mentioned in PRINCE2 Agile
_______ So that ___ Time but not extensively
Low level 5 There is much more to Agile than the Scrum framework. Agile is not Scrum.
* a product description could be represented by: requirements
(A) A detailed requirements list or LOW Issues NEWS 6 The most ‘commonly used’ Agile approaches are Scrum and Kanban, but
(B) A user story they are not suitable for managing a project in isolation. However, they can
Independent Reduced Dependences make it easier to plan be effectively used in a project context.
TEAM We should be honest
Negotiable Details of the user story are added via collaboration and consensus 7 The term Agile (in the manual) refers to a family of behaviours, concepts,
RULES We should be open
Valuable Should always provide value to the end customer Everyone has a say frameworks and techniques.
Estimable Should not be too large or too vague as this will not support story point estimating 8 Using Agile on a project is not a question of ‘yes or no’. It is about ‘how much’.
Small Should be capable of being developed by the team in a short time scale
Testable User stories should always be supported by clear well-written acceptance criteria
T: UK +44 (0)1270 611600
T: AUS 13 0045 9459
T: NZ + 64 9 363 9777
T: UAE + 971 (0) 4 362 4295
PRINCE2 Agile®, PRINCE2® are registered trade marks of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. © ILX Group plc E: contactus@ilxgroup.com