PMQ — APM Project Management Qualification Quick Review

Quick Review purpose

This independent Quick Review supports candidates preparing for the Association for Project Management APM Project Management Qualification (PMQ), exam code PMQ.

Use it to refresh the concepts you should be able to explain, apply, compare, and diagnose before moving into topic drills, mock exams, and detailed explanations. It is not a replacement for the current Association for Project Management syllabus or guidance; use those as your authoritative reference for the live exam requirements.

The main PMQ skill is not just remembering terminology. You need to show that you understand why a project management technique is used, when it is appropriate, who is involved, and what can go wrong if it is applied poorly.

High-yield PMQ checklist

Decision rules that answer many PMQ questions

1. Start with objectives and the business case. If a decision affects scope, time, cost, benefits, risk, or viability, connect it back to the business case.
2. Do not bypass governance. Significant decisions should follow agreed authority, escalation, and approval routes.
3. Baseline first, then control. You cannot control schedule, cost, scope, or quality effectively without an agreed baseline or acceptance standard.
4. Analyse before acting. For risks, issues, changes, delays, or supplier problems, first understand impact, options, urgency, and ownership.
5. Differentiate risk, issue, and change. Risk is uncertain, issue is happening, change is a proposed alteration to an agreed baseline.
6. Engagement is more than communication. Stakeholders may need involvement, negotiation, consultation, resistance management, or formal approval.
7. Quality is designed in. Quality planning and assurance reduce the need for late rework.
8. Benefits often outlive the project. The project may deliver outputs, but the organisation normally realises benefits through use and change adoption.
9. The project manager integrates. PMQ answers often require showing how scope, schedule, cost, risk, quality, resources, and stakeholders interact.
10. A good answer includes limits. Techniques have assumptions, costs, and weaknesses; explaining these shows judgment.

Project context, lifecycle, and governance

Lifecycle traps

• Linear does not mean unmanaged change. Even predictive projects need change control and review.
• Iterative does not mean no governance. Adaptive approaches still need objectives, prioritisation, control, and assurance.
• A gate is not just a meeting. It is a decision point based on evidence: continue, stop, defer, re-plan, or escalate.
• Closure is not just delivery. It includes acceptance, handover, records, lessons, contract closure where relevant, and transition to operation.

Business case and benefits

The business case is a control document as well as a justification document. PMQ questions often test whether you understand that the project should remain viable throughout delivery, not just at approval.

Benefits decision rule

If a question asks whether a project should continue, do not answer using delivery progress alone. Consider:

• current and forecast cost;
• remaining benefits and whether they are still achievable;
• changed risks or assumptions;
• stakeholder and operational readiness;
• strategic relevance;
• opportunity cost of using resources elsewhere.

Organisation, roles, and accountability

Role clarity traps

• Confusing accountability with activity: a person may be accountable for an outcome without doing every task.
• Escalating every problem to the sponsor: the project manager should manage within agreed authority.
• Leaving users out of requirements and acceptance: this increases rework and adoption risk.
• Ignoring functional managers in a matrix environment: they often control specialist resources.

Scope, requirements, and change control

Scope management connects the customer need to what the project will and will not deliver. PMQ questions frequently test how well you control scope without blocking legitimate change.

Change control quick path

For a proposed change:

1. Record the request.
2. Clarify what is being requested and why.
3. Assess impact on scope, schedule, cost, quality, risk, resources, benefits, and contracts.
4. Identify options, including reject, defer, approve, or approve with conditions.
5. Submit to the correct authority.
6. Update baselines, plans, records, and communications if approved.
7. Monitor implementation.

The most common wrong answer is to implement the change because it appears small. Small changes can accumulate into major cost, schedule, quality, or benefits impacts.

Planning and scheduling

Planning is iterative. Early plans may be high level; later plans should become more detailed as information improves.

Critical path and float

Total float can be reviewed as:

\[ \text{Total float} = \text{Latest finish} - \text{Earliest finish} = \text{Latest start} - \text{Earliest start} \]

Key interpretation points:

• An activity on the critical path normally has zero total float.
• Delay on a critical activity usually delays the project unless action is taken.
• Reducing duration on a non-critical activity may not shorten the project.
• Float can change when progress, logic, or estimates change.
• Near-critical paths matter because small delays can make them critical.

Estimating review

Three-point expected duration is often reviewed as:

\[ \text{Expected duration} = \frac{\text{optimistic} + 4(\text{most likely}) + \text{pessimistic}}{6} \]

Do not just calculate. Explain what uncertainty the estimate captures and how it affects planning, contingency, or risk management.

Cost control and earned value basics

Cost management is not only accounting. It links estimates, budgets, funding, commitments, actual spend, forecasts, and value delivered.

If earned value is in scope for your preparation, focus on both calculation and interpretation:

\[ \begin{aligned} \text{CV} &= \text{EV} - \text{AC} \\ \text{SV} &= \text{EV} - \text{PV} \\ \text{CPI} &= \frac{\text{EV}}{\text{AC}} \\ \text{SPI} &= \frac{\text{EV}}{\text{PV}} \end{aligned} \]

Risk, issue, and opportunity management

Risk management is proactive. Issue management is reactive. Both need ownership, escalation, and tracking.

Threat response review

Opportunity response review

Risk wording template

A strong risk statement is specific:

Because of cause, there is a risk that event may occur, leading to effect on project objectives.

Weak risk statement: “Supplier risk.”

Better risk statement: “Because the supplier is using a new component, there is a risk that test failures may occur, leading to rework, delayed acceptance, and increased cost.”

Quality management

Quality is about fitness for purpose and conformance to requirements. It must be planned, built in, checked, and improved.

Quality traps

• Quality does not always mean “highest specification”; it means meeting agreed needs and standards.
• Late inspection may detect defects but does not prevent them.
• Poor requirements create quality problems even if the team works hard.
• Quality responsibilities should be clear across the project team, suppliers, reviewers, and customer representatives.

Stakeholders and communication

Stakeholder work is high-yield because it appears in almost every project scenario: unclear requirements, resistance, conflict, delay, benefit failure, and governance issues.

Communication decision rule

Choose communication method by considering:

• sensitivity of message;
• urgency;
• complexity;
• need for feedback;
• stakeholder influence and interest;
• record-keeping requirements;
• geographic or cultural constraints;
• risk of misunderstanding.

A dashboard may be suitable for routine status reporting. A major scope conflict may require direct discussion, negotiation, and formal decision records.

Leadership, teamwork, conflict, and negotiation

PMQ preparation should connect people concepts to project situations. Avoid writing abstract theory only.

Conflict management traps

• Avoiding conflict may preserve short-term harmony but allow risks to grow.
• Forcing a decision may be necessary in a crisis but can damage commitment if overused.
• Compromise may be practical but can produce a weak solution if core needs are ignored.
• Collaboration is powerful but takes time and requires trust, information, and willingness.

Procurement and supplier management

Procurement questions often test whether you consider value, risk, clarity of requirements, and governance rather than just price.

Procurement decision points

Ask:

1. Is the requirement clear enough to procure?
2. What risks should remain with the buyer, and what risks can realistically be transferred?
3. How will supplier performance be measured?
4. How will changes be controlled?
5. What dependencies does the supplier create for schedule, quality, integration, and acceptance?
6. What happens if the supplier fails, delays, or delivers below standard?

Reporting, control, and assurance

Project control compares actual performance with the plan, identifies variance, forecasts outcomes, and triggers corrective action.

Control traps

• Reporting a delay is not the same as controlling it.
• A green status without evidence is not useful.
• Corrective action should have an owner and due date.
• Replanning without approval can hide variance.
• Escalation is not failure; it is part of governance when authority limits are reached.

Handover, transition, and closure

A project can produce a technically complete output that still fails if transition is poor.

Closure traps

• Closure is not just “the work is finished.”
• Benefits may require business adoption after the project team leaves.
• Lessons are only valuable if accessible and used by future projects.
• Outstanding defects, risks, or support needs should be transferred clearly, not hidden.

Calculation and interpretation traps

When calculations appear in practice, candidates often lose marks through interpretation errors rather than arithmetic.

Common PMQ candidate mistakes

• Giving definitions without explaining purpose or application.
• Listing documents without saying how they are used.
• Treating the project manager as the sole decision-maker for strategic or commercial decisions.
• Ignoring the sponsor’s role in business justification and senior stakeholder support.
• Confusing risks, issues, assumptions, constraints, and changes.
• Forgetting to assess impact before approving a change.
• Discussing schedule delay without considering cost, quality, risk, resources, and benefits.
• Treating stakeholder communication as one-way broadcasting.
• Assuming quality is only final inspection.
• Choosing procurement options based only on price.
• Describing benefits without measures or owners.
• Closing the project without handover, acceptance, lessons, or transition.
• Writing generic answers that could apply to any project, instead of using the scenario or context.
• Memorising theory names but failing to explain how they guide action.

Answering PMQ-style prompts efficiently

For most practice prompts, build your answer around this structure:

1. Define the concept briefly.
2. State the purpose: why it matters to project control or success.
3. Apply it to the situation or project phase.
4. Identify roles involved, such as sponsor, project manager, team, user, supplier, or governance body.
5. Mention evidence or documents, such as business case, project management plan, risk register, schedule, issue log, or change request.
6. Add a limitation or trap where relevant.

Example pattern for “explain the importance of stakeholder analysis”:

• It identifies people or groups affected by or able to influence the project.
• It helps the project manager understand interests, power, expectations, and likely support or resistance.
• It informs communication and engagement planning.
• It reduces risk of missed requirements, opposition, late change, or poor adoption.
• It should be reviewed as stakeholders and attitudes change.

Mini self-check

Independent question-bank practice plan

Use this Quick Review before starting intensive practice, then let the question bank expose weak areas.

1. Run topic drills first. Start with lifecycle, governance, business case, planning, risk, quality, stakeholders, and change control.
2. Review detailed explanations, not just scores. For every missed question, identify whether the error was terminology, application, calculation, or exam technique.
3. Create a trap log. Record repeated mistakes such as risk versus issue, assurance versus control, or baseline versus forecast.
4. Practise mixed sets. PMQ questions often combine topics; for example, a change request may affect business case, schedule, cost, stakeholders, risk, and procurement.
5. Use mock exams after topic confidence improves. Timed practice is most useful when you already understand the core concepts.
6. Re-drill weak topics. Do not simply read the explanation once; answer similar original practice questions until the decision rule becomes automatic.

Final quick checklist before practice

Before moving to full mock exams, confirm that you can:

• explain the difference between project, programme, portfolio, and business-as-usual;
• link project decisions to the business case;
• describe lifecycle phases, gates, assurance, and closure;
• distinguish sponsor, project manager, team, user, supplier, and PMO responsibilities;
• build a clear risk statement with cause, event, and effect;
• select suitable risk responses for threats and opportunities;
• explain change control from request to implementation;
• interpret critical path, float, and schedule impact;
• understand estimate types and uncertainty;
• interpret basic cost and earned value indicators if included in your study scope;
• explain stakeholder analysis and engagement planning;
• distinguish quality planning, assurance, control, and acceptance;
• describe procurement decisions beyond lowest price;
• connect handover and transition to benefits realisation.

Next step: choose your two weakest PMQ areas, complete focused topic drills in the PM Mastery question bank, and read the detailed explanations until you can explain both the correct answer and the most tempting wrong answer.

Continue in PM Mastery

Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official APM questions, copied live-exam content, or exam dumps.