• Six aspects of project performance to be managed
• Definition of a project
• Four integrated elements of principles, themes, processes and the project environment upon which PRINCE2 is based
• Customer / supplier context of a PRINCE2 project
• Benefits of using PRINCE2 Seven principles
• Characteristics of a project

• Definition of project output, an outcome, a benefit and a dis-benefit
• The purpose of the Business Case theme
• The purpose of a: Business Case
• Benefits Review Plan
• Identify outputs, outcomes, benefits, and dis-benefits

• oles within the Organisation the
• The purpose of the Organisation theme
• The three project interests and how these are represented within the three levels of the project management team structure
• The responsibilities and characteristics of the role:
• Project Board
• Project Manager
• Project Assurance
• Change Authority
• Team Manager
• Project Support
• What a stakeholder is
• The purpose of the Communication Management Strategy

• Recall the recommended quality review team roles
• The purpose of the Quality theme
• The difference between Quality Assurance and Project Assurance
• The objectives of the quality review technique
• The difference between quality planning, quality control, and quality assurance
• The difference between customer’s quality expectations and acceptance criteria
• The purpose of a:Project Product Description
• Product Description
• Quality Register
• Quality Management Strategy

• Levels of plan recommended by PRINCE2
• Four tasks of product-based planning
• The purpose of the Plans theme
• The levels of plans, their purpose and the interrelationship between the:
• Project Plan
• Stage Plans
• Team Plans
• Exception Plan
• The tasks within the product-based planning technique

• The definition of risk and the difference between a threat and an opportunity
• The recommended risk response types and whether they are used to respond to a threat or an opportunity
• The difference between a risk owner and a risk actionee
• The purpose of the Risk theme
• The steps within the recommended risk management procedure. This should include:
• Identify the context and therefore the influences on a project’s Risk Management Strategy
• Identify the threats and opportunities that may affect a project’s objectives
• Estimate risks to assess their probability, impact, and proximity
• Evaluate the net effect of all risks on a project when aggregated together
• Plan risk management responses
• Implement planned risk management responses, identifying an appropriate risk owner and/or risk actionee
• Communicate information related to risks, both within the project and externally to stakeholders
• The purpose of a risk budget
• The risk probability, risk impact, and risk proximity
• The difference between cause, event, and effect when expressing a risk
• The purpose of a:
• Risk Management Strategy
• Risk Register
• The concept of risk appetite and risk tolerance

• Three types of issues
• Five typical activities of configuration management
• The purpose of the Change theme
• The purpose of a change budget
• The purpose of a:
• Project Plan
• Stage Plans
• Team Plans
• Exception Plan
• The steps in the recommended issue and change control procedure

• Lines of authority and reporting between the four levels of management
• The difference between event-driven and time-driven controls
• The purpose of the Progress theme
• The concept of management stages and the difference between management and technical stages
• The factors to consider in identifying management stages
• Tolerance(s): when and how tolerances are set, and exceptions reported, in which management products tolerances are documented and how management by exception applies to the different levels of management
• The purpose of a:
• Daily Log
• Lessons Log
• Work Package
• The purpose of a:
• End Stage Report
• End Project Report
• Lessons Report
• The purpose of a:
• Checkpoint Report
• Highlight Report
• Exception Report

• The purpose of the SU process
• The objectives of the SU process
• The context of the SU process
• The purpose of a Project Brief

• The purpose of the DP process
• The objectives of the DP process
• The context of the DP process

• The purpose of the IP process
• The objectives of the IP process
• The context of the IP process
• The purpose of a Project Initiation Documentation (PID)

• The purpose of the CS process
• The objectives of the CS process
• The context of the CS process

• The purpose of the MP process
• The objectives of the MP process
• The context of the MP process

• The purpose of the SB process
• The objectives of the SB process
• The context of the SB process

• The purpose of the CP process
• The objectives of the CP process
• The context of the CP process

• The purpose of the CS process
• The objectives of the CS process
• The context of the CS process

• The purpose of the MP process
• The objectives of the MP process
• The context of the MP process

• The purpose of the SB process
• The objectives of the SB process
• The context of the SB process

• The purpose of the CP process
• The objectives of the CP process
• The context of the CP process

• Project Managers
• Aspiring Project Managers
• Project Board members
• Product Delivery Managers
• Project Support Staff
• Operational Line Managers
• Team Leads / Team Managers

The PRINCE2 Foundation credential does not have an expiry period, and the certification is valid for life. Whereas, the PRINCE2 Practitioner certification is only valid for 5 years.

• Instructor-led Classroom Training
• Instructor-led Online Training
• On-site Group Training
• Focused 1-to-1 Training