100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 460
Which observed result supports acceptance of the Sprint-goal-coherence corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Treating the Sprint as a random list of tasks weakens focus and coherence.
- Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The result is recorded in the project controls.
- The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence.
- The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls.
Explanation
Correct Answer
B:The stated result demonstrates the case acceptance condition: Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The result is recorded in the project controls. It depends on the decision Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Record the rationale before the next commitment.
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Treating the Sprint as a random list of tasks weakens focus and coherence. It does not show that Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The result is recorded in the project controls. [R158 R158-Q0460; case R158-C115; CAPM domain 3, task 3.2; source SCRUM.]
C: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: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Retain the initiating evidence for audit.
D:The proposed outcome (The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls.) 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: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Here, the relevant check is Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Retain the initiating evidence for audit. [R158 R158-Q0460; case R158-C115; CAPM domain 3, task 3.2; source SCRUM.]
Question 461
Which project-management decision best addresses the Sprint-goal-coherence situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review.
- Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.
- Treating the Sprint as a random list of tasks weakens focus and coherence.
Explanation
Correct Answer
B:The case evidence identifies A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. The specified decision directly addresses it: Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review. This can be checked using Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0461; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A: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: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Here, the relevant check is Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0461; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
C:The proposed action (Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.) 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 Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Here, the relevant check is Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0461; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
D:This is a tempting but unsupported shortcut in this case: Treating the Sprint as a random list of tasks weakens focus and coherence. It does not show that Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. [R158 R158-Q0461; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Question 462
After a corrective decision on Sprint-goal-coherence, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.
- Treating the Sprint as a random list of tasks weakens focus and coherence.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.
- 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
D:This checks the actual mechanism rather than merely declaring success: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. The desired observed result is Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. [R158 R158-Q0462; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A: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: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Here, the relevant check is Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0462; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
B:This is a tempting but unsupported shortcut in this case: Treating the Sprint as a random list of tasks weakens focus and coherence. It does not show that Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. [R158 R158-Q0462; case R158-C116; 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. 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: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Here, the relevant check is Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0462; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Question 463
Which statement most accurately flags a misleading shortcut to avoid in this Sprint-goal-coherence case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence.
- Treating the Sprint as a random list of tasks weakens focus and coherence.
- Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
B:The shortcut is mistaken: Treating the Sprint as a random list of tasks weakens focus and coherence. The appropriate response is to form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. It is not an unsupported assumption.
C:This is an appropriate independent test of the proposed decision: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
D:This is a supported decision, not the unsupported claim: Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish.
Question 464
Select TWO case-specific elements of a justified Sprint-goal-coherence resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. 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.
- 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 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.
- Treating the Sprint as a random list of tasks weakens focus and coherence.
Explanation
Correct Answer
A:The case evidence identifies A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. The specified decision directly addresses it: Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review. This can be checked using Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. [R158 R158-Q0464; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
B:This checks the actual mechanism rather than merely declaring success: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline. The desired observed result is Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. [R158 R158-Q0464; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
C: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: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline.
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: Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Reconcile the result with the current approved decision baseline.
E:This is a tempting but unsupported shortcut in this case: Treating the Sprint as a random list of tasks weakens focus and coherence. It does not show that Sprint work has a clear objective and the team can adapt the Sprint Backlog while protecting that goal. The decision can be traced to the review evidence. [R158 R158-Q0464; case R158-C116; CAPM domain 3, task 3.2; source SCRUM.]
Question 465
Which project-management decision best addresses the Iteration-backlog-planning situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. 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.
Explanation
Correct Answer
A:The case evidence identifies A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. The specified decision directly addresses it: Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment. This can be checked using Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0465; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
B:This is a tempting but unsupported shortcut in this case: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. It does not show that The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. [R158 R158-Q0465; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
C:The proposed action (Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Record the rationale before the next commitment.) comes from a different Iteration planning situation: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. It does not resolve or independently test the stated issue: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0465; case R158-C117; 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: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0465; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
Question 466
After a corrective decision on Iteration-backlog-planning, 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: A team commits to seven complex stories without considering historical capacity, dependencies 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. Retain the initiating evidence for audit.
- Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
- Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. The desired observed result is The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. [R158 R158-Q0466; case R158-C117; 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. 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: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0466; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
B: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 selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit.
C:This is a tempting but unsupported shortcut in this case: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. It does not show that The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. [R158 R158-Q0466; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
Question 467
Which statement most accurately flags a misleading shortcut to avoid in this Iteration-backlog-planning case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit.
- The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
- Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment.
Explanation
Correct Answer
C:The shortcut is mistaken: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. The appropriate response is to select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment.
Incorrect Answers
A:This is an appropriate independent test of the proposed decision: Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. It is not the invalid shortcut.
B:This is a relevant outcome to seek after the decision: The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. It is not an unsupported assumption.
D:This is a supported decision, not the unsupported claim: Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment. It responds to the actual project issue: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done.
Question 468
Select TWO case-specific elements of a justified Iteration-backlog-planning resolution : the decision and its direct evidence. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Retain the initiating evidence for audit.
- Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. 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. Record the rationale before the next commitment.
- Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
Explanation
Correct Answer
C:The case evidence identifies A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. The specified decision directly addresses it: Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment. This can be checked using Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0468; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
D:This checks the actual mechanism rather than merely declaring success: Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. The desired observed result is The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. [R158 R158-Q0468; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A:The proposed verify (Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Retain the initiating evidence for audit.) comes from a different Iteration planning situation: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. It does not resolve or independently test the stated issue: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0468; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
B:The proposed action (Form a coherent Sprint Goal during Sprint Planning and select Product Backlog Items that support it. Document impacted stakeholders and the decision owner at the review.) comes from a different Iteration planning situation: A Scrum team selects unrelated backlog work and cannot explain what valuable outcome the next Sprint should accomplish. It does not resolve or independently test the stated issue: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Retain the initiating evidence for audit. [R158 R158-Q0468; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
E:This is a tempting but unsupported shortcut in this case: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. It does not show that The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The result is recorded in the project controls. [R158 R158-Q0468; case R158-C117; CAPM domain 3, task 3.2; source SCRUM.]
Question 469
Which project-management decision best addresses the Iteration-backlog-planning situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
- 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.
- 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.
Explanation
Correct Answer
A:The case evidence identifies A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. The specified decision directly addresses it: 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. This can be checked using 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. [R158 R158-Q0469; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
B:This is a tempting but unsupported shortcut in this case: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. It does not show that The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence. [R158 R158-Q0469; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
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: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is 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. [R158 R158-Q0469; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
D:The proposed action (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.) 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 team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Here, the relevant check is 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. [R158 R158-Q0469; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Question 470
After a corrective decision on Iteration-backlog-planning, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Compare progress visuals with objectively accepted Increment items and remaining work. 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.
- Review the Sprint Goal, chosen work and subsequent Increment against the stated objective. Retain the initiating evidence for audit.
- Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: 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. The desired observed result is The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence. [R158 R158-Q0470; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A: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 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.
C: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 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.
D:This is a tempting but unsupported shortcut in this case: Assuming every story has equal effort despite known size and dependency differences makes the plan unreliable. It does not show that The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence. [R158 R158-Q0470; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests