100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.]
Question 471
Which statement most accurately flags a misleading shortcut to avoid in this Iteration-backlog-planning case? 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.
- 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. Document impacted stakeholders and the decision owner at the review.
- The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence.
- 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.
Explanation
Correct Answer
A: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. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
B: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. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done.
C:This is a relevant outcome to seek after the decision: The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence. It is not an unsupported assumption.
D: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. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
Question 472
Select THREE consistent elements of the Iteration-backlog-planning case: appropriate decision, verification, and observable success condition. 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.
- 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. Document impacted stakeholders and the decision owner at the review.
- The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence.
- 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.
- The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence.
- 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.
Explanation
Correct Answer
B: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-Q0472; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
C:The stated result demonstrates the case acceptance condition: The iteration contains a credible delivery forecast rather than an arbitrary commitment count. The decision can be traced to the review evidence. It depends on the decision 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.
F: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-Q0472; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Incorrect Answers
A: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-Q0472; case R158-C118; 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. 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 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-Q0472; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
E:The proposed outcome (The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence.) 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-Q0472; case R158-C118; CAPM domain 3, task 3.2; source SCRUM.]
Question 473
Which project-management decision best addresses the WBS-to-iteration-translation situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. 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.
- 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.
- 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.
- Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning.
- Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
Explanation
Correct Answer
A:The case evidence identifies A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. The specified decision directly addresses it: 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. This can be checked using Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit. [R158 R158-Q0473; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
Incorrect Answers
B:The proposed action (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.) 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: 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. Retain the initiating evidence for audit. [R158 R158-Q0473; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
C: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 result is recorded in the project controls. [R158 R158-Q0473; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
D:The proposed action (Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.) 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. Retain the initiating evidence for audit. [R158 R158-Q0473; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
Question 474
After a corrective decision on WBS-to-iteration-translation, 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 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.
- Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.
- Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning.
- Compare usage evidence and revised order with previously agreed product objectives. 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. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit. The desired observed result is The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls. [R158 R158-Q0474; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
Incorrect Answers
A:The proposed verify (Compare usage evidence and revised order with previously agreed product objectives. Retain the initiating evidence for audit.) 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. Retain the initiating evidence for audit. [R158 R158-Q0474; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
B: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 result is recorded in the project controls. [R158 R158-Q0474; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
C:The proposed verify (Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.) 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. Retain the initiating evidence for audit. [R158 R158-Q0474; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
Question 475
Which statement most accurately flags a misleading shortcut to avoid in this WBS-to-iteration-translation case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. 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.
- 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.
- 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 result is recorded in the project controls.
- Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.
Explanation
Correct Answer
B:The shortcut is mistaken: Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning. The appropriate response is to 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.
Incorrect Answers
A:This is a supported decision, not the unsupported claim: 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. It responds to the actual project issue: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early.
C:This is a relevant outcome to seek after the decision: The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls. It is not an unsupported assumption.
D:This is an appropriate independent test of the proposed decision: Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit. It is not the invalid shortcut.
Question 476
Select THREE consistent elements of the WBS-to-iteration-translation case: appropriate decision, verification, and observable success condition. During scope and delivery planning, the team must make a documented decision before significant work proceeds. 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.
- 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.
- Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. 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.
- 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.
- 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 result is recorded in the project controls.
Explanation
Correct Answer
A:The case evidence identifies A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. The specified decision directly addresses it: 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. This can be checked using Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit. [R158 R158-Q0476; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
C:This checks the actual mechanism rather than merely declaring success: Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit. The desired observed result is The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls. [R158 R158-Q0476; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
F:The stated result demonstrates the case acceptance condition: The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls. It depends on the decision 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.
Incorrect Answers
B:The proposed action (Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment.) 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: 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. Retain the initiating evidence for audit. [R158 R158-Q0476; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
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: Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.
E: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 result is recorded in the project controls. [R158 R158-Q0476; case R158-C119; CAPM domain 3, task 3.2; source ECO.]
Question 477
Which project-management decision best addresses the WBS-to-iteration-translation situation ? 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.
- 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.
- 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
C: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. To verify the specified result, 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.
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-Q0477; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
B: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: 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.
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 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-Q0477; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
Question 478
After a corrective decision on WBS-to-iteration-translation, 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 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.
- 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 progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.
- Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning.
- Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
A: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. The expected result is the team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence.
Incorrect Answers
B:The proposed verify (Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.) 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-Q0478; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
C: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-Q0478; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
D:The proposed verify (Compare usage evidence and revised order with previously agreed product objectives. Reconcile the result with the current approved decision baseline.) 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-Q0478; case R158-C120; CAPM domain 3, task 3.2; source ECO.]
Question 479
Which statement most accurately flags a misleading shortcut to avoid in this WBS-to-iteration-translation case? 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.
- 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.
- Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning.
- 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.
- The team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence.
Explanation
Correct Answer
B:The shortcut is mistaken: Moving the entire multi-month WBS package into a two-week Sprint without decomposition is not incremental planning. The appropriate response is to 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 supported decision, not the unsupported claim: 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. It responds to the actual project issue: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early.
C:This is an appropriate independent test of the proposed decision: 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. It is not the invalid shortcut.
D:This is a relevant outcome to seek after the decision: The team delivers usable functionality early rather than only completing isolated technical layers. The decision can be traced to the review evidence. It is not an unsupported assumption.
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.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests