Acceptance Criteria
A prioritized list of criteria that the final product(s) must meet before the customer will accept them (a measurable definition of what must be done for the final product).
A list of criteria the final output of the project must satisfy for the customer to accept it. Just imagine a list of criteria arranged in order of importance in a spreadsheet and each entry should be discussed and confirmed by both the customer and the supplier.
Throughout the project, the acceptance criteria can be refined and changed, but in the end only when all the criteria are met and each box ticked off can the project can be closed.
Baseline
A snapshot; a position or situation that is recorded. A baselined product is a reminder of the original state and as a comparison against the current position. Products that have passed their quality checks and are approved are baselined products.
Once a product is baselined, it becomes a fixed reference for the following versions of the same product.
For example, the Project Plan is defined, agreed and signed off at the start of the project. The Project Plan will be updated during the project to show what has been done.
The Project Board can compare the baselined Project Plan with the current project plan to see how well the project is going compare to the original expectations.
Another example: a mailing list for an event may have been approved, so this mailing list will be baselined, given a version number and cannot be changed.
If changes do need to be made, then a new version of the mailing list will be created as the baseline version cannot be changed.
Business Case
Information that describes the justification for setting up and continuing a PRINCE2 project. It provides the reasons (and answers the question: ‘Why?’) for the project.
An outline Business Case should be in the project mandate and can be updated in Project Brief. A fuller version should appear in the Project Initiation Document.
A document that explains the reasons for the project in terms of costs, risks and benefits. It explains in detail why the project should be done, why the final outcome is desired.
During the project annual whenever a risk appears, the odds should be weighed against the Business Case to check if the benefits still exist within the expected time and cost constraints.
For example, if a company is running a project to develop and implement a new CRM application, the Business Case should include the improved efficiency for client management so more clients could be handled within a certain period of time.
Another example: During the project an important new requirement has been added to the project.
A new feature will be added to allow users to see if items they wish to order are already in stock and this connection to the stock application will cost an extra €30,000. So the business case must be updated to reflect this increase in costs and see if the project is still worth doing.
Communication Management Approach
A description of the means and frequency of communication between the project and the project’s stakeholders.
A description of the flow of information between the project and its stakeholders. It defines the method and frequency of the information exchange. During the start-up, the traffic of communication and reporting may be higher.
The Communication Management Approach provides an organized approach to deliver reports on a timely basis to those who need the information for decision making and/or the purposes.
E.g.: The Communication Management Approach document may show that it has been agreed that the Project Manager will send a two page Highlight Report to the Project Board every two weeks on a Thursday morning with a certain format.
Customer
The person or group who commissioned the work and will benefit from the end results.
The customer will specify the desired outcome of the project, will be the owner of the final product of the project, will be representative to those who are going to use the final product and will probably pay for the project.
Remember PRINCE2 is based on a Customer/Supplier environment and both will be represented in the Project Board.
The term Customer can also refer to both User and Business interests.
Output
A specialist product that is handed over to a user. Note that management products are not outputs but are created solely for the purpose of managing the project.
Outputs refer to the products that are delivered to the customer/user and they are the reason why the project is done.
There are two kinds of products in a PRINCE2 project which are Specialist products and Management products. Specialist products are the outputs of the project and are given to the users.
Management products are created for the purpose of managing the project, e.g.: Project Plan, Business Case. These are never given to users.
End Project Report
A report given by the Project Manager to the Project Board that confirms the handover of all products and provides an updated Business Case and a Project Assessment.
The End Project Report is the Project Manager’s report to the Project Board that confirms the delivery of outputs to the customer, an overview of what went good and not so good, a review of the benefits compared to the expected benefits that were listed in the Business Case, and a review of how well the project went according to the Project Plan.
It can also confirm that products have been accepted by the customer.
End Stage Report
A report given by the Project Manager to the Project Board at the end of each management stage of the project. This provides information about the project performance during the stage and the project status at stage end.
The Project Manager’s report to the Project Board that provides information on project performance during each stage and the overall project status up to that point. It will also include a review of the benefits reached so far and a review of the Issues and Risks.
An End Stage Report should contain a forecast for the next stage, this will help the Project Board to decide whether to continue the project or not. This can be a structured document, email or a few slides.
Executive
The single individual with overall responsibility for ensuring that a project meets its objectives and delivers the projected benefits.
This individual should ensure that the project maintains its business focus, that it has clear authority and that the work is actively managed. The Executive is the Project Board chairperson, representing the customer, and is the owner of the Business Case.
The person responsible to ensure the project satisfies its goals and delivers the intended benefits.
The Executive is the chairperson of the Project Board, represents the Customer and is responsible for the Business Case. He or she is also responsible for making sure the project runs within the framework of the Business Case and has the final say in the Project Board.
Follow-on Action Recommendations
A report that can be used as input to the process of creating a Business Case/Project Mandate for any follow-on PRINCE2 project and for recording any follow-on instructions covering incomplete products or outstanding Project Issues.
A report created by the Project Manager at the end of a project that puts together recommendations on how to handle incomplete outputs, ongoing issues which are taken from the Issue Register and existing risks. E.g.: unfinished work, possible activities that should be done for some products.
As you can imagine, this can be very important for the persons who are going to take over the maintenance of the products.
Highlight Report
A time-driven report from the Project Manager to the Project Board on stage progress.
A report on the stage progress, prepared regularly by the Project Manager for the Project Board.
The frequency for this report is indicated in the Communication Management Strategy, e.g.: It may be agreed that the Project Manager will send this every two weeks on a certain day and with a specific format which can be a 2 or 3 page overview.
The report can confirm that the stage runs within tolerances and the Project Manager can also point out any foreseeable problems.
Issue
A relevant event that has happened, was not planned and requires management action. It can be any concern, query, request for change and suggestion or off-specification raised during a project. Project issues can be about anything to do with the project.
Any event related to the project that has already happened and requires the intervention of the higher management.
All issues that need to be handled formally will be first examined and then classified into one of three types of issues and then entered into the Issue Register.
The three categories for an issue are: 1) A request for change, 2) An off-specification (which is something that supplier was not able to do as planned) and 3) and a problem or a concern.
Issue Register
A register used to capture and maintain information on all of the issues that are being managed formally. The Issue Register should be monitored by the Project Manager on a regular basis.
A log that captures and keeps track of all formal issues. It is regularly monitored by the Project Manager throughout the project. Just imagine a spreadsheet where each line is an issue and there are columns for Issue ID, Issue Type, Date Raised, Raised By, Description, Current Status and Close Date.
Lessons Report
A report that documents any lessons that can be usefully applied to other projects.
The purpose of the report is to provoke action so that the positive lessons from a project become embedded in the organization’s way of working and that the organization is able to avoid the negative lessons on future projects.
A document that lists the lessons gained during the project. It helps to avoid possible mistakes and to repeat positive actions in future projects.
Any important lessons that can be applied to future projects should be listed in the Lessons Report.
This report is created by the Project Manager using the information from the Lesson Log and given to Project Board always at the end of the project. In large projects, it can also be created at the end of a stage.
Product
An input or output, whether tangible or intangible, that can be described in advance, created and tested. PRINCE2 has two types of products – management products and specialist products.
Any input to a project or output produced during the project. A PRINCE2 project creates two kinds of products, specialist product and management products.
The creation of the specialist products is the reason that the project was started and these are the products that will be given to the users.
The management products are documents used solely for the purpose of communication among the project management team. E.g.: Project Plan, Business Case. So the Users are only interested in the specialist products.
Product-based planning
A technique leading to a comprehensive plan based on creation and delivery of required outputs. The technique considers prerequisite products, quality requirements and the dependencies between products.
A PRINCE2 technique used to create a detailed plan that focuses on the required products before even thinking about activities. There are four steps in Product Based Plan:
Step 1: Write the Project Product Description: Just imagine the information you might see on a web site about a laptop: Laptop Overview, Laptop Specifications and Features including information on Quality.
Step 2: Create Product Breakdown Structure: This is a sorted list in a diagram of all the parts that make up the laptop such as keyboard, mouse, memory, motherboard, hard-drive and case. You may put keyboard & mouse under a branch labeled as Input devices.
Step 3: Write a Product Description for each part mentioned in the Product Breakdown structure: For example, Hard-drive: overview information, specifications, features and quality information.
Step 4: Create Product flow diagram: This defines the sequence in which the Project Product will be created. E.g.: A new Laptop prototype – You may decide to start with products that are manufactured in house and add products that are out sourced.
The flow diagram must represent the sequence of how the product will be created.
Product Breakdown Structure
A hierarchy of all the products to be produced during a plan (during a project).
A ranking list of all the products defined in the plan. The plan is broken down into the its major products and these products are listed in priority according to their dependencies.
E.g.: A Laptop Prototype: You would list and link all the parts that make up the laptop in a diagram such as keyboard, mouse, memory, motherboard, hard-drive and case.
You might place Keyboard & Mouse Pad under a branch Input devices, and you may have another branch for external connection adapters, for example Video, USB, Power, Network, Earphone.
This can either be a top down diagram or you can use a Mind-map.
Product Checklist
A list of the major products of a plan, plus key dates in their delivery.
A list of all the major products to be produced, along with their dates of delivery.
Imagine a spreadsheet with a number of columns like Product ID, Product Title, Product Description Approved date, Draft Ready date – Plan & Actual, Quality Check date – Plan &
Actual and Approved date – Plan & Actual.
This checklist is a great way to see how the project is progressing and some Project Managers use this as their main document for this purpose.
Product Description
A description of a product’s purpose, composition, derivation and quality criteria. It is produced during the time of planning, as soon as possible after the need for the product is identified.
Information on the product’s purpose, composition, derivation and quality criteria. A product is defined as soon as its need is identified. Technical products as well as management products should have product descriptions.
E.g.: Think of a Product Description for the Hard Drive of a Laptop. You will have an Overview description, Features, Specifications, Quality requirements & how this will be tested and a list of parts it may have.
Product Flow Diagram
A diagram showing the sequence of production and inter dependencies of the products listed in a Product Breakdown Structure. (It shows what has to be produced 1st, 2nd, 3rd and so on.)
A diagram showing the order of production and the prerequisites for each product defined in the Product Breakdown Structure.
E.g.1: Imagine you are building a new prototype Laptop: The Product Flow Diagram may show that you start with the bottom casing, and then add the metal linings, the motherboard and the rest of the parts in sequence until the laptop is built.
E.g.2: Think of an instruction diagram that comes with a flat pack piece of furniture from IKEA; this is also a sequence of steps to create a product.
Project Assurance
The Project Board’s responsibilities to assure itself that the project is being conducted correctly. Each of the Project Board members have a specific area of focus for Project Assurance, namely business assurance for the Executive, user assurance for the Senior User, and supplier assurance for the Senior Supplier.
The Project Board is responsible for monitoring the project’s performance in the user, supplier and business areas. To achieve this, the Board may decide to delegate its assurance functions to another entity to make sure the project runs smoothly.
The best way to explain Project Assurance is to look at why we need Project Assurance.
The Project Manager may be hiding information or providing misinformation to the Project Board, therefore the Project Board need an independent view of how the project is really going, so that they can check if the products reported to be created have actually been created.
This is Project Assurance.
Project Brief
A statement that describes the purpose, time, cost and performance requirements, and constraints for a project. It is created pre-project during the Starting up a Project process and is used during the Initiating the Project process to create the Project Initiation Documentation and its components.
It is superseded by the Project Initiation Documentation and not maintained.
A document that contains the following information collected during the Pre-project process “The Starting up a Project Process”: The Project Definition which includes background information, time, cost, quality & scope; an Outline of the Business Case; Project Description; Project Team Structure and Project Approach.
It is used by the Project Board to decide if they will continue with the initiation stage of the project and therefore spend money. This is their first decision. It is not updated during the project.
Project Initiation Documentation
A logical set of documents that brings together the key information needed to start the project on a sound basis and to convey that information to all concerned with the project.
A set of documents that contain essential information to start the project; in other words the documents that were created during the Initiation Stage that describes how the project will be done in detail. It includes the Project Plan, Business Case, 4 Strategy Documents, Risk
Register and Team Structure among others. The Project Board reviews the Project Initiation Documentation in order to authorize the start of the project. It is also used to communicate the project to its stakeholders.
The documents in the Project Initiation Documentation are subject to change throughout the project. After each change every document is baselined for future comparison. A good way to think about the contents of a PID is to think of the Themes.
Project life cycle
The period from the start-up of the project to the acceptance of the project product.
The time between the start of the project and the acceptance of the product or the close of the project. Therefore, follow up maintenance and support is not part of the project life cycle but happens after the project has closed.
Project management
The planning, monitoring and control of all aspects of a project and the motivation of all those involved in it to achieve the project objectives on time and to the specified cost, quality and performance.
The conducting of the project by planning, delegating, monitoring and controlling all sides of the project in view of the project objectives by creating the project plan and then running the project according to this plan. This includes the management of the human and nonhuman resources within the limits of time, cost and quality.
Project management team
Covers the entire management structure of Project Board, Project Manager, including Team Managers, Project Assurance and Project Support roles.
Defines the total management structure of the project from top to bottom, from the Project Board to the Project Manager to the Team Managers and the support staff.
It is a temporary structure solely established to manage the project to a successful conclusion. The Project Management Team is disbanded at the end of the project.
Project Manager
The person given the authority and responsibility to manage the project on a day-to-day basis to deliver the required products within the constraints agreed with the Project Board.
The person appointed by the Project Board to manage the daily progress of the project to deliver the end product within the limits set by the Board, in other words run the project according to the project plan as efficiently as possible, for example, by looking for opportunities to speed the project up and reduce costs.
Project mandate
Information created externally to the project that forms the terms of reference and is used to start up the PRINCE2 project.
Information provided by the upper management outlining what is desired from the project. This is an external document and is used as an input for the Starting up a Project process.
This can be an email, internal memo or a structured document. The project mandate can contain some basic information on the business case, project tolerances, reasons for the project, who the executive should be and risk information.
The information in the project mandate document is expanded into the Project Brief in the Starting up a Project process.
Project Plan
A high-level plan showing the major products of the project, when they will be delivered and at what cost. An initial Project Plan is presented as part of the Project Initiation Document.
This is revised as information on actual progress appears. It is a major control document for the Project Board to measure actual progress against expectations.
A control document for measuring progress. It shows the required products of the project, their delivery dates and costs as well as the quality objectives and how these will be achieved.
It is not just a Gantt chart but contains product descriptions, product breakdown structure, responsibilities, how stages are used, lessons, how the project will be controlled, tolerances, and quality information.
Quality Management Approach
A strategy defining the quality techniques and standards to be applied, and the various responsibilities for achieving required quality levels during a project.
A plan of action that defines the quality requirements and the control methods for all the products in the project.
This document also confirms how the quality systems from the customer and supplier are going to be applied in the project. This is created at the Initiation Stage and becomes a part of the Project Initiation documentation.
Quality
The totality of features and inherent or assigned characteristics of a product, person, process, service and/or system that bears on its ability to show that it meets expectations or satisfies stated needs, requirements or specifications.
A product’s ability to satisfy its intended properties by meeting expectations, requirements and specifications.
One of the first questions you should ask when defining the Project is what quality is expected, for example, if you are developing a CRM system, some quality questions would be: how easy should the product be to use, what percentage of features should work when launched (this could be 99%), the time delay to carry out specific activities like a search.
Documenting the quality requirements really helps to define the project product and therefore the project.
Risk
An uncertain event or set of events that, should they occur, would have an effect on the achievement of objectives. A risk is measured by a combination of the probability of a perceived threat or opportunity occurring, and the magnitude of its impact on objectives.
An event that, if it occurs, may have a positive or negative effect on the project’s objectives. Risks are constantly reviewed during the project using the Risk Register. As projects are unique in nature, they will have risks and these need to be managed.
Risk Register
A record of identified risks that are faced by an organization and its exposure to those risks.
A log of possible risks that the project faces, this is kept up to date during the project by the Project Manager. Imagine a spreadsheet with the following columns: Risk ID, Risk Author,
Date Registered, Risk Category, Risk Description, Impact, Proximity, Risk Status, Risk Owner.
Senior Supplier
The Project Board role that provides knowledge and experience of the main disciplines involved in the production of the project’s deliverables. The Senior Supplier represents the supplier interests within the project and provides supplier resources.
Senior Supplier is a Project Board role that represents the interests of those who are going to deliver the desired products. The supplier can be an in-house department or an external company.
Their main concern throughout the project is “Can it be done?” and can it be done within the agreed time and costs and quality.
Senior User
The Project Board role accountable for ensuring that user needs are specified correctly and that the solution meets those needs.
The Senior User is a Project Board role that represents the future users of the project’s product. They represent the Users’ Interests. The Senior User is responsible to ensure that the product satisfies the quality and functionality requirements of the user and their main concern throughout the project is Will it Work as expected.
Stage Plan
A detailed plan used as the basis for the project management control throughout a stage.
A Stage Plan is created by the project manager and has a similar structure to the Project Plan but it differs in two ways:
1) The project plan is very high level while the stage plan is much more detailed for example, it can show what has be done day to day.
2) The project plan lists all products that will be produced during the project while the stage plan is just focused on the products that will be created during a particular stage.
Stages (Management Stages and Technical Stages)
Management Stage: The section of a project that the Project Manager is managing on behalf of the Project Board at any one time, at the end of which the Project Board will wish to review progress to date, the state of the Project Plan, the Business Case and risks, and the next Stage Plan in order to decide whether to continue with the project.
Technical Stage: A method of grouping work together by the set of techniques used, or the products created. This results in stages covering elements such as design, build and implementation. Such stages are technical stages and are a separate concept from management stages.
There are two types of stages Management Stages and Technical Stages.
Management Stages: A PRINCE2 a project is divided into stages and each stage is separated by a decision from the Project Board to continue or not to the next stage.
A Technical Stage is a grouping of a certain set of techniques used in the development of the product.
One difference is that Management Stages can never overlap while the Technical Stages can overlap, e.g.: Designing, Building and Training may overlap.
So how can the Project Manager manage Technical Stages from PRINCE2?
The PRINCE2 Project Manager uses Management Stages so they see which products are created in the Technical Stages and place these in the corresponding Management Stage.
E.g.: There may be a Training Technical stage that spans two Management Stages and the final output is approved training material. So the Project Manager looks to see how they can divide this work into two separate Management Stages.
A solution can be to split the product into 2 products, a first product could be draft training and the complete product could be the approved training material.
Therefore the draft training product can be produced in the first Management Stage and Approved Training Material product is produced in the next Management Stage. See page 106 for more information on this.
Team Plans
An optional level of plan used as the basis for a team management control when executing Work Packages.
A Team Plan is created by the Team Manager to plan the execution of the activities which are agreed with the project manager. Team Plans are optional. These activities are grouped together into Work Packages and a Team Plan can be for one or more Work Packages.
PRINCE2 does not provide a format for Team Plans and the Team Manager can use a simple task list in excel, MS Project or create a plan that looks like a stage plan. In most projects the Project Manager may request to review the Team Plan to get a better idea of how the work will be done.
Tolerance
The permissible deviation above and below a plan’s estimate of time and cost without escalating the deviation to the next level of management. Separate tolerance figures should be given for time and cost.
The estimated time and cost allowance in the project plan to tolerate possible deviations without the need of the Project Board intervention. Imagine if there was no tolerance in a project, then every small issue that the Project Manager would have, they would contact the Project Board, this would happen many times each day and the Project Board would end up running the project.
The Project Board members are very busy and don’t want to be bothered each hour by the PM, so they give them tolerances for time, cost, quality, benefits, sustainability, scope and risk and let the Project Manager get on with it.
They are told to alert the Project Board only if it is forecast for the project to go above one of these tolerances.
User(s)
The person or group who will use the final deliverable(s) of the project.
The end users of the project’s final deliverable; they will receive the benefits of the project.
Work Package
The set of information relevant to the creation of one or more products. It will contain a description of the work, the Product Descriptions(s), details of any constraints on production and confirmation of the agreement between the Project Manager and the person or Team Manager who is to implement the Work Package such that the work is done within these constraints.
Work Packages are a way for the Project Manager to group work activities together and assign work to a team or Team Manager to produce one or more products.
A Work Package is therefore a set of information about one or more required products. A Work Package can contain: Work Package description, product descriptions, techniques to be used, tolerances, date of agreement between PM and TM, how the TM will report to the PM and Quality information.
This course is DEPRECATED
The old PRINCE2 6th Edition Foundation and Practitioner syllabus was upgraded in 2024. Check out the brand NEW PRINCE2 7th Edition Masterclass, covering all the current syllabus, training material and online exam benefits HERE

Your Route To PRINCE2 6th Edition Practitioner
Study PRINCE2 6 Foundation and Practitioner Exams with our famous on-line course with streaming HD Video Lessons, study guides and mock exams. In the last fifteen years we have had 6,000+ Academy students successfully transform their careers as PRINCE2 Practitioners.
