1. Overview PRINCE2 2009 Hogeschool Rotterdam

2. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case

3. 3 Six variables to control  Costs  Timescales  Quality  Scope  Risk  Benefits

4. 4 Structure of PRINCE2  The principles (7):  Guiding obligations  Good practices  The themes (7):  Aspects that must be addressed  The processes (7):  Describe step-wise progression through the project lifecycle  Tailoring PRINCE2

5. 5 PRINCE2 Principles  Continued business justification:  From start throughout the life of the project  Justification is documented and approved  Learn from experience:  At start, progress, closing  Defined roles and responsibilities:  Business, Users, Suppliers  Manage by stages:  Management stages, high-level Project Plan, detailed Stage Plans  Minimum of two stages: initiation and one or more management stages  Manage by exception:  Distinct responsibilities for directing, managing and delivering  Delegating by setting tolerances  Focus on products:  Output orientation  Tailor to suit the project environment:  Stated in Project Initiation Document

6. 6 PRINCE2 Themes  Business Case:  Why?  Organization:  Who?  Quality:  What?  Plans:  How? How much? When?  Risk:  What if?  Change:  What’s the impact?  Progress:  Where are we now? Where are we going? Should we cary on?

7. 7 Business Case  Executive is responsible  Business justification  Is (and remains) project:  Desirable: cost/benefit/risk balance  Viable: the project can deliver the products  Achievable: the products can provide the benefits  Develop: Starting Up (outline) and Initiating (detailed)  Verify and maintain: with decision making  Confirm: Benefits Review Plan  Contents: reasons, options, expected (dis)benefits, timescale, costs, investment appraisal, major risks

8. 8 Organization  Roles in the BUS  Directing: Project Board, overall direction  Executive: overall responsible, business case  Senior User: interests of those who will use the products  Senior Supplier: interests of the delivery parties  Managing: Project Manager, day-to-day management  Delivering: Team Manager, product delivery  Project Assurance, Change Authority, Project Support

9. 9 Quality  Fit for purpose: product focus  Quality Planning:  Understanding quality expectations  Defining acceptance criteria  Document in Project Product Description  Formulating Quality Management Strategy  Writing Product Descriptions  Setting up Quality Register (diary of quality events)  Quality Control:  Carry out quality methods (Quality Review Technique)  Maintain quality and approval records  Gaining acceptance

10. 10 Plans  Three levels:  Project Plan  Stage Plans (and Exception Plans)  Team Plans  Approach to plans:  Design the plan  Define and analyze the products:  (write the project product description)  Create the product breakdown structure  Write the product descriptions  Create the product flow diagram  Identify activities and dependencies  Prepare estimates  Prepare the schedule  Analyze the risks  Document the plan

11. 11 Risk  Threat / opportunity to objectives  Identify:  Context  Risks: cause, event, effect  Assess  Estimate: probability, impact, proximity  Evaluate  Plan  Threat: Avoid, Reduce, Fallback, Transfer, Share, Accept  Opportunity: Exploit, Enhance, Share, Reject  Implement  Risk owner / actionee  Communicate

12. 12 Change  Configuration management  Request for change, Off-specification, Problem/concern  Planning, Identification, Control, Status accounting, Verification and audit  Capture, Examine, Propose, Decide, Implement  Change Authority, concession

13. 13 Progress  Delegating authority: baselines, exceptions and tolerances  Six variables  Time, cost, scope, risk, quality, benefits  Main controls:  Authorizations, progress updates, exceptions/changes  Logs and registers (Risk, Issue, Quality)  Reports (Checkpoint, Highlight, End Stage, End Project)  Management stages  Event driven versus time driven

14. 14 PRINCE2 Processes

15. 15 PRINCE2 Processes  Objectives  Activities  Input - Output  Roles and responsibilities

16. 16

17. 17

18. 18

19. 19

20. 20

21. 21

22. 22

23. 23 Management products Benefits Review Plan Business Case Checkpoint Report Communication Management Strategy Configuration Item Record Configuration Management Strategy Daily Log End Project Report End Stage Report Exception Report Highlight Report Issue Register Issue Report Lessons Log Lessons Report Plan Product Description Product Status Account Project Brief Project Initiation Document Project Product Description Quality Management Strategy Quality Register Risk Management Strategy Risk Register Work Package