PRINCE2-SampleProject-Premium-MP847

More documents

Recommendations

Info

Tailoring of PRINCE2 (part of PID) Document: Tailoring of PRINCE2 Project: Pen Project Author: Project Manager Date: 1. Adapting the Principles All PRINCE2 principles will be fully applied in the project. 2. Adapting the Themes Build beber relaDonships with clients and reduce the loss in the renewal of maintenance contracts from 10% to 5%. CopyWorld365 had 4,200 maintenance contracts with an average profit of €200 per contract = €840,000. A 10% loss in contracts is a loss of €84,000 3. Adapting the Terms The default PRINCE2 terminology will be used in the project, except for the Project Brief, which may also be called “project charter” in some documents or verbal communicaDons; they will both address the same management product. 4. Adapting the Management Products The default PRINCE2 management products will be kept separated (each in a single document), with the same default PRINCE2 product descripDons, except that: we would not use formal and documented Work Packages except for those that are handled by a Team manager other than the Project Manager. Checkpoint Reports would be verbal too. 5. Adapting the Processes All PRINCE2 processes will be kept separated and will be handled formally. 6. Adapting the Roles • The same person will handle both the ExecuDve role and represent the corporate level. • The Project Assurance and Change Authority roles will be merged into the Project Board. • The Project Support role will be handled by the Project Manager. • The Project Manager will also have the role of Team Manager in most cases. Our objec(ve here is to apply the simplest possible -‐ yet full -‐ form of PRINCE2 so you can view the majority of PRINCE2 documents and get a be_er idea of how a typical midsize project works and see that all the PRINCE2 principles are applied. It’s common for small projects to handle the Star(ng up a Project process informally, or to combine it with Ini(a(ng a Project process; A small project like this would usually be tailored differently, but we’ve not simplified it enough, because we have demonstra(on purposes. PRINCE2® is a Registered Trade Mark of the AXELOS. The Swirl logo is a Trade Mark of the AXELOS. © Management Plaza P2P-SampleProject-EN Version V01.14 – Premium Edition 46
Project Initiation Documentation (PID) Pre-Project Stage 1 (initiation) Stage 2 Stage 3 (Final) Processes Star.ng up a Project Ini.a.ng a Project Controlling a Stage Controlling a Stage Managing a Stage Boundary Managing a Stage Boundary Closing a Project Management Products Project mandate Risk Register, Quality Register, Issue Register Daily Log, Lessons Log Project Brief Project Product Descrip.on Project Management Team Structure Outline Business Case Ini.a.on Stage Plan Project Ini.a.on Documenta.on Four Strategy Docs Tailoring Product Descrip.ons(s) Project Plan Project Controls Business Case Benefits Review Plan Next Stage Plan PBS The PID is a collec(on of a number of documents, it defines the whole project and provides a basis for its management (it acts as a contract between the Project Board and the Project Manager) Note: this diagram only contains the sample documents of this training course, rather than all the necessary documents in each stage. PRINCE2® is a Registered Trade Mark of the AXELOS. The Swirl logo is a Trade Mark of the AXELOS. © Management Plaza P2P-SampleProject-EN Version V01.14 – Premium Edition 47
Page 1 and 2: y Management Plaza The Pen Projec
Page 3 and 4: About the authors Frank Turley has
Page 5 and 6: The Project Scenario PRINCE2® is a
Page 7 and 8: Pre-Project Starting up a Project P
Page 9 and 10: Project mandate Document: Project m
Page 11 and 12: Lessons Log Document: Lessons Log P
Page 13 and 14: Project Product Description (part o
Page 15 and 16: Project Product Description (part o
Page 17 and 18: Project Management Team Structure (
Page 19 and 20: Outline Business Case (part of Proj
Page 21 and 22: Project Brief Pre-Project Stage 1 (
Page 23 and 24: Initiation Stage Plan Pre-Project S
Page 25 and 26: Interested in our CBT for this “A
Page 27 and 28: Communication Management Strategy (
Page 29 and 30: Product Breakdown Structure (part o
Page 33 and 34: Product Description: Client List Do
Page 35 and 36: Risk Register Document: Risk Regist
Page 37 and 38: Benefits Review Plan Document: Bene
Page 39 and 40: Project Controls (part of PID) Docu
Page 41 and 42: Project Plan (part of PID) Document
Page 43 and 44: Business Case (part of PID) Pre-Pro
Page 45: Tailoring of PRINCE2 (part of PID)
Page 49 and 50: Dependencies Diagram (part of the n
Page 51 and 52: Schedule (part of the next Stage Pl
Page 53 and 54: Next Stage Plan Pre-Project Stage 1
Page 55 and 56: The first stage was ini(a(ng s
Page 57 and 58: Work Package Document: Work Package
Page 59 and 60: Issue Register Document: Issue Regi
Page 61 and 62: Issue Report Document: Issue Report
Page 63 and 64: Issue Register Document: Issue Regi
Page 65 and 66: Highlight Report Document: Highligh
Page 69 and 70: Dependencies Diagram (part of the n
Page 71 and 72: Schedule (part of the next Stage Pl
Page 73 and 74: Next Stage Plan Document: Next Stag
Page 75 and 76: Configuration Management Document:
Page 77 and 78: Configuration Item Record Document:
Page 79 and 80: End Stage Report Document: End Stag
Page 81 and 82: This is the last stage of the
Page 83 and 84: Quality Register Document: Quality
Page 85 and 86: Product Status Account Document: Pr
Page 87 and 88: Lessons Report (part of End Project
Page 89 and 90: Summary PRINCE2® is a Registered T
Page 91 and 92: Summary Pre-Project Stage 1 (initia
Page 93 and 94: Summary Management Plaza’s PRIN
Page 95 and 96: Recommended material: Introduction
Page 97 and 98:
Notes Page Notes PRINCE2® is a Re
Page 99 and 100:
Page 101:
show all

PRINCE2-SampleProject-Premium-MP847

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?