AGILE AND PRINCE2Happy bedfellows?
Let’s start with some assumptions!§  We assume that we are dealing with organisations that have    PRINCE2 and want to ru...
So, just what is PRINCE2?§  Was created in 1996 by a UK Government agency (OGC – Office    Government Commerce)§  Intend...
PRINCE2 has seven principles§    Continued business justification§    Learn from experience§    Defined roles & respons...
PRINCE2 has seven themes§    ‘The Why’ – Business Case§    ‘The Who’ – Organisation§    ‘The What’ - Quality§    ‘The ...
PRINCE2 projects have four phases§    Starting a Project§    Initiating a Project§    Managing Stages within a Project§...
PRINCE2 focuses on products§    Benefits Review Plan                §    Configuration Item Records§    Business Case  ...
PRINCE2 focuses on products§    Benefits Review Plan                §    Configuration Item Records§    Business Case  ...
What about the People?
A (little) bit about Agile…§  Agile Manifesto created in 2001§  Lots of different flavours   –    SCRUM   –    XP   –   ...
Agile focuses on the product
Agile focuses on the people
So, do the two fit together?
We	  understand	                         Project  both	  Agile	  and	                     Manager                         ...
Managing by Exception    WIDER                  Time              Cost ORGANISATIONEXTENDED AGILE    TEAM                 ...
Mapping Agile to Prince2Starting       Initiate                         Managing Stages                       Closing   a ...
Starting a ProjectAGILE ACTIVITIES             PRINCE2 PRODUCTS                                 •    Identify Project Spon...
Initiating a ProjectAGILE ACTIVITIES            PRINCE2 PRODUCTS                                      •    Prepare the Pro...
Managing / Defining StagesAGILE ACTIVITIES                                  PRINCE2 PRODUCTS•    Release Planning Meeting ...
Defining a work packageAGILE ACTIVITIES                                     PRINCE2 PRODUCTS•    Iteration Planning Meetin...
Product DescriptionsAGILE ACTIVITIES                                 PRINCE2 PRODUCTS       MOV-010               M       ...
Reporting ActivitiesAGILE ACTIVITIES                        PRINCE2 PRODUCTS •    Daily Stand-ups                        •...
Exiting a StageAGILE ACTIVITIES              PRINCE2 PRODUCTS                                    •    End Stage Report (pa...
Closing a ProjectAGILE ACTIVITIES              PRINCE2 PRODUCTS                                    •     End Project Repor...
To sum up….§  Understand the boundaries in your organisation   –    Where does PRINCE2 make most sense?   –    Where does...
QUESTIONS?§  (e) – mike.allen@western-agile.com§  (Blog) – western-agile.blogspot.com§  (w) – www.western-agile.com
Prince2 and agile happy bedfellows
Upcoming SlideShare
Loading in …5
×

Prince2 and agile happy bedfellows

2,909 views

Published on

An overview of how you can run Agile projects in a PRINCE2 organisation.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,909
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
193
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Prince2 and agile happy bedfellows

  1. 1. AGILE AND PRINCE2Happy bedfellows?
  2. 2. Let’s start with some assumptions!§  We assume that we are dealing with organisations that have PRINCE2 and want to run Agile projects§  We assume that you are NOT an Agile organisation who wants to adopt PRINCE2!§  We assume that you already know a bit about Agile
  3. 3. So, just what is PRINCE2?§  Was created in 1996 by a UK Government agency (OGC – Office Government Commerce)§  Intended to create a standard approach for managing government projects§  Is now used throughout the UK and in over 50 countries worldwide§  “It is designed to be applied to any type of project – and can easily be implemented alongside specialist, industry specific models (e.g. development lifecycles)” – (Managing Successful Projects with Prince2, OGC, 2009)
  4. 4. PRINCE2 has seven principles§  Continued business justification§  Learn from experience§  Defined roles & responsibilities§  Manage by stages§  Manage by exception§  Focus on products§  Tailor to suit the environment
  5. 5. PRINCE2 has seven themes§  ‘The Why’ – Business Case§  ‘The Who’ – Organisation§  ‘The What’ - Quality§  ‘The How, How Much & When’ – Plans§  ‘The What-if’ - Risk§  ‘The Impact’ - Change§  ‘The Progress’ – Monitoring and escalation
  6. 6. PRINCE2 projects have four phases§  Starting a Project§  Initiating a Project§  Managing Stages within a Project§  Closing a Project
  7. 7. PRINCE2 focuses on products§  Benefits Review Plan §  Configuration Item Records§  Business Case §  Daily Log§  Communications Management §  Issue Register Strategy §  Lessons Log§  Configuration Management Strategy §  Quality Register§  Project Plan §  Risk Register§  Product Description §  Checkpoint Report§  Project Brief §  End Project Report§  Project Initiation Document §  End Stage Report§  Project Product Description §  Exception Report§  Quality Management Strategy §  Highlight Report§  Risk Management Strategy §  Issue Report§  Work Package §  Lessons Report §  Product Status Account
  8. 8. PRINCE2 focuses on products§  Benefits Review Plan §  Configuration Item Records§  Business Case §  Daily Log§  Communications Management §  Issue Register Strategy §  Lessons Log§  Configuration Management Strategy §  Quality Register§  Project Plan §  Risk Register§  Product Description §  Checkpoint Report§  Project Brief §  End Project Report§  Project Initiation Document §  End Stage Report§  Project Product Description §  Exception Report§  Quality Management Strategy §  Highlight Report§  Risk Management Strategy §  Issue Report§  Work Package §  Lessons Report §  Product Status Account
  9. 9. What about the People?
  10. 10. A (little) bit about Agile…§  Agile Manifesto created in 2001§  Lots of different flavours –  SCRUM –  XP –  DSDM –  Atern§  Now considered a ‘mainstream’ software delivery approach
  11. 11. Agile focuses on the product
  12. 12. Agile focuses on the people
  13. 13. So, do the two fit together?
  14. 14. We  understand   Project both  Agile  and   Manager We  love   PRINCE2   PRINCE2!   processes   Project PMO Sponsor CORE AGILE TEAM Scrum master / Product Owner / IM Customer Board QA BA Dev BA Dev Senior Dev ExecsWe  focus  on  Agile  and  let  someone   WIDERelse  worry  about   EXTENDED AGILE ORGANISATION PRINCE2   TEAM
  15. 15. Managing by Exception WIDER Time Cost ORGANISATIONEXTENDED AGILE TEAM ValueCORE AGILE TEAM Features
  16. 16. Mapping Agile to Prince2Starting Initiate Managing Stages Closing a a on a aProject Project Project Project Project PID End Brief Project Report STAGES & WORK PACKAGES RELEASES & ITERATIONS Release 1 Release 2 I0 I1 I2 ….…. In I0 I1 I2 ….…. In Concept Inception ReleaseWorkshops Workshops Retrospective
  17. 17. Starting a ProjectAGILE ACTIVITIES PRINCE2 PRODUCTS •  Identify Project Sponsor •  Identify Project Manager •  Prepare Outline Business Case •  Prepare Project Brief •  Project Background •  Project Objectives •  Project Scope CONCEPT WORKSHOPS FEEDS   •  Risks •  Issues •  Assumptions •  Dependencies •  Benefits •  Plan the next stage
  18. 18. Initiating a ProjectAGILE ACTIVITIES PRINCE2 PRODUCTS •  Prepare the Project Initiation Document •  Project Definition •  Project Approach •  Team Structure FEEDS   •  High Level Project Plan •  Refined Business Case •  Plan for next stage INCEPTION WORKSHOPS •  Project Initiation Document •  Role descriptions •  Quality management strategy •  Configuration management strategy •  Risk management strategy •  Communications management strategy •  Project controls & tolerances
  19. 19. Managing / Defining StagesAGILE ACTIVITIES PRINCE2 PRODUCTS•  Release Planning Meeting •  Stage Plan •  Timing of the Release •  Plan description •  Resources planned for the FEEDS   •  Plan prerequisites Release •  Planning Assumptions •  Assumptions •  Review of Lessons Learned •  Dependencies •  Product Descriptions (i.e. scope) •  Themes to be delivered •  Schedule •  Monitoring and Control •  Budgets •  Tolerances
  20. 20. Defining a work packageAGILE ACTIVITIES PRINCE2 PRODUCTS•  Iteration Planning Meeting •  Work package definition •  Timing of the iteration •  Dates •  Resources planned for the FEEDS   •  Who is delivering the work package iteration •  A description of the work package •  Features being committed to within the iteration •  Techniques, processes & procedures •  Development interfaces •  Operations & maintenance interfaces •  Configuration management requirements •  Joint agreements •  Tolerances •  Constraints •  Reporting Arrangements •  Problem Handling and escalation •  Stage plan extract •  Product Descriptions •  Approval method
  21. 21. Product DescriptionsAGILE ACTIVITIES PRINCE2 PRODUCTS MOV-010 M As a Cinema Visitor I want to buy a ticket •  Product Description So I see the movie 3 •  Identifier •  Title •  Purpose •  Composition Story Manual •  Derivation Narrative Test •  Format & Presentation Scripts REPLACES   •  Development skills required •  Quality Criteria •  Quality Tolerance •  Quality Method •  Quality skills required •  Quality Responsibilities Delivered Automated Code Tests
  22. 22. Reporting ActivitiesAGILE ACTIVITIES PRINCE2 PRODUCTS •  Daily Stand-ups •  Checkpoint Report •  Card Wall •  Risk Register •  Iteration Burn-up Chart •  Assumptions •  Release Burn-up Chart FEEDS   •  Issues Log •  Story Map •  Dependencies •  Master Story List •  Decision Log •  Financials Tracking •  Resource Plan
  23. 23. Exiting a StageAGILE ACTIVITIES PRINCE2 PRODUCTS •  End Stage Report (part) FEEDS   •  Overview of Business Case •  Review of Stage Objectives •  Review of Team Performance •  Off specifications •  Lessons Report (part) PROJECT RETROSPECTIVE •  End Stage Report (part) •  Review of products •  Lessons Report (part)
  24. 24. Closing a ProjectAGILE ACTIVITIES PRINCE2 PRODUCTS •  End Project Report (part) FEEDS   •  Overview of Business Case •  Review of Project Objectives •  Review of Team Performance •  Off specifications •  Lessons Report (part) PROJECT RETROSPECTIVE •  End Project Report (part) •  Review of products •  Lessons Report (part)
  25. 25. To sum up….§  Understand the boundaries in your organisation –  Where does PRINCE2 make most sense? –  Where does Agile make most sense?§  Create ‘cookie cutter’ Agile versions of key PRINCE2 documents –  Project Brief –  Project Initiation Document –  Work Package definition§  Use Agile activities to feed information into PRINCE2 documents§  Use PRINCE2 to run the PROJECT§  Use Agile to create the PRODUCT§  Use Agile to focus on the PEOPLE
  26. 26. QUESTIONS?§  (e) – mike.allen@western-agile.com§  (Blog) – western-agile.blogspot.com§  (w) – www.western-agile.com

×