PMP 2026: The 10 Most Common Mistakes

Try these free questions

1. Loomstream runs a subscription video service and is localising its back catalogue into nine languages. Subtitle files are produced by three vendors, in Buenos Aires, Cairo and Ho Chi Minh City, and are checked by a single quality team in Dublin. Over the last quarter about eighteen percent of delivered files were rejected for timing drift, where subtitle cues fall progressively out of step with the audio. Each rejection triggers a rework cycle, and because the working days barely overlap a rejected file usually comes back two days later. The project manager has already added two reviewers in Dublin and the rejection rate has not shifted. All three vendors use their own subtitling tools and none of them checks timing before delivery. What should the project manager do next?

   1. Add a third reviewer in Dublin and raise the inspection from a sample of each delivery to every file, so that no drifting subtitle file can reach the platform unchecked.
   2. Introduce a rejection charge into the three vendor contracts at the next renewal so that the cost of the defects sits with the parties that are creating them.
   3. Shift the Dublin team's working hours to overlap the vendors so that a rejected file can be corrected and returned inside a single working day instead of two.
   4. Work with the three vendors to add an automated timing check inside their own tooling before delivery.
   Show the answer and explanation

   Answer: D. Adding reviewers has already been tried and the rejection rate has not moved, which is the clue that the problem is not detection. Defects are being created upstream, at three vendors none of whom check timing, and inspection at the far end of a two-day round trip can only ever find them again. Option 4 moves the check to the point of creation, which is the cheapest place to catch anything, and it removes the time zone penalty entirely because the vendor fixes drift before the file ever leaves. Option 1 is the instinct the project manager has already acted on once. Full inspection would raise detection to near certainty and it is not absurd, but it doubles cost, adds queueing delay, and leaves the eighteen percent creation rate exactly where it was. Option 2 is a legitimate commercial lever and it does align incentives, so it may be worth doing at renewal, but it is slow, it does not tell a vendor how to stop producing drift, and punitive terms with a supplier who lacks the tooling tend to produce disputes rather than quality. Option 3 is a genuine improvement to cycle time and would help the schedule; it just accepts the defect rate as a fixed feature of the process instead of attacking it. Prevention beats inspection here because the cause is known, local and fixable. ECO Domain II, Process, task 'Plan and optimize quality of products and deliverables'; PMBOK Guide Eighth Edition, the Embed Quality Into Processes and Deliverables principle.

2. Pelham Pharma has validated a new blister-packaging line. At the final qualification review the regulator's inspector rejected the batch records. The tamper-seal check appeared in every record as a pass or fail entered by the line operator, with no stated measurement method and no acceptance threshold, and two operators asked how they judged a pass gave different answers. Everything else passed: the equipment qualification, the cleaning validation, the operator training records and the deviation log. Rework and requalification will take five weeks, and the launch market has a competitor entering in three months. The quality management plan listed tamper-seal integrity among its quality metrics, and the project ran two quality audits during the build phase. What did the project manager fail to do earlier?

   1. Schedule quality audits often enough during the build for the gap to surface before qualification.
   2. Define, for each named quality metric, how it would be measured and what result counts as acceptable.
   3. Identify the regulator's inspector in the stakeholder register and engage him on acceptance expectations.
   4. Use control charts on the trial runs so there was data showing the sealing process was stable.
   Show the answer and explanation

   Answer: B. A metric that cannot be measured the same way twice is not a metric. The quality management plan named tamper-seal integrity, which is why the check appears in every batch record, but naming a metric is only half the work: the plan has to state the measurement method and the acceptance threshold, or what gets recorded is an opinion. Two operators giving different accounts of what a pass means is the direct evidence of that omission, and it is what the inspector rejected. More frequent quality audits is tempting because audits are the process-improvement mechanism, but the stem says two audits ran during the build. An audit checks whether the process is being followed, and when the process itself says the operator judges the seal, a compliant audit finds nothing wrong. More of the same control would not have caught it. Missing the inspector from the stakeholder register is a plausible-sounding root cause and is not the cause here: the acceptance requirement is not one inspector's preference, it is what any regulator would expect of a validated line, and it belonged in the plan whoever inspected. Control charts on trial runs would have shown variation in a measured value, which is useful, but there was no measured value to chart, and the absence of a defined measurement sits upstream of the absence of data. ECO Domain II, Process, task 'Plan and optimize quality of products and deliverables'; PMBOK Guide Eighth Edition, Scope Performance Domain and the Embed Quality Into Processes and Deliverables principle.

Take the full free 10-question sample with scoring →