Cheat sheet
PRINCE2 7 Foundation Cheat Sheet
Key Concepts
- 3% of exam
- Exam Mechanics Five Integrated Elements Seven Performance Aspects Delivery Approaches + Definitions Practice vs Process
Principles
- 8% of exam
- Seven Principles Tailoring Rules Manage by Exception Focus on Products
People
- 14% of exam
- People Element Concepts People Management Products Change Management vs Change Control Leadership vs Management
Practices
- 60% of exam
- Seven Practices PID Management Approaches Project Log Records Roles + Three Interests Plans + Planning Technique Risk Terms Issue Types + Change Progress Controls Which Practice Applies?
Processes
- 15% of exam
- Seven Processes: Purpose Process Triggers + Outputs Which Process Applies? Managing a Stage Boundary
Quick Facts
- Exam PRINCE2 7 Foundation
- Body PeopleCert (AXELOS)
- Questions 60 multiple choice
- Time 60 minutes
- Pass 36/60 = 60%
- Marking 1 mark; no negatives
- Book Closed book
- Question styles Standard, missing word, list
- Bloom levels 1 and 2
- Extra time 75 min if non-native
- Prerequisite None
- Renewal 3 years; CPD or retake
- Version PRINCE2 7 (2023)
Performance Aspects KE
- Benefits Cost Time Quality Scope Sustainability Risk
- Sustainability is new Version 6 had six Each aspect carries tolerance Tolerances enable exception management
Practice vs Process KE
Practice
- Ongoing throughout project
- Seven, renamed from themes
- Business case, risk, progress
Process
- Step-by-step activities
- Seven, in time order
- Starting up, initiating, closing
- Continuous versus sequential
Exam Mechanics KE
- Standard question Four options, one correct
- Missing word Choose word completing sentence
- List question Pick two correct statements
- Negative question Used only exceptionally
- Bloom level 1 Recall facts
- Bloom level 2 Show understanding
- Marks needed 36 of 60 60%
Five Integrated Elements KE
- Principles Seven guiding obligations
- People New fifth element v7
- Practices Renamed from themes v7
- Processes Seven step-by-step stages
- Project context Where PRINCE2 is applied
- Version 6 count Four elements, no people
Seven Performance Aspects KE
- Benefits Measurable improvement from outcome
- Cost Permitted overspend or underspend
- Time Permitted early or late
- Quality Variation from acceptance criteria
- Scope Products in or out
- Sustainability Environmental, social, economic impact NEW
- Risk Threat and opportunity exposure
Delivery Approaches + Definitions KE
- Linear-sequential Plan fully, then build
- Iterative-incremental Repeated cycles add features
- Hybrid Mixes both approaches
- Project Temporary, creates business change
- Project management Plan, delegate, monitor, control
- Management product Used to run project
- Specialist product What the project delivers
Seven Principles PR
- Business Lessons Roles Stages Exception Products Tailor
- Business: continued justification Lessons: learn from experience Roles: and relationships Stages: manage by stages Exception: tolerance breaches only Products: focus on products Tailor: to the project
Seven Principles PR
- Ensure continued business justification Desirable, viable, achievable throughout
- Learn from experience Lessons sought, recorded, applied
- Define roles, responsibilities and relationships Relationships added in v7 v7
- Manage by stages Authorize one stage ahead
- Manage by exception Escalate only tolerance breaches
- Focus on products Agree product descriptions first
- Tailor to suit the project Adapt to project context
Tailoring Rules PR
- Can tailor Processes, terminology, products, roles
- Cannot tailor The seven principles
- Recorded in PID tailoring section
- Recommends tailoring Project manager
- Approves tailoring Project board
- Drivers Size, complexity, importance, environment
Change Management vs Change Control PE
Change management
- People element
- Adoption of outputs
- Change management approach
Change control
- Issues practice
- Protects the baseline
- Issue management approach
- People adopt versus baselines protected
People Element Concepts PE
- Organizational ecosystem Wider organization around project
- Project ecosystem People delivering the project
- Change management Moving people to target
- Stakeholder Affects or is affected
- Culture Shared values and behaviours
- Collaboration Working together toward objectives
- Co-creation Stakeholders build solution together
- Leadership Influence, motivate, set direction
- Management Plan, delegate, monitor, control
People Management Products PE
- Change management approach How adoption is achieved
- Communication management approach Means and frequency defined
- Both stored in The PID
- Effective team Capability, diversity, cultural intelligence
- Stakeholder engagement Planned two-way communication
Seven Practices PR
- Big Old Projects Quickly Reveal Interesting Progress
- B: business case O: organizing P: plans Q: quality R: risk I: issues P: progress
Project Brief vs PID PR
Project brief
- Created in starting up
- Outline business case
- Not a baseline
PID
- Assembled in initiating
- Full business case
- Baseline for the project
- Proposal versus baseline
Which Practice Applies? PR
- Is it still worthwhile → Business case ( Desirable, viable, achievable )
- Who is accountable → Organizing ( Roles and interests )
- What, when, how much → Plans ( Product-based planning )
- Will product be acceptable → Quality ( Acceptance criteria )
- Uncertain future event → Risk ( Threat or opportunity )
- Something has already happened → Issues ( Change control included )
- Are we on track → Progress ( Tolerance and exception )
- People must adopt change → People element ( Not a practice )
Seven Practices PR
- Business case Judge desirable, viable, achievable
- Organizing Accountability, roles, relationships
- Plans What, who, how, when
- Quality Meet the user requirements
- Risk Manage threats and opportunities
- Issues Assess issues, control changes
- Progress Monitor, forecast, control deviation
Project Log Records PR
- Daily Lessons, Issue Risk Quality Product
- Two logs: daily, lessons Four registers: issue, risk Plus quality and product Six records in total
Issue vs Exception PR
Issue
- Something has happened
- Logged in issue register
- May need no change
Exception
- Tolerance forecast to breach
- Triggers exception report
- Escalated one level up
- Event versus tolerance breach
Which Management Product? PR
- Pre-initiation summary → Project brief ( Outline business case )
- Baseline after initiation → PID ( Approved by board )
- Regular team update → Checkpoint report ( Time-driven )
- Board progress update → Highlight report ( Time-driven )
- Tolerance forecast breach → Exception report ( Event-driven )
- Informal note → Daily log ( Project manager )
- Formal change request → Issue register ( Plus issue report )
- Quality event scheduled → Quality register ( Inside project log )
PID Management Approaches PR
- Benefits management How benefits are measured
- Sustainability management How sustainability targets met
- Commercial management Supplier and contract handling
- Quality management Standards, tools, responsibilities
- Risk management How risk is handled
- Issue management How issues, changes handled
- Change management How people adopt outputs
- Communication management Means and frequency
- Digital and data management Data, tools, security rules v7
Risk Technique PR
- Identify Assess Plan Implement Communicate
- Identify: threats, opportunities Assess: probability, impact Plan: response types Implement: owners, actions Communicate: runs throughout
Risk Appetite vs Tolerance PR
Risk appetite
- Willingness to take risk
- Set by the business
- Qualitative attitude
Risk tolerance
- Measurable threshold
- Triggers escalation
- Set per performance aspect
- Attitude versus measurable limit
Who Decides? PR
- Within work package tolerance → Team manager ( No escalation )
- Within stage tolerance → Project manager ( Corrective action )
- Stage tolerance forecast breached → Project board ( Exception report )
- Project tolerance breached → Business layer ( Beyond board authority )
- Request for change → Change authority ( Board may delegate )
- Business case no longer viable → Project board ( May close early )
Project Log Records PR
- Project log Single repository for records v7
- Daily log Informal notes and actions
- Lessons log Lessons captured and applied
- Issue register Formally managed issues
- Risk register Identified threats and opportunities
- Quality register Planned and actual quality
- Product register Product status and versions v7
Issue Technique PR
- Capture Assess Recommend Decide Implement
- Capture: type and severity Assess: impact on objectives Recommend: options and actions Decide: authority approves Implement: and update register
Work Package vs Stage Plan PR
Work package
- Agreed with team manager
- Covers specific products
- Carries its own tolerances
Stage plan
- Approved by project board
- Covers the whole stage
- Baseline for project manager
- Delegated work versus stage baseline
Reports: Who Writes Them PR
- Checkpoint report Team manager to project manager
- Highlight report Project manager to board
- End stage report Project manager at boundary
- End project report Project manager at closure
- Exception report Project manager forecasts breach
- Lessons report Shares lessons with organization
- Issue report Describes a formal issue
Output vs Outcome vs Benefit PR
Output
- The deliverable itself
- Built by the project
- Handed over at closure
Outcome
- Result of using output
- Changed way of working
- Leads to a benefit
- Benefit is measurable improvement
Roles + Three Interests PR
- Executive Business interest; owns business case
- Senior user User interest; owns benefits
- Senior supplier Supplier interest; provides resources
- Project board Executive, senior user, supplier
- Project manager Daily management; one person
- Team manager Delivers agreed work packages
- Project assurance Independent check for board
- Project support Administration, tools, records
- Change authority Decides requests for change
Quality Assurance vs Control PR
Quality assurance
- Independent of the project
- Checks the process
- Organizational responsibility
Quality control
- Inside the project
- Checks the products
- Tests, reviews, inspections
- Process versus product
Four Organizational Levels PR
- Business layer Commissions project; sets tolerances
- Directing Project board authorizes stages
- Managing Project manager runs stage
- Delivering Team manager builds products
- Mandate comes from Business layer
- Appoints the executive Business layer
Project Assurance vs Support PR
Project assurance
- Independent of project manager
- Project board accountable
- Business, user, supplier views
Project support
- Serves the project manager
- Administration and tools
- Optional role
- Independent check versus administration
Plans + Planning Technique PR
- Project plan Board baseline for project
- Stage plan Detailed plan per stage
- Team plan Optional, for work packages
- Exception plan Replaces plan after breach
- Planning horizon How far detail is realistic
- Project product description Defines what project delivers
- Product breakdown structure Hierarchy of required products
- Product flow diagram Sequence and dependencies
- Work package description Agreed work for team
- Minimum stages Initiation plus one delivery
Event-driven vs Time-driven PR
Event-driven
- Triggered by an occurrence
- Stage end or exception
- End stage report
Time-driven
- At set intervals
- Weekly or monthly
- Checkpoint and highlight reports
- Trigger versus timetable
Quality Terms PR
- User quality expectations What the user expects
- Acceptance criteria Prioritized measurable acceptance list
- Quality specifications Measurable detail per product
- Quality planning Define criteria and methods
- Quality control Test, inspect, review products
- Quality assurance Independent of project team
- Quality register Diary of quality events
- Product description Purpose, composition, quality criteria
Risk Terms PR
- Risk Uncertain event affecting objectives
- Threat Risk with negative impact
- Opportunity Risk with positive impact
- Risk appetite Willingness to take risk
- Risk tolerance Measurable escalation threshold
- Risk budget Money for risk responses
- Risk exposure Combined effect of risks
- Risk owner Manages and monitors risk
- Risk action owner Carries out the response
- Cause, event, effect How risks are described
Risk Response Types PR
- Avoid Remove the threat entirely
- Exploit Make opportunity happen
- Reduce Lower probability or impact
- Enhance Raise probability or impact
- Transfer Move impact to another
- Share Split gain and pain
- Accept Take no action now
- Prepare contingent plans Act only if triggered
Issue Types + Change PR
- Request for change Proposal to alter baseline
- Off-specification Product misses quality specification
- Problem Immediate negative impact
- Concern Timing and impact unassessed
- Business opportunity Unexpected positive possibility
- Project baseline Approved versions under control
- Change budget Funds approved changes
- Change authority Board or delegated decider
Progress Controls PR
- Tolerance Permitted deviation before escalation
- Exception Forecast breach of tolerance
- Forecast Projected outcome versus plan
- Time-driven control Happens at set intervals
- Event-driven control Triggered by an event
- Tolerance areas The seven performance aspects
- Escalation route Up one management level
Process Order PR
- SU DP IP CS MP SB CP
- SU: starting up DP: directing (throughout) IP: initiating CS: controlling a stage MP: managing product delivery SB: stage boundary CP: closing a project
Which Process Applies? PR
- Mandate just received → Starting up a project ( Pre-project )
- Board must authorize → Directing a project ( Runs throughout )
- Baseline the project → Initiating a project ( Produces the PID )
- Daily stage work → Controlling a stage ( Project manager )
- Team is building products → Managing product delivery ( Team manager )
- Stage nearly finished → Managing a stage boundary ( Next stage plan )
- Tolerance forecast breached → Managing a stage boundary ( Exception plan )
- Products accepted → Closing a project ( End project report )
Seven Processes: Purpose PR
- Starting up a project Check project is worthwhile
- Directing a project Board decides and controls
- Initiating a project Build solid project foundations
- Controlling a stage Assign, monitor, correct work
- Managing product delivery Team builds agreed products
- Managing a stage boundary Plan next stage, report
- Closing a project Confirm acceptance, hand over
Process Triggers + Outputs PR
- Project mandate Triggers starting up
- Project brief Output of starting up
- Initiation stage plan Approved before initiating
- PID Output of initiating
- Work package Controlling stage to delivery
- Exception report Board may request replan
- End stage report Output of stage boundary
- End project report Output of closing
Common Traps
Practices, not themes
- Version 7 says practices ≠ Version 6 said themes
Five elements, not four
- Version 7 adds people ≠ Version 6 had four
Seven aspects, not six
- Version 7 adds sustainability ≠ Version 6 had six
Brief is not PID
- Brief precedes initiation ≠ PID baselines the project
Issue is not exception
- Issue already happened ≠ Exception is forecast breach
Appetite is not tolerance
- Appetite is willingness ≠ Tolerance is measurable limit
Assurance is not support
- Assurance checks independently ≠ Support administers for manager
Registers sit in log
- Version 7 uses project log ≠ Version 6 kept them separate
Pass mark is 60%
- Version 7 needs 36 ≠ Version 6 needed 33
Adoption is not control
- Change management moves people ≠ Change control protects baselines
Last Minute
- 1. 60 questions; 60 minutes; 36 pass
- 2. Closed book; no negative marking
- 3. Practices = 60% of exam
- 4. People = 14%; processes = 15%
- 5. Practices not themes (version 7)
- 6. Elements = 5; aspects = 7
- 7. Sustainability = seventh performance aspect
- 8. Project log holds six records
- 9. Brief = pre-project; PID = baseline
- 10. Executive owns the business case
- 11. Senior user owns the benefits
- 12. Tolerance = limit; exception = breach
- 13. QA independent; QC tests products
- 14. Manage by stages: minimum two
- 15. Tailor everything except the principles
PRINCE2 7 Foundation (Version 7)
- Practice Questions 157 questions Study Guide 39 topics Cheat Sheet 165 facts Flashcards 50 cards Shorts 1 short Videos 2 videos Blogs 2 blogs Free CE Podcast