Managing Successful Projects

Transcription

1 } Managing Successful Projects wth PRINCE2 00 OfficeofGovQrnmentCommerce LOnGOÜ! I ju

2 Acknow Whyusea project management method? 1.2 BenefitsofusingPRINCE2 1.3 Support forprince2 Structure of the manual 1.5 Using the manual What is a project? 2.2 ThescopeofPRINCE2 2.3 PRINCE2 in context 2.4 QÄ*view<> PRmC The proeesses 2.6 The eomponents 2.7 Thetechniques 2.8 Process and component links Management levels Structure of each process description 3.3 Diagram and text notation 23 VII

3 4.1 Fundamental principles mmmmmmmmm. 4.2 Context 4.3 Processdescription Appointing an Executive and a Project Manager (SU1) 4.5 Designing a Project Management Team (SU2) Appointing a Project Management Team (SU3) 4.7 Preparing a Project Brief (SU4) Planning an Initiation Stage (SU6) 43 5 Initiating a Project (IP) 5.1 Fundamental principles Context 5.3 Processdescription 5.4 Planning Quality(IPl) 5.5 Planninga Project(IP2 5.6 Refining the Business Case and Risks (IP3) 5.7 Setting up Project Controls (IP4) Do 5.9 Assembling a Project Initiation Document (IP6) 65 6 Dirertinga Protect i 6.1 Fundamental principles fi 2 Contpxt 6.3 Processdescription 6.4 Authorisir ''mmmmmiam mmmm 6.5 Authorising a Project (DP2) 69,,, by 70 _. '"* Authorising a Stage or Exception Plan (DP3) 6.7 Giving Ad Hoc Direction (DP4) 6.8 Confirming Project Closure (DP5) VIII

4 ) 7.1 Fundamental principles 7.2 Context 7.3 Processdescription Assessing Progress (CS2) Examining Project Issues (CS4) 7.8 Rcviewing Stage Status (CS5) 7.9 Reporting Highlights (CS6) 7.11 Escalating Project Issues (CS8) - :' :: ':-.'Y - : - v. /,-:,' - 0& ;illillii»illiiii Fundamental principles 127 YY : YYUYY/ yvyyyyyyyy;yvyyyy<yyyy ; fyyyh4 8.3 Process description Executing a Work Package (MP2) 8.6 Delivering a Work Package (MP3) l. ; ;.--. * ; mit: Fundamental principles Processdescription 9.4 Planninga Stage (SB1) 9.5 Updating a Project Plan (SB2) B3i Updating the Risk Log (SB4) Producing an Exception Plan (SB6) 150 IX

5 10.1 Fundamental principles 10.2 Context 10.3 Processdescription 10.4 Decommissioning a Project (CP1) 10.5 Identifying Follow-on Actions (CP2) 10.6 Evaluating a Project (CP3) Planning(PL) \'^^^äsststilbh^ 11.1 Fundamental principles 11.2 Context 11.3 Processdescription 11.4 Designinga Plan (PL1) 11.5 DefiningandAnalysing Products (PL2) 11.6 Identifying Activities and Dependencies(PL3) 11.7 Estimating (PL4) 11.8 Scheduling (PL5) 11.9 Analysing Risks (PL6) Completinga Plan (PL7) P^H? Introduction to the PRINCE2 components 13 Business Case 13.1 Whatisa Business Case? i: j..2 What should a Business C;;sr cor:tain? 13.3 Developing a Business Case 13.4 Development path of the Business Case. ^ «* Organisation 14.1 Overview 14.2 The PRINCE2 project management team Project Support 217

6 ) 15 Plans >H/ lil Benefitsof planning Whatisa plan? What are the elements of a plan? ThePRINCE2approach Levelsof plan Controls ;I^^^K^^^#*- r^' ; ' Purpose of control 00 V 16.2 Controls overview Projectstart-up Controlled progress Control led dose Stages 246 ia. fvi3njiqvmfcrii OT rlsk.^iseäs. cyi-'j/-., -~.'i:. ;.~T*-' 17.1 What is risk management? Riskpnnciples The risk management cyele Risk profile Budgeting for risk management Mapping the management of risk to the PRINCE2 processes Interdependencies Further risk management considerations Quality in a project environment ^,; Sit: Purpose OCE 18.2 What is quality? Quality management The quality path Making project quality work 273 XI

7 19.1 Purpose 19.3 Baseline naging the eonfiguration 19.5 Configuration management method Configuration management and a Projeet Support Office 283 $& Ctetftgecontrol 20.1 Purpose Authority levels Management of change and configuration management 289 SWS'' 22.1 The four products of product-based planning Producing a Product Description of the final product 22.4 Producing a Product Breakdown Structure Writing a Product Description 22.7 Product-based planning example iiitoiääiiiiiiiwii lililll mmmim Guidance on creating a product-based plan Change control steps 315 XII

8 i 24.1 Whatisaquality review? 24.2 Quality review benefits 24.3 Context < review technique A.1 Acceptance Criteria Business Cas A.3 Checkpoint Report M& Communication Plan A.5 Configuration Item Record A.6 Configuration Management Plan A.7 Customer's quality expectations A.9 End Project Report A.11 Exception Plan 355 A.13 Follow-on Action Recommendations A.14 Highlight Report A.15 IssueLog A.16 Lessons Learned Log A.17 Lessons Learned Report ;.>* : K : «?i,v; A.18 Off-Specification- -. «^ :.- ; r % ; A.19 Post-Project Review Plan A.21 Product Checklist A.23 Product Flow Diagram A.24 Product Status Aeeöfc A.25 Project Approach : :.4--, ft"ji*jjb!s.iy XIII

9 A.26 Project Brief 373 A.27 Project Initiation Document 375 A.28 Project Issue 378 A.29 Project Mandate 379 A.30 Project Plan 381 A.31 Project Quality Plan 383 A.32 Quality Log 385 A.33 RequestforChange 386 A.34 RiskLog 387 A.35 StagePlan 389 A.36 WorkPackage 391 Appendix B: Project management team roles 395 B.1 Project Board 395 B.2 Executive 397 B.3 Senior User 399 B.4 Senior Suppiier 400 B.5 Project Manager 401 B.6 Team Manager 402 B.7 Project Assurance 403 B.8 Project Support 405 B.9 Configuration Librarian 406 B.10 Project Support Office (PSO) 407 Appendix C: Risk categories 409 Appendix D: PRINCE2 healthcheck 413 Appendix E: Project document management 421 Further information Index 427 XIV i