PRINCE2 Documents Flashcards
Project initiation documentation (PID)
The project initiation documentation gives the direction and scope of the project and (along with the stage plan) forms the ‘contract’ between the project manager and the project board.
The three primary uses of the project initiation documentation are to:
● ensure that the project has a sound basis before asking the project board to make any major commitment to the project
● act as a base document against which the project board and project manager can assess progress, issues, and ongoing viability questions
● provide a single source of reference about the project so that people joining the ‘temporary organization’ can quickly and easily discover what the project is about and how it is being managed.
Change management approach (PID)
To establish the target organizational state required for the project to meet its objectives together with the means by which the business will shift from the current state and through any interim states.
Communication management approach (PID)
To define and describe the means and frequency of communication with and receiving feedback from across the project ecosystem, supporting alignment and shaping of the project. It facilitates engagement with stakeholders through the establishment of a controlled and bidirectional flow of information.
Benefits management approach (PID)
The purpose of the benefits management approach is to define the benefits management actions and benefits reviews that will be established to ensure that the project’s outcomes are achieved and to confirm that the project’s benefits are realized.
Sustainability management approach (PID)
The purpose of the sustainability management approach is to define the actions, reviews, and controls that will be established to ensure that sustainability performance targets for the project are achieved.
Commercial management approach (PID)
The purpose of the commercial management approach is to describe the procedures, techniques, and standards to be applied and the responsibilities for effective commercial management.
This covers the approach to secure, service, and maintain all commercial agreements required for the project to be a success. This may include activities such as market engagement, procurement, and contract management.
Project management team structure (PID)
The purpose of the project management team structure is to define who is involved in the project, their relationships, and how they will work together. It may also include a description of relevant key personnel outside the project team.
Quality management approach (PID)
The purpose of the quality management approach is to describe the quality techniques and standards to be applied and the roles and responsibilities for achieving the required quality specifications and acceptance criteria during a project.
Risk management approach (PID)
The purpose of the risk management approach is to describe how risk will be managed on the project. This includes the specific procedures, techniques, standards, and responsibilities to be applied.
Issue management approach (PID)
The purpose of the issue management approach is to describe how issues will be captured and reported and explain how changes to the project baseline will be assessed and controlled.
Digital and data management approach (PID)
How digital technology will be used to support project management (for example, project controls) and project work (for example, the use of digital twins for design and construction).
How data and information will be created, used, and managed across the project ecosystem and through the project lifecycle and afterwards.
Role descriptions
The purpose of role descriptions is to describe the roles of those in the project management team and their specific responsibilities.
Project Log (PL)
The purpose of the project log is to capture the continually changing records of issues, lessons, products, quality, risk, and other formal/informal actions or events. The project log is dynamic in that it contains the current and historic record of project activities and progress.
Quality register (PL)
The purpose of the quality register is to summarize all quality management activities that are planned or have occurred. The quality register is used by the project manager and project assurance as part of reviewing progress.
Product register (PL)
The purpose of the product register is to list of all products required of a plan and the status of those products.