This document discusses integrating the Prince2 project management methodology with Agile methods like DSDM Atern. It outlines the key benefits of Prince2 and reasons for changing to a more Agile approach. DSDM Atern is described as having principles and techniques that overlap with Prince2. Integrating the two can provide benefits like iterative delivery and increased flexibility, while maintaining Prince2's governance structures. Considerations for a successful integration include assessing organizational culture, identifying pilot projects, and introducing Agile techniques gradually.

1. Prince2 + Agile = Successful projects Presented by: Alex Osborne Date: 23 rd April 2010

4. Why change? Scalability and speed of delivery “ The core problem seems to have been one of scalability, that as the business grew, the billing system wasn’t able to scale up. ” (Jackson, 2007) The downturn will accelerate the adoption of agile. It will play to agile’s strengths, e.g. reduced waste, release to market bringing revenue forward, thereby improving cash flow. (Kelly, 2009) Recession “… it struggles with the impact of the recession …where voice and messaging revenues are declining as consumers rein in their spending and regulation forces prices down.” (Wray, 2009) Culture ready “ Vodafone’s change from a command and control culture to one based on coaching and collaboration…The key values were to put customers first, move quickly into action, be open and involving, work as a team, deliver quality and innovation…” (Eaton and Brown, 2002)

5. What is Agile? Agile Project Management “ Agile Project Management is the work of energizing, empowering, and enabling project teams to rapidly and reliably deliver business value by engaging customers and continuously learning and adapting to their changing needs and environments” (Augustine, 2005) Manifesto for Agile Software Development Augustine, 2005

6. Why integrate DSDM Atern with Prince2? DSDM Atern Scrum Feature Driven Development Crystal methods Lean Software Development eXtreme Programming Why reinvent the wheel! With DSDM you can hit the ground running “ There is considerable overlap between the frameworks of PRINCE2 and DSDM, but this is largely without direct conflict.” (Richards, 2010) Less radical change Well documented

8. Overlap *Avoid duplication of effort DSDM Consortium, 2000

9. Components and Techniques * Adapted from DSDM Consortium (2010) & Tudor (2006) Component Prince2 DSDM Business Case Business case as driver of the project, under constant review DSDM make less of the business case as a document. Business need and direction are maintained by Executive Sponsor and Visionary and Ambassador User roles. Not defining the product in detail at the outset can lead to an ill defined outcome. Organisation Similar in organisational structures, however DSDM has more team roles and empowerment. Controls Tolerance on time, cost quality and benefit is key Team empowerment, can adjust scope, no time or cost tolerance (fixed) which may be difficult to achieve. Emphasis on face to communication can lead to poor audit trail. Risk Good advice on managing risk Suitability risk list, plus white paper on handling risk. Quality Quality plan and path for quality management, plus quality review technique DSDM has quality (fitness for purpose and testing throughout). Change Control Prince2 has the concept of “Request for Change” and Off Specification” as a means of managing change. Regards change as negative thing and is a risk to the project. Manages change dynamically, through close team-working during time-boxes and using MoSCoW prioritization. Time and Cost are constant, allowing change in prioritisation.