The Project Initiation Document (PID) defines the project and provides the basis for its authorization and progress. It answers key questions about the project's objectives, stakeholders, timelines, and deliverables. The PID establishes the project's scope, quality plans, governance structure, risks, and controls to manage the project. It serves as the basis for measuring the project's delivery and success.
The Project Initiation Document (PID) defines the project and provides the basis for its authorization and progress. It answers key questions about the project's objectives, stakeholders, timelines, and deliverables. The PID establishes the project's scope, quality plans, governance structure, risks, and controls to manage the project. It serves as the basis for measuring the project's delivery and success.
The Project Initiation Document (PID) defines the project and provides the basis for its authorization and progress. It answers key questions about the project's objectives, stakeholders, timelines, and deliverables. The PID establishes the project's scope, quality plans, governance structure, risks, and controls to manage the project. It serves as the basis for measuring the project's delivery and success.
Template & Notes Project Initiation Document Template Version 1 Controlled Start Up: Project Initiation Document (PID) The Project Initiation Document is the basis on which the project is authorised and allowed to progress. It will also be the basis on which the project is measured both on delivery timescales and the content and quality of the deliveries. It is one of the most important documents produced by the project. It answers the questions !hat is the Project aiming to achieve !hy it is important to achieve it !ho is going to be involved in managing and delivering it "ow and when it will happen The PID can be a complete document in its own right or it can be a summary document# which points to separate documents# which are part of the overall PID. Further support $or further advice and support on Project %anagement please contact www.Pmadvice.co.u& Project Initiation Document Template Version 1
PR!"CT INITI#TIN DCU$"NT Document Status: %ersion Num&er: Created: Printed: Project Initiation Document Template Version 1 Re'ie( Re'ie(ed &) Name r*anisation Date #ppro'al #ppro'ed &) Name r*anisation Date Document +istor) %ersion Summar) o, Chan*es Document Status Date pu&lished Project Initiation Document Template Version 1 T#-." F CNT"NTS /0 PURPS" 10 -#C23RUND 40 PR!"CT D"FINITIN 50 INITI#. -USIN"SS C#S" 60 PR!"CT R3#NIS#TIN STRUCTUR" 70 C$$UNIC#TIN P.#N 80 PR!"CT 9U#.IT: P.#N ;0 INITI#. PR!"CT P.#N <0 PR!"CT T."R#NC"S /=0 PR!"CT CNTR.S //0 ">C"PTIN PRC"SS /10 INITI#. RIS2 .3 /40 CNTIN3"NC: P.#NS /50 PR!"CT FI.IN3 STRUCTUR" Project Initiation Document Template Version 1 /0 PURPS" This document should adequately define the project and provide a basis for its management and assessment of its overall success. It must demonstrate that the project has a fundamentally sound basis before gaining project board commitment. 10 -#C23RUND Refer to Project Brief Explain the context of the project and what it was that suggested the need for it. State whether the project will be a stand-alone activity to fulfill a particular business requireent or whether it is part of a larger prograe. 40 PR!"CT D"FINITIN 40/0 PR!"CT -!"CTI%"S Explain what the project is trying to achieve by stating its objectives! which should be easurable and defined in ters of the project"s ajor deliverables! effort! cost! tolerances and business benefits expected. 4010 D"FIN"D $"T+D F #PPR#C+ State or insert the initial ethod of approach! which should have been considered and established during the startup process. #or exaple! will the solution be$ Bought %off the shelf" %&ade to easure" 'eveloped in-house (ontracted to third parties Based on an existing product %Built fro scratch" Based on specific technologies) 4040 PR!"CT D".I%"R#-."S #ND?R D"SIR"D UTC$"S 'escribe the ain project deliverables and outcoes! i.e. the actual products that the project will deliver to the end user. 'o not attept to specify how the products will be delivered at this tie. Project Initiation Document Template Version 1 4050 PR!"CT SCP" 'escribe the ajor deliverables of the project along with specific products which are not part of the project. 'escribe the ajor dependencies *which ipact on the project during its life+ and interdependencies which will exist after ipleentation. 4060 CNSTR#INTS 'escribe the constraints within which the project ust operate. #or exaple there ay be constraints on the aount of resources available to the project or the location of the project tea. 4070 ">C.USINS 'tate here which products are e(cluded from the project# including any products that may be added at a later date. 4080 INT"RF#C"S 'escribe any interfaces with the project both internal and external to the organisation including any lin,s to other projects or prograe*s+. 40;0 #SSU$PTINS -ist any assuptions that are being ade which will have a bearing on the projects progress i.e. will it be assued that particular equipent or personnel will be available when required) 50 INITI#. -USIN"SS C#S" .nsert the refined Business (ase based on the /utline Business (ase in the Project &andate! Project Brief and the Project Plan. 0ou should also expand on the ris,s in the Project Brief and include any new ris,s found since. 60 PR!"CT R3#NIS#TIN STRUCTUR" Show the /rganisation Structure including role descriptions and responsibilities. 1overnance and decision a,ing processes should be clearly defined and understood. 70 C$$UNIC#TIN P.#N Project Initiation Document Template Version 1 .nsert or a,e reference to the (ounication Plan! which should include sta,eholder engageent. 80 PR!"CT 9U#.IT: P.#N .nsert the Project 2uality Plan which should specify how the quality expectations of the custoer will be et. 3he plan should include$ (ustoer"s 2uality Expectations 4 5 stateent fro the custoer about the quality expected fro the final product. 5cceptance (riteria 4 5 easurable definition of what ust be done for the final product to be acceptable to the custoer. 2uality Responsibilities 4 3he roles and naes of those responsible. 2uality Standards which apply to this Project 4 5ny applicable standards processes or procedures to which the project ust coply. 2uality (ontrol and 5udit Processes 43he ethod by which products will be tested against their quality specifications. (hange &anageent Procedures 4 3he ethod by which change anageent will operate. ;0 INITI#. PR!"CT P.#N .nsert or a,e reference to the .nitial Project Plan. <0 PR!"CT T."R#NC"S 'efine the agreed project tolerances! such as level 6 ilestones ay deviate plus or inus 6 wee, without need for escalation or project spend can increase by up to 678 or 96777.77 *which ever is the saller+ before need for escalation. /=0 PR!"CT CNTR.S 'efine the level and frequency with which Project &anageent controls will be applied e.g. :ighlight Reports and the reporting and onitoring systes which will apply. //0 ">C"PTIN PRC"SS 'escribe what the procedure will be should an exception situation arise within the project! i.e. where it is forecast that there will be a deviation between any agreed tolerance levels. /10 INITI#. RIS2 .3 .nsert or a,e reference to the .nitial Ris, -og. Project Initiation Document Template Version 1 /40 CNTIN3"NC: P.#NS 'escribe plans to deal with the consequences of any identified ris,s that aterialise within the project. /50 PR!"CT FI.IN3 STRUCTUR" 'etail how the various eleents of inforation and deliverables produced by the project are to be filed and retrieved. Project Initiation Document Template Version 1