Mandate usually in the form of: Terms of Reference PRINCE2 Agile® Process Blending

PRINCE2 Directing a Servant Leaders OK Celebrate the PID is OK to IP OK and Resources Final Demo to CS Regular Escalated with the TEAM Progress Issues and DP Blockers From Starting Up Information for Board a Project Radiator to resolve PRINCE2 thinking PRINCE2 project Agile thinking ® direction Process Flow Servant Leader SU Initiating Managing a Closing PRINCE2 project Work Controlling a Stage management a Project Stage Boundary Package a Project SB CP Agile product IP CSRegular Escalated progress Issues and delivery from Burn Blockers Agree Team Charts & from Daily Work Project Brief Stage Plan PID Daily Stand-ups End Project Report Why? What? Who? Release Plan Plan Package - Strategies Stand-ups Final Demo How? Review and update: Sprint Planning Done - Registers (Follow on Actions) - Business Case Sprint Goal On-going Benefits - Project Plan - Project Plan - Detailed Business Value Managing B Case - Project Team etc. U S - Benefits Review Plan - Release Demo Product Delivery - End Stage Report MPD

1st Time 1st 1st 1st

Project Timebox

Stage Timebox 1 Stage Timebox 2 T’box n Final Stage Timebox

On-going Initiation Product

Agile Project Timeline Stage Plan Prioritised PRINCE2 Product Backlog Backlog 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 READY READY READY Sprint Sprint Sprint Sprint Sprint Backlog Backlog Backlog Backlog Prioritised READY Prioritised Quick Agilometer Sprint Product Cynefin Agilometer Backlog Backlog - MPD On-going WIP

Prioritised Prioritised Key Product Product Backlog Backlog Quick Initial Potentially Shippable Agilometer Sprint Sprint Sprint Sprint Sprint Sprint Product Retrospective Prioritised Prioritised Prioritised Prioritised Prioritised Prioritised Visioning or Sprint Zero READY READY READY READY READY READY Sprint Sprint Sprint Sprint Sprint 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: [email protected] Rich Self- Transparency Collaboration communication organisation Exploration 24 Development Scrum Hours Team PRINCE2 Agile®

PO 2 to 4 Useful References SM Weeks

Development Team Sprint SM Backlog Sprint Sprint Term Examples Similar terms PO The Sprint Behaviours Being collaborative, Self-organizing, Customer Principles. Values. Product Principles focused, Empowered, Trusting not blaming. Mind-set. Backlog Sprint Planning Meeting Concepts Prioritising what we delivered, Working Fundamentals SM PO iteratively and incrementally, Not delivering Development Team Scrum 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 Through this work we have come to value: Techniques Burn charts, User Stories, Retrospectives, Practices. Tools. 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 over comprehensive Supplier Assurance Supplier Representative(s) role has some overlap Change Authority Product Owner makes the key prioritising decisions Don’t Customer over contract Time Fix Cost Roles collaboration negotiation flex Pastor of Fun (possibly scrum of scrum master) 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. Benefits Fix or Risk May product from the project Flex flex Is composed of description Requirements (Composition) HIGH Rich Communication The Eight Product Product Product Key Points Fix & 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 Effort 2 PRINCE2 is suitable for any style of project and is not a ‘traditional’ project (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 ______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 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 RULES We should be open 7 The term Agile (in the manual) refers to a family of behaviours, concepts, 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: [email protected]