100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 500
Which observed result supports acceptance of the Increment-evidence-control corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence.
- Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
- Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.
- Integrated work meets consistent quality expectations without hiding unfinished dependencies. The decision can be traced to the review evidence.
Explanation
Correct Answer
C:The stated result demonstrates the case acceptance condition: Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls. It depends on the decision Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.
Incorrect Answers
A:The proposed outcome (Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit. [R158 R158-Q0500; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]
B:This is a tempting but unsupported shortcut in this case: Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control. It does not show that Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls. [R158 R158-Q0500; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]
D:The proposed outcome (Integrated work meets consistent quality expectations without hiding unfinished dependencies. The decision can be traced to the review evidence.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit. [R158 R158-Q0500; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]
Question 501
Which project-management decision best addresses the Increment-evidence-control situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Document impacted stakeholders and the decision owner at the review.
- Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
D:The case evidence identifies A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. The specified decision directly addresses it: Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review. This can be checked using Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0501; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control. It does not show that Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. [R158 R158-Q0501; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
B:The proposed action (Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0501; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
C:The proposed action (Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0501; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Question 502
After a corrective decision on Increment-evidence-control, 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 labels an unfinished feature as a production-ready Increment despite failing integration tests. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Check common quality criteria and test evidence for cross-team Increment integration. Retain the initiating evidence for audit.
- Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.
- Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. The desired observed result is Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. [R158 R158-Q0502; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:This option concerns a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. For the reported case, use this verification: Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.
C:This is a tempting but unsupported shortcut in this case: Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control. It does not show that Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. [R158 R158-Q0502; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
D:The proposed verify (Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0502; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Question 503
Which statement most accurately flags a misleading shortcut to avoid in this Increment-evidence-control case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
- Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.
- Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence.
- Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
A:The shortcut is mistaken: Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control. The appropriate response is to apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
B:This is an appropriate independent test of the proposed decision: Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
C:This is a relevant outcome to seek after the decision: Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. It is not an unsupported assumption.
D:This is a supported decision, not the unsupported claim: Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests.
Question 504
Select TWO case-specific elements of a justified Increment-evidence-control 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 labels an unfinished feature as a production-ready Increment despite failing integration tests. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
- Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
- Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
- Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. The desired observed result is Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. [R158 R158-Q0504; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
E:The case evidence identifies A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. The specified decision directly addresses it: Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Document impacted stakeholders and the decision owner at the review. This can be checked using Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0504; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:The proposed action (Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0504; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
C:The proposed verify (Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.) comes from a different Adaptive project controls situation: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. It does not resolve or independently test the stated issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. Here, the relevant check is Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline. [R158 R158-Q0504; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
D:This is a tempting but unsupported shortcut in this case: Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control. It does not show that Only work meeting the shared quality commitment is counted as completed Increment value. The decision can be traced to the review evidence. [R158 R158-Q0504; case R158-C126; CAPM domain 3, task 3.3; source SCRUM.]
Question 505
Which project-management decision best addresses the Visible-adaptive-artifacts situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
- Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
B:The case evidence identifies A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. The specified decision directly addresses it: Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment. This can be checked using Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0505; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:The proposed action (Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.) comes from a different Adaptive project controls situation: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0505; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
C:This is a tempting but unsupported shortcut in this case: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. It does not show that Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls. [R158 R158-Q0505; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
D:The proposed action (Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0505; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Question 506
After a corrective decision on Visible-adaptive-artifacts, 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 delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
- Check common quality criteria and test evidence for cross-team Increment integration. Retain the initiating evidence for audit.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
- Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit.
Explanation
Correct Answer
C:This checks the actual mechanism rather than merely declaring success: Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. The desired observed result is Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls. [R158 R158-Q0506; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. It does not show that Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls. [R158 R158-Q0506; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
B:The proposed verify (Check common quality criteria and test evidence for cross-team Increment integration. Retain the initiating evidence for audit.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0506; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
D:The proposed verify (Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit.) comes from a different Adaptive project controls situation: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0506; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Question 507
Which statement most accurately flags a misleading shortcut to avoid in this Visible-adaptive-artifacts case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
- Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
Explanation
Correct Answer
A:The shortcut is mistaken: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. The appropriate response is to maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
Incorrect Answers
B:This is a supported decision, not the unsupported claim: Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment. It responds to the actual project issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress.
C:This is a relevant outcome to seek after the decision: Decisions draw on a current shared view of value, work and results. 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 whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. It is not the invalid shortcut.
Question 508
Select TWO case-specific elements of a justified Visible-adaptive-artifacts 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 delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
- Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment.
- Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. The desired observed result is Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls. [R158 R158-Q0508; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
D:The case evidence identifies A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. The specified decision directly addresses it: Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Record the rationale before the next commitment. This can be checked using Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0508; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. It does not show that Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls. [R158 R158-Q0508; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
C:The proposed action (Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0508; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
E:The proposed verify (Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit. [R158 R158-Q0508; case R158-C127; CAPM domain 3, task 3.3; source SCRUM.]
Question 509
Which project-management decision best addresses the Visible-adaptive-artifacts situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
- Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Document impacted stakeholders and the decision owner at the review.
- Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
C:The case evidence identifies A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. The specified decision directly addresses it: Maintain transparent Product Backlog, Sprint Backlog and Increment artifacts with clear ownership and shared access. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. [R158 R158-Q0509; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:The proposed action (Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.) comes from a different Adaptive project controls situation: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. [R158 R158-Q0509; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
B:This is a tempting but unsupported shortcut in this case: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. It does not show that Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence. [R158 R158-Q0509; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
D:The proposed action (Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. [R158 R158-Q0509; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
Question 510
After a corrective decision on Visible-adaptive-artifacts, 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 delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline.
- Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.
- Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline.
- Replacing all visible artifacts with private verbal status prevents inspection and adaptation.
Explanation
Correct Answer
C:This checks the actual mechanism rather than merely declaring success: Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. The desired observed result is Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence. [R158 R158-Q0510; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
Incorrect Answers
A:The proposed verify (Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive project controls situation: Two teams integrating one product use conflicting completion rules, and defects pass between them. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. [R158 R158-Q0510; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
B:The proposed verify (Review test results and completion criteria for each purportedly finished backlog item. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive project controls situation: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests. It does not resolve or independently test the stated issue: A delivery team has a hidden backlog spreadsheet and cannot identify current work or forecast progress. Here, the relevant check is Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Reconcile the result with the current approved decision baseline. [R158 R158-Q0510; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
D:This is a tempting but unsupported shortcut in this case: Replacing all visible artifacts with private verbal status prevents inspection and adaptation. It does not show that Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence. [R158 R158-Q0510; case R158-C128; CAPM domain 3, task 3.3; source SCRUM.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests