Study PMP Continuously Monitoring Deliverable Quality: key concepts, common traps, and exam decision cues.
Quality surveillance matters because quality drifts when nobody is watching for it. PMP questions in this area usually reward the project manager who monitors quality continuously enough to catch weak signals early, rather than waiting until final acceptance exposes major defects.
Useful quality surveillance may involve:
The stronger answer usually treats quality as something that must be observed during execution, not only at the end.
flowchart TD
A["Work is being produced"] --> B["Review outputs and process signals"]
B --> C["Detect defect trend, drift, or nonconformance"]
C --> D["Decide whether correction or improvement is needed"]
D --> E["Continue surveillance with updated controls"]
The exam often tests whether the project manager chooses early detection over late surprise. Continuous quality surveillance helps the team:
A team’s testing pass rate is still acceptable overall, but defect severity is rising in one module. The stronger move is to treat that pattern as a warning signal and investigate before the next delivery cycle amplifies the problem.
Scenario: A project manager reviews quality data weekly. Overall acceptance remains above target, but one component shows rising defect severity across three consecutive review cycles. The development lead says the final release quality target is still technically being met.
Question: What is the strongest project-manager action?
Best answer: B
Explanation: The strongest answer is B because PMP questions in this area reward early action on meaningful trends. A worsening module-level pattern is a valid surveillance signal even when aggregate performance still appears acceptable.
Why the other options are weaker: