APM PMQ study plan
APM PMQ · Give each week a clear focus.
8 weeks · About 7 hours per week
Project management and the project context & Scope, schedule and resource management
Map all ten PMQ domains to their exam weighting and write a one-sentence distinction between project, programme, portfolio and business-as-usual
Decompose a realistic scenario project into a three-level work breakdown structure and derive a dependency-linked activity list from it
Calculate the critical path, total float and free float for two hand-drawn network diagrams, verifying each with a forward and backward pass
Explain in writing how the business case, project mandate, success criteria and benefits profile shape the definition of scope
Your checkpoint
A two-page foundation pack: domain weighting map, three-level WBS with activity list, and two fully solved network diagrams annotated with critical path and float
Scope, schedule and resource management & Budgeting and cost control
Assign durations and resources to the week-1 activity list and plot the resulting resource histogram
Resolve a deliberate over-allocation by resource levelling and record the trade-off in duration, cost and float
Compare bottom-up, analogous, parametric and three-point estimating on a single scope item and justify the selection
Build a cost baseline covering direct and indirect cost, contingency and management reserve, reconciled to the approved budget
Your checkpoint
A resourced schedule and a cost baseline spreadsheet for the same project, with every estimating assumption logged
Budgeting and cost control & Risk and issue management
Calculate CV, SV, CPI, SPI, EAC and VAC from three periods of earned value data and write a 150-word interpretation of the trend
Identify twelve risks for the scenario using structured prompts and classify each in cause-event-effect form
Score and rank the twelve risks on a 5x5 matrix using probability and impact definitions applied consistently
Write responses for the six highest-ranked risks covering avoid, reduce, transfer and accept, each with owner, trigger and residual risk
Your checkpoint
A risk register of twelve scored risks with owners, responses and triggers, plus a one-page earned value analysis with CPI/SPI and a forecast narrative
Project governance and organisation & Risk and issue management
Draw the governance structure for the scenario: sponsor, project board, PMO, project manager and workstream leads, with decision rights for each
Draft terms of reference for the project board including quorum, reporting cycle and escalation thresholds
Trace how risk appetite and tolerances flow from governance documents into the risk process and escalation route
Complete a timed 60-question half paper covering domains 1, 4, 5 and 6 and log every incorrect answer by root cause
Your checkpoint
A governance one-pager (structure, roles, decision rights, tolerances) plus a scored half paper with a categorised error log
Project governance and organisation & Stakeholder engagement and communication
Plot stakeholders on a power/interest grid and match each quadrant to a tailored engagement approach
Write a communication plan specifying audience, message, channel, frequency and owner for six stakeholder groups
Draft three difficult communications (slippage, scope pushback, escalated bad news) in a structured message format
Contrast functional, matrix and project organisational structures and state the project manager's authority and reporting lines in each
Your checkpoint
A stakeholder grid and full communication plan for the scenario covering six groups with named owners and frequencies
Quality management & Change control and configuration management
Distinguish quality planning, quality assurance and quality control, and position each activity in the project lifecycle
Write acceptance criteria for four deliverables and select an appropriate review technique for each (peer review, inspection, audit)
Design an end-to-end change control process: request, impact assessment, decision, implementation and closure
Explain configuration management components (configuration items, baselines, version control, status accounting) and how they underpin change control
Your checkpoint
A completed change request form, a configuration item list and a quality plan with acceptance criteria for four deliverables
Leadership and team management & Procurement, contracts and benefits management
Compare three leadership styles and match each to a team maturity level using a situational leadership model
Plan team formation, a motivation approach and a conflict-handling route for a scenario team of six
Select fixed-price, cost-plus or target-cost contract for three procurement scenarios and justify the resulting risk allocation
Build a benefits profile with owner, measure, baseline and realisation timing, and separate outputs, outcomes and benefits
Your checkpoint
A team leadership plan plus a procurement and benefits pack containing three justified contract recommendations and a four-benefit profile
Project management and the project context & Project governance and organisation & Stakeholder engagement and communication & Scope, schedule and resource management & Budgeting and cost control & Risk and issue management & Quality management & Change control and configuration management & Leadership and team management & Procurement, contracts and benefits management
Sit two full-length timed mock papers under exam conditions and mark them against command-word expectations
Rewrite the ten weakest answers using the correct command word (explain, evaluate, justify) and an explicit structure
Condense each domain onto a single page of trigger facts, formulas and model names for final revision
Your checkpoint
Two marked mock papers with a remediation log, plus a ten-page condensed revision set (one page per domain)
Milestones
Week 2: Resourced schedule and cost baseline are complete, with contingency and management reserve shown as separate lines and reconciling to the approved budget total
Week 4: Half paper scored at least 60% overall with no single domain below 50%, and the error log shows each wrong answer traced to a cause
Week 6: First full-length mock completed under time; score at least 55%, with every domain 7 and 8 answer written in full command-word structure
Week 8: Two full mocks average at least 65% with every domain at 55% or above, and no root cause repeats in the final error log