100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 480
Which observed result supports acceptance of the WBS-to-iteration-translation corrective decision ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning.
- The team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence.
- The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence.
- The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls.
Explanation
Correct Answer
B:The stated result demonstrates the case acceptance condition: The team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence. It depends on the decision Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning. It does not show that The team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence. [R158 R158-Q0480; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
C:The proposed outcome (The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence.) comes from a different Iteration planning situation: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. It does not resolve or independently test the stated issue: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. Here, the relevant check is Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline. [R158 R158-Q0480; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
D:The proposed outcome (The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls.) comes from a different Iteration planning situation: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. It does not resolve or independently test the stated issue: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. Here, the relevant check is Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline. [R158 R158-Q0480; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
Question 481
Which project-management decision best addresses the Adaptive-scope-feedback situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
- Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Record the rationale before the next commitment.
Explanation
Correct Answer
B:The case evidence identifies Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. The specified decision directly addresses it: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment. This can be checked using Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. [R158 R158-Q0481; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. [R158 R158-Q0481; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
C:This option concerns a different Iteration planning situation: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. For the reported case, use this verification: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
D:This option concerns a different Iteration planning situation: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. For the reported case, use this verification: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
Question 482
After a corrective decision on Adaptive-scope-feedback, which independent evidence most directly verifies the result ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
- Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Reconcile the result with the current approved decision baseline.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
Explanation
Correct Answer
A:This checks the actual mechanism rather than merely declaring success: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. The desired observed result is The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. [R158 R158-Q0482; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
B:This option concerns a different Iteration planning situation: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. For the reported case, use this verification: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
C:The proposed verify (Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. [R158 R158-Q0482; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
D:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. [R158 R158-Q0482; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
Question 483
Which statement most accurately flags a misleading shortcut to avoid in this Adaptive-scope-feedback case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
- Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
Explanation
Correct Answer
D:The shortcut is mistaken: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. The appropriate response is to have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. It is not an unsupported assumption.
B:This is a supported decision, not the unsupported claim: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment. It responds to the actual project issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected.
C:This is an appropriate independent test of the proposed decision: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. It is not the invalid shortcut.
Question 484
Select TWO case-specific elements of a justified Adaptive-scope-feedback resolution : the decision and its direct evidence. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
- Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
- Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Record the rationale before the next commitment.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
Explanation
Correct Answer
A:The case evidence identifies Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. The specified decision directly addresses it: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment. This can be checked using Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. [R158 R158-Q0484; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
B:This checks the actual mechanism rather than merely declaring success: Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. The desired observed result is The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. [R158 R158-Q0484; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
C:The proposed action (Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Record the rationale before the next commitment.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. [R158 R158-Q0484; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
D:The proposed verify (Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit. [R158 R158-Q0484; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
E:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The result is recorded in the project controls. [R158 R158-Q0484; case R158-C121; CAPM domain 3, task 3.2; source SCRUM.]
Question 485
Which project-management decision best addresses the Adaptive-scope-feedback situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
- Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review.
- Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
C:The case evidence identifies Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. The specified decision directly addresses it: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0485; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. [R158 R158-Q0485; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
B:The proposed action (Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.) comes from a different Iteration planning situation: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0485; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
D:This option concerns a different Iteration planning situation: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. For the reported case, use this verification: Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
Question 486
After a corrective decision on Adaptive-scope-feedback, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
- Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.
- Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. The desired observed result is The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. [R158 R158-Q0486; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. [R158 R158-Q0486; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
B:The proposed verify (Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.) comes from a different Iteration planning situation: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0486; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
C:The proposed verify (Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0486; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
Question 487
Which statement most accurately flags a misleading shortcut to avoid in this Adaptive-scope-feedback case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review.
- Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
- The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence.
Explanation
Correct Answer
C:The shortcut is mistaken: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. The appropriate response is to have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a supported decision, not the unsupported claim: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected.
B:This is an appropriate independent test of the proposed decision: Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
D:This is a relevant outcome to seek after the decision: The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. It is not an unsupported assumption.
Question 488
Select TWO case-specific elements of a justified Adaptive-scope-feedback resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review.
- Forcing a lower-value item to remain top priority solely because it was first written ignores learning.
- Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
- Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Document impacted stakeholders and the decision owner at the review.
- Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
A:The case evidence identifies Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. The specified decision directly addresses it: Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0488; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
C:This checks the actual mechanism rather than merely declaring success: Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. The desired observed result is The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. [R158 R158-Q0488; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
B:This is a tempting but unsupported shortcut in this case: Forcing a lower-value item to remain top priority solely because it was first written ignores learning. It does not show that The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence. [R158 R158-Q0488; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
D:The proposed action (Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Document impacted stakeholders and the decision owner at the review.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. Here, the relevant check is Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline. [R158 R158-Q0488; case R158-C122; CAPM domain 3, task 3.2; source SCRUM.]
E:This option concerns a different Iteration planning situation: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. For the reported case, use this verification: Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
Question 489
Which project-management decision best addresses the Burndown-versus-value situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
- Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.
- Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Document impacted stakeholders and the decision owner at the review.
- Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
Explanation
Correct Answer
B:The case evidence identifies An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. The specified decision directly addresses it: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment. This can be checked using Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0489; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:This option concerns a different Iteration planning situation: Following a user demo, the highest-value feature changes because a newly observed workflow is more frequent than expected. For the reported case, use this verification: Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.
C:The proposed action (Slice the module into independently testable user-value increments and prioritize a usable vertical slice for the next iteration. Document impacted stakeholders and the decision owner at the review.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0489; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
D:This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0489; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
Question 490
After a corrective decision on Burndown-versus-value, which independent evidence most directly verifies the result ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.
- Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
- Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Reconcile the result with the current approved decision baseline.
- Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. The desired observed result is The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:The proposed verify (Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
B:This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
C:The proposed verify (Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests