PMP · Question #985
A sponsor requires that the established quality standards for the project be met. As a result, the sponsor asks the project manager for stable measures to ensure that the quality is met. Which three…
The correct answer is A. Identify in the iteration planning the acceptance criteria that meet quality standards. C. Analyze the lessons learned to determine appropriate testing metrics in quality standards. D. Incorporate performance metrics on the verified deliverables according to quality standards. To establish stable measures for quality, the project manager should identify quality-aligned acceptance criteria during iteration planning, analyze lessons learned for testing metrics, and incorporate performance metrics on verified deliverables. These actions proactively…
Question
Options
- AIdentify in the iteration planning the acceptance criteria that meet quality standards.
- BIdentify the acceptance criteria during the retrospective that meet the quality standards.
- CAnalyze the lessons learned to determine appropriate testing metrics in quality standards.
- DIncorporate performance metrics on the verified deliverables according to quality standards.
- EPerform a risk analysis to determine the impact of not complying with quality standards.
How the community answered
(23 responses)- A74% (17)
- B9% (2)
- E17% (4)
Why each option
To establish stable measures for quality, the project manager should identify quality-aligned acceptance criteria during iteration planning, analyze lessons learned for testing metrics, and incorporate performance metrics on verified deliverables. These actions proactively embed and measure quality throughout the project lifecycle.
Identifying acceptance criteria that meet quality standards during iteration planning ensures that quality is built into the work from the outset of each development cycle. This proactive approach sets clear expectations for what "done" means in terms of quality for each increment.
Identifying acceptance criteria during a retrospective is reactive; acceptance criteria should be defined upfront during planning to guide development and testing for the current iteration.
Analyzing lessons learned from previous projects or iterations helps identify what quality metrics and testing approaches were effective or ineffective, allowing the project manager to determine and apply appropriate, proven metrics for the current project's quality standards.
Incorporating performance metrics on verified deliverables directly measures whether the completed work meets the established quality standards. This provides concrete, objective data on the quality of the output, satisfying the sponsor's need for stable measures.
Performing a risk analysis to determine the impact of non-compliance is part of risk management and quality planning, but it doesn't directly establish "stable measures to ensure that the quality is met." It identifies potential negative outcomes rather than proactive measurement.
Concept tested: Quality assurance and measurement in Agile
Source: https://www.pmi.org/learning/library/agile-quality-assurance-best-practices-6031
Topics
Community Discussion
5Our group landed on A, C, and D. Acceptance criteria get defined during iteration planning (not retrospectives, which rules out B), lessons learned feed your testing metrics, and performance metrics on verified deliverables confirm the standards are actually being met.
Spot on, though I would add that performance metrics on verified deliverables also loop straight back into your next iteration planning, so C and D feed each other more than people realize.
Saw ACD on my exam last week. B is wrong because retrospectives are too late for criteria.
Honestly B is the right call here because the retrospective is where you reflect on what worked and what didn't, which is exactly when stable quality measures get locked in. The team reviews how well the quality standards were actually met during the iteration and then commits to concrete acceptance criteria going forward. That makes it a stable, repeatable measure the sponsor is asking for, not just a one-time checklist. Pair B with C and D and you have your three, since lessons learned feed your testing metrics and performance metrics confirm the deliverables comply.
Actually the group landed on A, C, D, because the question is asking for stable quality measures you define and track throughout the project, and acceptance criteria in the project quality plan is the foundation for that, not something you retroactively lock in during iteration reviews.