PMI CAPM Exam Dumps, Practice Test Questions

100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

PMI CAPM Premium Bundle
$79.97
$59.98

CAPM Premium Bundle

  • Premium File: 688 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 123 Video Lectures
  • Study Guide: 719 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

CAPM Premium Bundle

PMI CAPM Premium Bundle
  • Premium File: 688 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 123 Video Lectures
  • Study Guide: 719 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

PMI CAPM Practice Test 50

Question 490

After a corrective decision on Burndown-versus-value, which independent evidence most directly verifies the result ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. 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.
  2. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  3. 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.
  4. Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. The desired observed result is The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

Incorrect Answers

A:

The proposed verify (Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

B:

This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

C:

The proposed verify (Compare selected work with known capacity, dependency readiness and done evidence at the end of the iteration. Reconcile the result with the current approved decision baseline.) comes from a different Iteration planning situation: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0490; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

Question 491

Which statement most accurately flags a misleading shortcut to avoid in this Burndown-versus-value case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls.
  2. Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.
  3. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  4. Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.

Explanation

Correct Answer

C:

The shortcut is mistaken: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. The appropriate response is to track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a relevant outcome to seek after the decision: The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. It is not an unsupported assumption.

B:

This is a supported decision, not the unsupported claim: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment. It responds to the actual project issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done.

D:

This is an appropriate independent test of the proposed decision: Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. It is not the invalid shortcut.

Question 492

Select THREE consistent elements of the Burndown-versus-value 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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.
  2. Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit.
  3. Select a realistic slice of ready work using capacity, past performance and completion criteria during iteration planning. Record the rationale before the next commitment.
  4. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  5. The team delivers usable functionality early rather than only completing isolated technical layers. The result is recorded in the project controls.
  6. The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls.

Explanation

Correct Answer

A:

The case evidence identifies An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. The specified decision directly addresses it: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment. This can be checked using Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0492; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

B:

This checks the actual mechanism rather than merely declaring success: Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. The desired observed result is The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0492; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

F:

The stated result demonstrates the case acceptance condition: The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. It depends on the decision Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Record the rationale before the next commitment.

Incorrect Answers

C:

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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0492; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The result is recorded in the project controls. [R158 R158-Q0492; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

E:

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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Retain the initiating evidence for audit. [R158 R158-Q0492; case R158-C123; CAPM domain 3, task 3.2; source SCRUM.]

Question 493

Which project-management decision best addresses the Burndown-versus-value situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. 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.
  2. Have the Product Owner re-evaluate backlog priority using stakeholder evidence while preserving transparent product goals. Record the rationale before the next commitment.
  3. Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.
  4. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.

Explanation

Correct Answer

C:

The case evidence identifies An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. The specified decision directly addresses it: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0493; case R158-C124; 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. Document impacted stakeholders and the decision owner at the review.) comes from a different Iteration planning situation: A predictive decomposition lists a complete reporting module but business stakeholders want one useful report available early. It does not resolve or independently test the stated issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0493; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

B:

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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0493; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. [R158 R158-Q0493; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

Question 494

After a corrective decision on Burndown-versus-value, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect each slice's user acceptance criteria and whether it can be demonstrated without the full module. Retain the initiating evidence for audit.
  2. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  3. Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.
  4. 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

C:

This checks the actual mechanism rather than merely declaring success: Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. The desired observed result is The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. [R158 R158-Q0494; case R158-C124; 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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0494; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

B:

This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. [R158 R158-Q0494; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

D:

This option concerns a different Iteration planning situation: A team commits to seven complex stories without considering historical capacity, dependencies or Definition of Done. For the reported case, use this verification: Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.

Question 495

Which statement most accurately flags a misleading shortcut to avoid in this Burndown-versus-value case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.
  2. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  3. Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.
  4. The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence.

Explanation

Correct Answer

B:

The shortcut is mistaken: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. The appropriate response is to track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

A:

This is an appropriate independent test of the proposed decision: Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

C:

This is a supported decision, not the unsupported claim: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done.

D:

This is a relevant outcome to seek after the decision: The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. It is not an unsupported assumption.

Question 496

Select THREE consistent elements of the Burndown-versus-value case: appropriate decision, verification, and observable success condition. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.
  2. Burning hours on unfinished features is not equivalent to delivering an accepted Increment.
  3. The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence.
  4. The next iterations reflect validated value rather than treating the initial backlog order as immutable. The decision can be traced to the review evidence.
  5. Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline.
  6. 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 An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. The specified decision directly addresses it: Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0496; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

C:

The stated result demonstrates the case acceptance condition: The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. It depends on the decision Track demonstrably completed product value and done work, not merely hours spent or tasks marked in progress. Document impacted stakeholders and the decision owner at the review.

E:

This checks the actual mechanism rather than merely declaring success: Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. The desired observed result is The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. [R158 R158-Q0496; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

Incorrect Answers

B:

This is a tempting but unsupported shortcut in this case: Burning hours on unfinished features is not equivalent to delivering an accepted Increment. It does not show that The team can distinguish real delivery progress from optimistic effort reporting. The decision can be traced to the review evidence. [R158 R158-Q0496; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

D:

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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0496; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

F:

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: An iteration burndown drops rapidly although several completed tasks do not meet acceptance or Definition of Done. Here, the relevant check is Compare progress visuals with objectively accepted Increment items and remaining work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0496; case R158-C124; CAPM domain 3, task 3.2; source SCRUM.]

Question 497

Which project-management decision best addresses the Increment-evidence-control situation ? 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.

  1. Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
  2. Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Record the rationale before the next commitment.
  3. Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.
  4. 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.

Explanation

Correct Answer

C:

Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment. To verify the specified result, review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit.

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 result is recorded in the project controls. [R158 R158-Q0497; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]

B:

The proposed action (Agree a shared minimum Definition of Done for the product and inspect integrated results against it. Record the rationale before the next commitment.) 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-Q0497; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]

D:

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. Retain the initiating evidence for audit. [R158 R158-Q0497; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]

Question 498

After a corrective decision on Increment-evidence-control, 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 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.

  1. Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline.
  2. Inspect whether stakeholders can see ordered product work, the current Sprint plan and done outcomes. Retain the initiating evidence for audit.
  3. Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit.
  4. Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.

Explanation

Correct Answer

C:

Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit. The expected result is only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.

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 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-Q0498; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]

B:

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. Retain the initiating evidence for audit. [R158 R158-Q0498; case R158-C125; 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 result is recorded in the project controls. [R158 R158-Q0498; case R158-C125; CAPM domain 3, task 3.3; source SCRUM.]

Question 499

Which statement most accurately flags a misleading shortcut to avoid in this Increment-evidence-control case? 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.

  1. Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.
  2. Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
  3. Apply the team's Definition of Done consistently and do not include unfinished work in the Increment. Record the rationale before the next commitment.
  4. Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit.

Explanation

Correct Answer

B:

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. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a relevant outcome to seek after the decision: Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls. It is not an unsupported assumption.

C:

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. Record the rationale before the next commitment. It responds to the actual project issue: A Scrum team labels an unfinished feature as a production-ready Increment despite failing integration tests.

D:

This is an appropriate independent test of the proposed decision: Review test results and completion criteria for each purportedly finished backlog item. Retain the initiating evidence for audit. It is not the invalid shortcut.

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.

  1. Decisions draw on a current shared view of value, work and results. The decision can be traced to the review evidence.
  2. Calling a partially tested build done simply because the Sprint ends bypasses the stated quality control.
  3. Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.
  4. 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.]

Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.