1. AXELOS. (2017). Managing Successful Projects with PRINCE2® (6th ed.). TSO (The Stationery Office).
Section 20.1, Purpose: "The purpose of the Project Initiation Documentation is to define the project, in order to form the basis for its management and an assessment of its overall success... The Project Initiation Documentation is a living product that should always reflect the current status, plans and controls of the project."
Section 20.4, Derivation and Format: "The Project Initiation Documentation is compiled during the initiating a project process... It is subject to formal change control and should be checked at stage boundaries (during a managing a stage boundary process) to see if any changes are required."
Appendix A, Section A.21, Project Initiation Documentation: This section lists the required composition, which includes the Business Case, Risk Management Approach, and Project Plan, all of which detail both positive and negative aspects (e.g., benefits vs. costs and risks).
2. Turner, J. R. (2014). The Handbook of Project-Based Management: Leading Strategic Change in Organizations (4th ed.). McGraw-Hill.
Chapter 10, Project Definition: Discusses the creation of a project definition report or PID. It emphasizes that this document must contain a thorough analysis of "constraints, assumptions, and risks" (p. 245) in addition to the project's objectives and scope, providing a complete picture for stakeholders to approve the project.
3. The Open University. (n.d.). M815: Project Management. Courseware.
Block 2, Part 3: Project start-up and initiation: The course materials, aligned with Association for Project Management (APM) and PRINCE2 standards, describe the PID (or equivalent Project Management Plan) as a document that is developed in the initiation phase and is updated through formal change control as the project progresses. It explicitly states the need to document risks, issues, and constraints.