Project initiation documentation: Difference between revisions

Revision as of 09:04, 7 June 2019

Revision as of 09:11, 7 June 2019

Line 81:

Specifying the importance of the project, Project Initiation Documentation identifies that it is the contract between the project management and sponsor. The aim of PID is understanding the premises of the project. The correct format of PID represents the understanding of the background, objectives and benefits. A good project manager is not only interested in delivering an output or a capability to their customer, but interested in the wider context and the benefits that this capability will ultimately bring about. PID identifies what is in scope within the project with the use of [[flow diagram]]s and [[Product Breakdown Structure]]s. The pivotal role plays the identification of responsibilities, which implies roles of project manager, [[team leader]], sponsor, [[Suppliers|supplier]], user representative, stakeholders and members of [[steering committee]].<ref name=":0" />

There are key aspects which need consideration before starting a [[project]] and creating a Project Initiation Document, such as: how will the project be delivered? What type of approach: variegates techniques ( e.g. [[Waterfall model|waterfall]], [[Agile software development|agile methodology]])? What ways of communication with stakeholders, keeping on top of risks, issues and changes.

For a PID it is sufficient to include the place, which emphasize on main phases and activities of the project.