|
== Project initiation documentation in terms of PRINCE2 ==
The project initiation documentation is a [[PRINCE2]] <ref>{{Cite web |last=Schwartz |first=Brenna |date=2023-07-26 |title=How to Create a Project Initiation Document (Template Included) |url=https://www.projectmanager.com/blog/project-initiation-document |access-date=2024-11-23 |website=ProjectManager |language=en-US}}</ref> term representing the plan of approach in project management. It is assembled from a series of other documents, including the [[business case]], the [[terms of reference]], the communication plan, the [[risk register]], the project tolerances, the [[project plan]], and any specific project controls or inspections as part of a departmental quality plan or common project approach. The project initiation documentation represents a detailed version of the basic project start-up document called the [[project brief]].
The project initiation documentation bundles together documentation to form the logical document that brings together all of the key information needed to start and run the project on a sound basis. It should be conveyed to all stakeholders and agreed and signed off by the [[Executive sponsor|business sponsors]]. In short, this is the, "who, why, and what", part of the project. It defines all major aspects of a project and forms the basis for its management and the assessment of overall success. The project initiation document builds upon the business case (if it exists) using the information and analysis data produced during initiation activities.<ref>[http://www.pmhut.com/project-initiation-and-the-project-initiation-document-pid Project Initiation and the Project Initiation Document] - ''Retrieved on June 3, 2010''</ref>
=== Quality plan ===
''Project quality plan'' is usually written by the IT quality assurance (ITQA) and identifies aspects which will be delivered as part of a project (''baselined project plan'', ''[[business requirements]]'' (BRS), ''[[Useuse case|use cases]]s'', ''[[High-level design|high level design]]'' (HLD), ''[[Software requirements specification|software requirements spec]]'' (SRS), ''test scripts'', ''test report'', ''post development review'' (PDR), ''stage assessments'' in a ''project quality plan''). The ITQA also determines when the ''end stage assessment'' (ESA) will be taking place. These are basically checkpoints during the life of the project which ensure that a quality product is being delivered. ESA's implies the meeting where considering the baselined project plan to ensure that it is up to date and on [[Schedule (project management)|schedule]], project management reports, project workstream checkpoint reports, team meeting minutes, actions and agenda, [[Project risk management|project risk]] and [[Issue log|issues log]], and a quality plan tip.<ref>Project Quality Plan, http://www.my-project-management-expert.com/writing-a-project-initiation-document-quality-plan.html</ref>
=== Initial project plan ===
|
