APM PFQ common mistakes
APM PFQ · Understand the traps and how to avoid them.
Treating the project life cycle and the extended project life cycle as the same thing - for example, stating that benefits realisation is a standard phase of every project life cycle.
Candidates memorise the four core phases but do not distinguish them from the extended life cycle, so they pick the wrong option when a question mentions activity after handover.
What to do instead
Learn the core phases as concept, definition, deployment and transition. The extended life cycle adds benefits realisation after transition. If the scenario includes measuring or realising benefits after the project is handed over, it is describing the extended life cycle.
Describing a deliverable as the benefit - for example, writing 'the benefit is a new finance system' instead of stating the measurable improvement the system enables.
Outputs, outcomes and benefits are easy to conflate because they are linked in a chain, and exam options often include the deliverable as a plausible-sounding benefit.
What to do instead
Use the chain: output = the product or deliverable created; outcome = the change in business behaviour or capability; benefit = the measurable, quantifiable advantage that results. A benefit must be measurable and describe value, not just a thing delivered.
Assigning accountability for the business case to the project manager, or saying the sponsor manages day-to-day delivery of the project.
In real organisations the roles often blur, so candidates answer from workplace experience rather than from the defined APM role boundaries.
What to do instead
Fix the role split: the sponsor champions the project, owns and is accountable for the business case, secures funding and is accountable for benefits realisation. The project manager delivers the scope to time, cost and quality and reports progress.
Placing a high-power, low-interest stakeholder in 'manage closely' or 'keep informed' on the power/interest grid.
Candidates remember the quadrant names but not the mapping between the two axes, and the labels sound interchangeable.
What to do instead
Memorise the grid: high power/high interest = manage closely; high power/low interest = keep satisfied; low power/high interest = keep informed; low power/low interest = monitor. Check both axes before choosing the quadrant.
Identifying the critical path as the path with the most activities, the shortest path, or claiming that critical path activities have spare float.
The word 'critical' is misread as 'most important' or 'busiest', and path length is confused with path duration.
What to do instead
The critical path is the longest total-duration path through the network. It determines the minimum project duration and normally has zero total float; any delay on it delays the project end date.
Using free float and total float as if they mean the same thing.
The two definitions are worded similarly and differ only in what the available delay is measured against.
What to do instead
Free float is the amount an activity can be delayed without affecting the earliest start of the next activity. Total float is the amount it can be delayed without affecting the project completion date.
Logging an event that has already happened as a risk.
Candidates focus on whether the event is bad rather than on whether it is uncertain, so anything problematic is labelled a risk.
What to do instead
A risk is an uncertain future event with a probability and an impact. An issue is something that has already occurred and must be managed now. If it has happened, it is an issue, not a risk.
Choosing 'transfer' for a response that reduces likelihood, or choosing 'avoid' when the team simply accepts the risk and plans a contingency.
The response labels are learned as a list without their defining mechanisms, and several options can sound sensible in the scenario.
What to do instead
Avoid removes the threat or the activity that creates it; reduce lowers probability or impact; transfer shifts ownership or financial impact, such as insurance or a contract; accept retains the risk with contingency. For opportunities, the parallel responses are exploit, enhance, share and accept.
Using quality assurance and quality control as synonyms.
Both contain the word 'quality' and both involve checking work, so the process-versus-product distinction is lost.
What to do instead
Quality assurance is process-focused and preventive: procedures, standards and audits intended to prevent defects. Quality control is product-focused and detective: inspections and tests intended to find defects in deliverables.
Saying the project manager can approve any change, or that change control applies only to scope.
Change control is often experienced as a paperwork step for scope changes, so candidates underestimate its breadth and the authority levels involved.
What to do instead
Change control covers baselined items including scope, schedule, cost and quality. Changes should be assessed for impact and approved at the delegated authority level, such as the change control board or sponsor; the project manager implements approved changes.