High-Yield PMQ Revision Curriculum (from the public question corpus)

Status: MODEL-DERIVED, not an official APM weighting. Generated 2026-08-27 from the corpus in 06_NORMALISED_CORPUS/ and the probability model in 11_ANALYSIS_MODELLING/01_probability_model/. Scores reflect the publicly observable question universe weighted toward the current (Sept-2024+) exam format.

0. The exam you are preparing for (current format)

2.5-hour online exam (Surpass), 40 questions / 90 marks, in two parts of 20 questions, optional break up to 30 min; Part 1 locks after submission.
20 multiple response (1 mark each) · 5 select-from-list (2 marks) · 5 short response (2 marks) · 10 long response (5 marks each).
Long response = 50 of 90 marks — it decides passes. Budget ~1 min per mark; protect the 5-mark questions.
No fixed pass mark (modified Angoff); observed candidate margins: pass 73% vs 64% pass mark; fail 61% vs 62%. Do not aim for 'just over half'.
Questions come from 73 learning outcomes across 24 competences in 4 areas: Setting up for success; Preparing for change; People and behaviours; Planning, management and deployment.

1. Tiered syllabus priority (strategic priority 0-100)

Tier	Syllabus area	Priority	Unique Qs	Indep. sources	Focus type mix
1	life_cycles	88.2	19	10	scenario diagnosis ('which life cycle would not be suitable?'), recognition, def
1	governance	86.2	26	13	responsibility, recognition, long-response compare (functional vs matrix), defin
1	teams	80.1	13	7	process/sequence (Tuckman), recognition, long-response application to scenario
1	risk_issue	76.2	12	7	process/sequence, distinction (risk vs issue), scenario diagnosis, best response
2	budget_cost	72.4	15	9	calculation, recognition, scenario diagnosis (which metric), long-response
2	schedule	71.2	21	11	calculation, distinction, recognition, long-response explain
2	leadership	70.9	10	6	scenario diagnosis (best leadership response), long-response explain 'why change
2	stakeholders	69.8	10	8	scenario diagnosis, application, long-response 'why essential' with scenario-spe
2	resources	67.0	9	7	recognition, scenario diagnosis, long-response 'explain why important'
2	business_case	64.9	13	10	recognition, definition, calculation, long-response 'what would be included'
2	change_control	61.0	11	10	process/sequence, recognition ('not required at raise stage'), long-response exp
2	requirements	60.9	9	8	prioritisation, process, recognition, long-response
3	procurement	59.8	10	9	process, distinction, definition, long-response explain steps
3	ethics_compliance	54.4	6	5	recognition, scenario diagnosis, short response
3	quality	54.4	6	5	distinction (QC vs QA), recognition, long-response explain purposes
3	reviews	51.3	10	8	process, recognition, long-response
3	transition	49.4	5	3	recognition, scenario diagnosis, long-response outcomes/consequences
3	sustainability	48.8	5	3	definition, recognition, long-response scenario
3	conflict	47.9	6	5	recognition, best response, long-response explain modes
3	benefits	44.3	4	5	process/sequence, recognition, long-response explain each step
3	integrated_planning	43.1	8	8	recognition, long-response list-and-describe
3	diversity_inclusion	42.8	3	2	recognition, long-response scenario
3	assurance	39.8	3	3	recognition, short response, long-response benefits
3	solutions_dev	37.1	3	2	prioritisation, scenario diagnosis

Tier 1 — must master (priority ≥ 75)

life_cycles (priority 88.2)

Know: linear / iterative / hybrid choice & strengths/limitations; why phases & decision gates; extended life cycle (adoption, benefits realisation); when to re-estimate at phase ends; deployment baseline in iterative
Practise: scenario diagnosis ('which life cycle would not be suitable?'), recognition, definition, long-response compare/differentiate, select-from-list

governance (priority 86.2)

Know: roles & responsibilities (sponsor vs PM, steering group, product owner, users); organisation structures (functional/matrix/project); policies vs procedures; assurance & delegated authority; linking projects to objectives; PMO (embedded) benefits
Practise: responsibility, recognition, long-response compare (functional vs matrix), definition (policy), 'state responsibilities'

teams (priority 80.1)

Know: Tuckman forming-storming-norming-performing; characteristics of effective teams; virtual/remote teams; coaching & mentoring; team cohesion factors; accountability & open communication
Practise: process/sequence (Tuckman), recognition, long-response application to scenario

risk_issue (priority 76.2)

Know: risk management process order (initiate, identify, analyse, respond, implement, monitor, close); risk vs issue; probability x impact grid; risk appetite & thresholds; escalation path; proactive (avoid/reduce/transfer/accept) & reactive responses; benefits of risk management; contingency
Practise: process/sequence, distinction (risk vs issue), scenario diagnosis, best response, escalation, long-response explain steps/benefits

Tier 2 — high value (priority 60-74)

budget_cost (72.4): cost breakdown structure & cost categorisation; budget creation; EVM (PV/AC/EV, SPI/CPI, EAC); reporting financial performance; surplus/underspend handling; financial closure; re-estimation
schedule (71.2): estimating methods (parametric/analogous/analytical/Delphi); critical path vs critical chain; resource smoothing vs levelling; re-estimation reasons; schedule reviews & metrics; re-planning after reviews
leadership (70.9): situational leadership; changing styles across team development; emotional intelligence; coaching & mentoring; hybrid/remote leadership; conflict-handling styles
stakeholders (69.8): stakeholder analysis -> communication plan; power/interest; expectations management; wind-farm style scenario questions; methods & channels; barriers (incl. voice-only factors); stakeholder analysis consequences
resources (67.0): identify & schedule resources; RACI/RAM with WBS+OBS; resource categorisation & allocation (linear vs iterative); availability & commitment; what is NOT critical to consider
business_case (64.9): business case sections (strategic context, economic analysis, commercial approach, financial case, management approach); PESTLE/SWOT/VUCA; NPV/IRR/payback; alignment to organisation objectives; regular review of changes
change_control (61.0): change control stages (raise -> evaluate -> recommend -> decide -> implement/update); what is captured in a change request; detailed evaluation (impact on business case); recommendations (approve/defer/reject); config management steps; importance in linear life cycle
requirements (60.9): requirements gathering methods; MoSCoW prioritisation; SMART; evaluation/prioritisation by customer value; scope definition (PBS/WBS/CBS); requirements management steps; change impact analysis

Tier 3 — don't neglect (priority < 60, still examinable)

procurement (59.8): procurement strategy contents & importance; supplier selection steps; contract types & relationships (transactional vs collaborative); reimbursement methods (fixed price, cost plus, per unit, target cost); BATNA/ZOPA; negotiation
ethics_compliance (54.4): CPD cycle & responsibility; code of professional conduct; legal/regulatory environment; gifts/inducements (sources of advice); professionalism actions (root cause, CPD, code)
quality (54.4): quality planning & quality plan contents; QC vs QA; inspection/testing/surveying stakeholders; acceptance criteria; quality control techniques; financial aspects
reviews (51.3): decision gates & questions before gates; benefits of reviews/gates; review types; knowledge management & lessons learned; re-planning after reviews; financial performance reporting points; why projects close early
transition (49.4): transition planning from outset; change impact analysis; knowledge transfer; engaging stakeholders; handover & closeout activities; outcomes of good/poor transition
sustainability (48.8): sustainability definition (org + individual responsibility, extended life cycle); principles (environmental/social/economic/administrative); monitoring & reporting; scenario applications
conflict (47.9): sources of conflict (incl. deployment phase); Thomas-Kilmann modes (compete/collaborate/compromise/accommodate/avoid); negative vs positive impacts; conflict addressing approaches
benefits (44.3): benefits management process (identification, definition, planning, tracking, realisation); benefits identification sources; alignment to objectives
integrated_planning (43.1): integrated PMP contents; baseline & control; uncertainty management parts (risk identification/analysis, contingency planning); PMP components (List & Describe 5)
diversity_inclusion (42.8): benefits of diverse teams; positive environment behaviours; conscious vs unconscious bias; diverse thinking & innovation
assurance (39.8): purpose of assurance; benefits (4) + external assurance reasons; true/false statements; final assurance activities
solutions_dev (37.1): evaluate & prioritise requirements for optimal solution; iterative first-release approaches (value to customer)

2. The 20 knowledge primitives with the strongest recurrence

Concept	Unique Qs	Indep. sources	Current-format Qs	Generation breadth (1-10)
earned_value	13	9	2	8
procurement_strategy_selection	9	9	5	8
linear_vs_iterative	11	7	7	9
risk_vs_issue	9	7	5	8
stakeholder_analysis	7	7	5	8
integrated_pmp	7	7	3	6
governance_principles	6	7	3	8
resource_allocation	8	6	5	6
requirements_prioritisation	6	6	5	8
functional_vs_matrix	4	6	3	6
risk_process_steps	7	5	5	7
conflict_sources_and_modes	6	5	3	8
change_control_stages	6	5	4	8
leadership_styles	5	5	2	7
quality_planning_qc_vs_qa	5	5	3	7
ethics_cpd_conduct	5	5	4	7
project_vs_bau	4	5	1	6
context_tools_pestle_swot_vuca	4	5	2	7
benefits_process	4	5	2	6
config_management	3	5	1	6

Generation breadth = how many distinct question forms the concept can generate (definition, recognition, distinction, scenario diagnosis, best response, process, etc.). A concept with breadth 8-9 is strategically important even if its raw count is modest (spec §26).

3. Command-word discipline

Observed command words in the corpus: describe and explain dominate; then state; list; outline; identify/recommend/interpret for scenarios.

State = a few words. List = the required number of items, brief. Outline = key features in sentences. Describe = characteristics (what/how/who/when). Explain = purpose/reason (why) — one-word answers score zero.
'Differentiate / explain the difference between X and Y' requires comparing both, not describing one side.
Highlight the command verb + the number of points required; structure answers around the marks (5 marks = 5 points, or 2+3 for split questions).

4. Question-family practice focus

Most common ways questions are asked (unique questions): recognition (69), explanation (41), scenario_diagnosis (28), process (21), best_response (20), justification (17), comparison (14), application (11), distinction (10).

Scenario diagnosis + best response are the current format's signature — the new exam is scenario-based (Wellingtone/APM guidance). Always link answers to the scenario ('in this project…').
Recognition dominates the 1-mark multiple-response questions: definitions, 'which is not…', 'which two…' — drill definitions precisely (APM terminology).
Process/sequence: risk process order, benefits process, change control stages, config management steps, information management steps — learn them as ordered lists.

5. Long-response (5-mark) answer recipe

Re-read the question; underline command verb(s) and the split (e.g. 2 marks + 3 marks).
Write exactly that many distinct points, numbered/headings so markers can see them.
Each point = claim + why it matters (and scenario link where given). Do not pad; extra content earns nothing.
Use APM language (assess/analyse, risk response terms, MoSCoW, EVM terms) — markers award APM-framework language.
Manage time: 5 minutes minimum per 5-mark question; move on if stuck.

6. Cross-topic revision pairs (integration is heavily tested)

Highest co-occurrence pairs in the corpus: change↔cost, change↔schedule, requirements↔change, risk↔schedule, risk↔cost, stakeholders↔leadership, sustainability↔risk, business case↔governance, governance↔transition, quality↔acceptance. When revising a topic, rehearse its neighbours: e.g. a change request forces schedule re-estimation, cost impact, risk re-assessment and business-case review.

7. Practice plan (recommended 80-120 hours)

Weeks 1-3 — knowledge pass (40h): work the 73 learning outcomes as a checklist, area by area, in the Tier order above; keep a one-page definition sheet in APM wording.
Weeks 4-5 — question-type drills (20h): official Sample Paper 1 & 2 question-by-question; then select-from-list and short-response drills; then long-response writing under 5-minute timings.
Weeks 6-7 — timed mocks (20h): sit the generated mock paper (see 05_mock_exam_generator/) and re-sit it after marking; then a second mock built with a different seed.
Final week — scenario day (10h): practise wind-farm-style 'why essential… in particular' questions and 'what would you do' scenarios across Tier-1 topics; review command-word table.
Daily (10h total): drill the 20 primitives in §2 via flashcards; one EVM and one estimating exercise per day.

8. Warnings — what NOT to treat as the exam

Commercial 'actual exam' dumps (13 sites): unverified, recycled practice-bank content. The '40 Q&A' claims are marketing; identical questions circulate across storefronts. Use them (if at all) only as extra style practice, never as the real exam.
Old-format (pre-Sept-2024) questions are study value for knowledge, not format: the exam changed from 16x50-mark essays to 40 questions/90 marks, and the syllabus moved from BoK7 to the 24-LO Competence Framework. Old 'List & Describe 5…' questions no longer match the exam's shape.
No official answer keys exist; corpus keys on official papers are analyst-inferred. Where an answer feels ambiguous (e.g. PESTLE Political vs Legal), learn the APM definition rather than memorising a letter.
No candidate-recalled live questions are available publicly — anyone selling 'recalled PMQ questions' is almost certainly selling fabricated or recycled material.

Generated by scripts/curriculum_pmq.py from probability_model.json + recurrence_model.json. Curriculum is a revision aid, not an APM publication.