PMQ — APM Project Management Qualification Exam Blueprint

This Exam Blueprint is an independent study aid for candidates preparing for the Association for Project Management APM Project Management Qualification (PMQ), exam code PMQ. Use it to turn broad project management knowledge into exam-ready capability: define terms clearly, choose appropriate actions in scenarios, connect artifacts to decisions, and explain why a project manager should act a certain way.

Because exact exam weighting is not provided here, the checklist avoids assuming official percentages. Treat the sections below as practical readiness areas to review before attempting full practice questions.

How to Use This Exam Blueprint

Work through the page in three passes:

1. Coverage pass: Mark topics you have studied at least once.
2. Readiness pass: For each topic, check whether you can apply it to a scenario, not just define it.
3. Exam-answer pass: Practise short, structured explanations: what you would do, why, what artifact changes, and who should be involved.

Use this simple rating:

PMQ Readiness Area Map

Core Concepts You Should Be Able to Define Clearly

Use this list to test whether you can give concise, exam-ready explanations.

Project and Organisational Context

• Define a project and explain how it differs from ongoing operations.
• Explain why projects exist: change, value creation, strategic implementation, compliance, capability, or problem solving.
• Distinguish between a project, programme, portfolio, and business-as-usual activity.
• Explain how organisational strategy influences project selection and prioritisation.
• Identify internal and external environmental factors that can affect a project.
• Explain why assumptions and constraints should be documented and reviewed.
• Describe how organisational culture can affect stakeholder behaviour, risk tolerance, decision making, and communication.

Project Life Cycle and Governance

• Explain what a project life cycle is and why it is useful.
• Describe typical life cycle thinking: concept, definition, delivery, handover, and closure, without assuming every organisation uses identical phase names.
• Explain the purpose of governance in authorising, directing, controlling, and assuring project work.
• Describe why stage gates or decision points are used.
• Explain the difference between project management control and independent assurance.
• Identify when a project manager should escalate rather than decide alone.
• Explain why tailoring governance matters for project size, risk, complexity, and organisational context.

Business Case, Benefits, and Value

• Explain the purpose of the business case.
• Identify typical business case elements: need, options, benefits, costs, risks, assumptions, timescales, and value.
• Explain why the business case should remain valid throughout the project.
• Distinguish outputs, outcomes, benefits, and value.
• Explain why benefits may be realised after project closure.
• Identify who may need to own benefits after delivery.
• Recognise when a change threatens the business case and requires review.

Roles and Responsibilities

• Explain the responsibilities of the project manager.
• Distinguish sponsor, project manager, team member, user, supplier, and governance body roles.
• Explain why role clarity reduces conflict and improves accountability.
• Use a responsibility assignment approach such as RACI in principle.
• Identify when decisions belong to the sponsor or governance body rather than the project manager.
• Recognise the difference between authority, accountability, responsibility, and consultation.

Can You Do This? PMQ Application Checklist

If you cannot confidently tick these, revise the related topic before relying on full mock practice.

Governance, Control, and Decision Readiness

Key Governance Questions

Governance and Artifact Checklist

• Project mandate, brief, or initiation information is understood at a concept level.
• Business case is linked to project objectives and benefits.
• Project management plan or equivalent integrated plan is coherent.
• Stakeholder and communication information is current.
• Risk and issue information is current and action-oriented.
• Change control process is understood.
• Baselines are understood: scope, schedule, cost, and quality where applicable.
• Tolerances, escalation routes, and decision authority are clear.
• Assurance and review points are recognised as governance mechanisms, not administrative extras.

Stakeholder and Communication Checklist

Stakeholder Readiness

• Identify stakeholders by interest, influence, power, impact, support, and information needs.
• Explain why stakeholders may change during the project.
• Distinguish stakeholder identification, analysis, planning, engagement, and monitoring.
• Select engagement approaches for resistant, neutral, supportive, and highly influential stakeholders.
• Explain why communication is two-way, not just reporting.
• Choose communication methods based on purpose, urgency, complexity, sensitivity, and audience.
• Identify when conflict is caused by objectives, resources, priorities, personalities, or misunderstandings.
• Explain when negotiation, facilitation, escalation, or formal decision making is appropriate.

Communication Decision Table

Scope, Requirements, and Change Control

Scope and Requirements Checklist

• Explain the difference between project objectives, deliverables, outputs, outcomes, and requirements.
• Describe why requirements should be clear, testable, prioritised, and traceable where appropriate.
• Identify causes of scope creep.
• Explain the role of acceptance criteria.
• Connect scope definition to estimating, scheduling, resourcing, quality, risk, and procurement.
• Identify when ambiguity should be resolved before planning proceeds.
• Explain why stakeholder agreement on scope does not eliminate the need for change control.

Change Control Decision Path

    flowchart TD
	    A[Change requested] --> B{Clarification or real change?}
	    B -->|Clarification| C[Confirm requirement and document decision]
	    B -->|Change| D[Log change request]
	    D --> E[Assess impact on scope, time, cost, quality, risk, benefits]
	    E --> F{Within delegated authority?}
	    F -->|Yes| G[Approve or reject using agreed process]
	    F -->|No| H[Escalate to sponsor or change authority]
	    G --> I[Update baselines, plans, and communications]
	    H --> I

Change Scenario Checks

Schedule, Dependencies, and Resource Readiness

Planning and Scheduling Checklist

• Explain why work breakdown and product breakdown thinking help define work.
• Identify dependencies: mandatory, discretionary, internal, external.
• Explain sequence, duration, milestones, and critical path.
• Recognise the effect of float on schedule flexibility.
• Distinguish effort, duration, and elapsed time.
• Explain why adding people to late work may not always recover time.
• Identify resource constraints and over-allocation.
• Explain schedule compression concepts at a practical level, including trade-offs.
• Recognise when schedule changes affect cost, risk, quality, or scope.

Schedule Formula and Concept Checks

Be comfortable with basic schedule network reasoning:

\[ \text{Float} = \text{Latest Finish} - \text{Earliest Finish} \]

or equivalently:

\[ \text{Float} = \text{Latest Start} - \text{Earliest Start} \]

Readiness prompts:

• Can you identify the critical path as the longest path through dependent activities?
• Can you explain why activities on the critical path have no schedule flexibility in the current network?
• Can you identify whether a delay affects the overall project completion date?
• Can you explain the effect of a dependency change?
• Can you distinguish milestone slippage from activity duration variance?

Budget, Estimating, and Cost Control

Cost Readiness Checklist

• Explain different estimating approaches at a practical level: analogous, parametric, bottom-up, and expert judgement.
• Distinguish accuracy, uncertainty, contingency, and management reserve conceptually.
• Explain why estimates should include assumptions.
• Connect scope clarity to estimate reliability.
• Explain the purpose of a cost baseline.
• Identify cost variance and forecast concerns.
• Explain why cost control should not ignore benefits, quality, or risk.
• Recognise when a budget issue requires escalation.

Earned Value Style Concepts

If your study materials include earned value concepts, be ready to interpret the ideas in plain language.

Common formulas, if applicable to your preparation:

\[ \text{Cost Variance} = \text{Earned Value} - \text{Actual Cost} \]\[ \text{Schedule Variance} = \text{Earned Value} - \text{Planned Value} \]

Readiness prompts:

• Can you say whether a negative cost variance is favourable or unfavourable?
• Can you explain why being under budget is not always good if less work has been completed?
• Can you connect variance to corrective action rather than just calculation?

Risk, Issue, and Opportunity Management

Risk Checklist

• Define risk as uncertainty that may affect objectives.
• Distinguish threats and opportunities.
• Separate risk cause, event, impact, probability, response, owner, and trigger.
• Explain qualitative risk assessment using likelihood and impact.
• Explain why risk proximity and urgency may matter.
• Identify common risk responses: avoid, reduce, transfer, accept, exploit, enhance, share.
• Explain contingency planning and fallback thinking.
• Know when a risk becomes an issue.
• Explain why risks should be reviewed throughout the project.

Risk Response Decision Table

Issue Management Checklist

• Define an issue as a current problem requiring action.
• Distinguish issue management from risk management.
• Record issue owner, impact, priority, action, and status.
• Assess impact on scope, schedule, cost, quality, risk, and benefits.
• Escalate issues outside authority or tolerance.
• Communicate issue impact to affected stakeholders.

Quality Management and Acceptance

Quality Checklist

• Define quality in relation to fitness for purpose and meeting requirements.
• Explain the purpose of quality planning.
• Distinguish quality assurance from quality control.
• Identify the role of acceptance criteria.
• Explain why quality should be built in, not inspected in only at the end.
• Recognise cost, schedule, and reputational impacts of poor quality.
• Explain corrective and preventive action.
• Connect quality responsibilities to team members, suppliers, users, and governance roles.

Quality Decision Prompts

Procurement and Supplier Management

Procurement Checklist

• Explain make-or-buy decision factors.
• Identify why procurement planning must align with scope, risk, schedule, and budget.
• Understand that supplier selection should consider more than lowest price.
• Explain basic procurement risks: dependency, performance, quality, commercial terms, integration, and knowledge transfer.
• Recognise the importance of clear requirements and acceptance criteria in supplier work.
• Explain why contract changes require control.
• Identify handover and transition responsibilities involving suppliers.

Supplier Scenario Checks

• A supplier is late: can you identify impact, contractual route, mitigation, and escalation?
• A supplier proposes a cheaper alternative: can you assess quality, risk, and approval implications?
• A contract deliverable is ambiguous: can you recommend clarification before acceptance?
• A supplier dependency threatens the critical path: can you link procurement risk to schedule control?

Leadership, Teamwork, and People Factors

Team and Leadership Checklist

• Explain why leadership differs from task administration.
• Identify how leadership style may need to adapt to team maturity, urgency, complexity, and uncertainty.
• Explain motivation factors beyond pay.
• Recognise signs of poor morale, unclear roles, overload, conflict, and lack of commitment.
• Use delegation appropriately: task, authority, accountability, and support.
• Explain why team development affects delivery performance.
• Recognise when conflict can be constructive and when it needs intervention.
• Select suitable responses to poor performance, confusion, or resistance.

People Scenario Decision Table

Agile, Predictive, and Hybrid Delivery Readiness

The PMQ candidate should be prepared to reason about delivery approaches without turning the answer into a method debate.

Readiness prompts:

• Can you explain why high uncertainty may favour iterative discovery?
• Can you explain why regulatory, contractual, or safety constraints may require stronger upfront control?
• Can you identify what should be tailored: documents, reviews, roles, cadence, reporting, or controls?
• Can you avoid claiming agile means no planning or governance?
• Can you avoid claiming predictive delivery means no adaptation?

Handover, Transition, Closure, and Learning

Closure Checklist

• Explain the difference between project completion, product acceptance, operational transition, and benefits realisation.
• Identify handover activities: documentation, training, support arrangements, acceptance, operational readiness, and ownership transfer.
• Explain why closure should confirm outstanding work, open risks or issues, contractual matters, and lessons learned.
• Recognise that premature closure can damage benefits, quality, and stakeholder confidence.
• Explain why lessons learned should be captured and used, not merely filed.
• Identify who may continue benefit tracking after the project team disbands.

Closure Scenario Checks

Artifact-to-Decision Checklist

Use this table to connect exam scenarios to project documentation and control artifacts.

Common Weak Areas and Exam Traps

Scenario Judgment Prompts

Use these prompts for final review. Answer each in two or three structured sentences.

What Should the Project Manager Do Next?

• A senior stakeholder asks for a change that will delay a key milestone.
• The project is under budget, but earned progress is also behind plan.
• A high-impact risk is close to occurring and no owner has acted.
• The team reports that requirements are unclear after planning has started.
• A supplier deliverable fails acceptance testing.
• The sponsor asks for a shorter schedule without reducing scope.
• A critical resource is assigned to another project.
• Users reject a deliverable that appears to meet the written specification.
• The business case depends on a benefit that no department has agreed to own.
• The team wants to bypass quality checks to meet a deadline.

What Artifact Should Be Updated?

• New risk identified during a stakeholder workshop.
• Approved scope change affects cost and schedule.
• Issue workaround creates a new operational risk.
• Stakeholder influence increases after organisational restructuring.
• Lessons learned identify a better estimating approach.
• Supplier delay affects the critical path.
• Acceptance criteria are clarified during testing.
• Benefits forecast changes after market conditions shift.

When Should You Escalate?

• Impact exceeds agreed tolerance or delegated authority.
• Business case viability is threatened.
• A decision is outside the project manager’s authority.
• Conflicting stakeholder priorities cannot be resolved at project level.
• A major risk or issue threatens agreed objectives.
• Contractual, regulatory, safety, or reputational implications arise.
• Required resources cannot be secured through normal channels.

Mini Self-Test: Explain the Difference

For each pair, practise a concise distinction and a scenario example.

Final-Week Review Checklist

Coverage and Recall

• I can explain the purpose of the business case and when it should be reviewed.
• I can map project life cycle stages to governance decisions.
• I can identify key project roles and decision authorities.
• I can distinguish scope, requirements, deliverables, acceptance criteria, and benefits.
• I can explain risk, issue, change, quality, stakeholder, and schedule control processes.
• I can interpret common project scenario cues and choose the next appropriate action.
• I can connect artifacts to decisions without over-documenting every answer.

Scenario Practice

• I have practised mixed scenarios, not just topic-by-topic recall.
• I can explain why an answer is appropriate, not just select it.
• I check whether the scenario asks for prevention, correction, escalation, communication, or approval.
• I look for constraints: authority, tolerance, baseline, stakeholder impact, and business case impact.
• I avoid assuming facts not stated in the question.
• I use project management language precisely and concisely.

Calculation and Interpretation

• I can calculate or interpret simple float and critical path implications if presented.
• I can explain basic cost and schedule variance concepts if included in my study materials.
• I can interpret estimates, contingencies, and forecasts in practical terms.
• I can connect calculations to management action.

Exam Readiness

• My weak topics are listed and reviewed.
• I have a one-page summary of key definitions and artifact links.
• I can answer under timed conditions.
• I review errors by cause: knowledge gap, misread question, poor judgment, or timing.
• I can handle scenario wording calmly without searching for a memorised template.
• I know when the best answer is to analyse, consult, update, escalate, or seek approval.

Practical Next Step

Choose three weakest readiness areas from this checklist and complete a focused practice cycle for each: review the concept, answer scenario questions, write a short explanation for each missed item, and retest under time pressure. Then move to mixed PMQ practice so you can apply Association for Project Management project management concepts across integrated scenarios rather than isolated topics.