PRINCE2-SampleProject-Premium-MP847

More documents

Recommendations

Info

Daily Log Document: Daily Log Project: Pen Project Author: Project Manager Date: ID Date of Entry Descrip.on Responsible Target Date Result 01 2013-‐06-‐17 When we were preparing the list of potenDal suppliers, I realized that one of them is owned by an old friend of mine (conflict of interest) Project Manager 2013-‐06-‐17 I believe I’m capable of evaluaDng the suppliers honestly. I’ve also informed the project board about this conflict of interest. 02 2013-‐06-‐18 A sales man from one of the potenDal suppliers came to our office today to meet me, while I was in a meeDng. He leg me a gig and leg the building before I could meet him. This can be considered a bribery. Project Manager 2013-‐06-‐18 I returned the gig and put the supplier in the company’s black list. 03 2013-‐06-‐22 Daniel Ross, who’s responsible for the logo, is asked to prepare its vector version, but he doesn’t seem to know how. Project Manager 2013-‐06-‐23 He’s replaced by Julie Gates, who’s more expert on graphic design. We’ve lost two days, but the acDvity has a lot of float and we won’t get into any problems. 04 2013-‐06-‐25 The communicaDon between Julie Gates and the supplier needed for the design of the logo is not effecDve enough. It takes a lot of Dme for each version to be reviewed and the new version is released. Project Manager 2013-‐06-‐25 Julie Gates is asked to meet with the responsible person in the supplier company to discuss the requirements of the logo and to prepare it together. 05 2013-‐06-‐26 I had a meeDng with the selected supplier to discuss the price, when we also talked about the quality, and especially about the quality of the printed logo and the best technique to use for this. Project Manager The Daily Log is used to capture issues and risks in the Star(ng up a Project process AOer that, it is used as a (private) daily journal for all informa(on by the Project Manager Note: the content of this sample Daily Log belongs to next stages of the project 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 12
Project Product Description (part of Project Brief) 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 Daily Log, Lessons Log Project Brief Project Product Descrip.on The Project Product Descrip(on defines what the project must deliver in order to gain acceptance. It usually defines the scope, requirements, quality expecta(ons, acceptance criteria, acceptance method, and acceptance responsibili(es. 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 13
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: Lessons Log Document: Lessons Log P
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 31 and 32: 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 and 46: Tailoring of PRINCE2 (part of PID)
Page 47 and 48: Project Initiation Documentation (P
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 67 and 68:
Product Breakdown Structure (part o
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?