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 53

Question 520

Which observed result supports acceptance of the Definition-of-Done-adaptation corrective decision ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Two teams integrating one product use conflicting completion rules, and defects pass between them. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Integrated work meets consistent quality expectations without hiding unfinished dependencies. The decision can be traced to the review evidence.
  2. Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.
  3. Allowing each team to redefine done after defects appear undermines transparency and integration.
  4. Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls.

Explanation

Correct Answer

A:

The stated result demonstrates the case acceptance condition: Integrated work meets consistent quality expectations without hiding unfinished dependencies. The decision can be traced to the review evidence. It depends on the decision 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.

Incorrect Answers

B:

The proposed outcome (Only work meeting the shared quality commitment is counted as completed Increment value. The result is recorded in the project controls.) 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: Two teams integrating one product use conflicting completion rules, and defects pass between them. Here, the relevant check is Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline. [R158 R158-Q0520; case R158-C130; CAPM domain 3, task 3.3; source SCRUM.]

C:

This is a tempting but unsupported shortcut in this case: Allowing each team to redefine done after defects appear undermines transparency and integration. It does not show that Integrated work meets consistent quality expectations without hiding unfinished dependencies. The decision can be traced to the review evidence. [R158 R158-Q0520; case R158-C130; CAPM domain 3, task 3.3; source SCRUM.]

D:

The proposed outcome (Decisions draw on a current shared view of value, work and results. The result is recorded in the project controls.) 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: Two teams integrating one product use conflicting completion rules, and defects pass between them. Here, the relevant check is Check common quality criteria and test evidence for cross-team Increment integration. Reconcile the result with the current approved decision baseline. [R158 R158-Q0520; case R158-C130; CAPM domain 3, task 3.3; source SCRUM.]

Question 521

Which project-management decision best addresses the Scrum-roles-and-accountabilities situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  2. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.
  3. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
  4. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.

Explanation

Correct Answer

D:

The case evidence identifies A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. The specified decision directly addresses it: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment. This can be checked using Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0521; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. [R158 R158-Q0521; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

B:

This option concerns a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. For the reported case, use this verification: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.

C:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0521; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Question 522

After a corrective decision on Scrum-roles-and-accountabilities, 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 department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.
  2. Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
  3. Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
  4. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.

Explanation

Correct Answer

A:

This checks the actual mechanism rather than merely declaring success: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. The desired observed result is Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. [R158 R158-Q0522; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

B:

The proposed verify (Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0522; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

C:

The proposed verify (Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0522; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. [R158 R158-Q0522; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Question 523

Which statement most accurately flags a misleading shortcut to avoid in this Scrum-roles-and-accountabilities case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls.
  2. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  3. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.
  4. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.

Explanation

Correct Answer

B:

The shortcut is mistaken: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. The appropriate response is to respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a relevant outcome to seek after the decision: Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. It is not an unsupported assumption.

C:

This is a supported decision, not the unsupported claim: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment. It responds to the actual project issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner.

D:

This is an appropriate independent test of the proposed decision: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. It is not the invalid shortcut.

Question 524

Select TWO case-specific elements of a justified Scrum-roles-and-accountabilities 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 department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
  2. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.
  3. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.
  4. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  5. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.

Explanation

Correct Answer

B:

The case evidence identifies A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. The specified decision directly addresses it: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment. This can be checked using Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0524; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

C:

This checks the actual mechanism rather than merely declaring success: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. The desired observed result is Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. [R158 R158-Q0524; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

A:

The proposed verify (Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0524; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls. [R158 R158-Q0524; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

E:

The proposed action (Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit. [R158 R158-Q0524; case R158-C131; CAPM domain 3, task 3.4; source SCRUM.]

Question 525

Which project-management decision best addresses the Scrum-roles-and-accountabilities situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.
  2. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review.
  3. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
  4. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.

Explanation

Correct Answer

B:

The case evidence identifies A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. The specified decision directly addresses it: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0525; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

A:

The proposed action (Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0525; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

C:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0525; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence. [R158 R158-Q0525; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Question 526

After a corrective decision on Scrum-roles-and-accountabilities, 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 department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
  2. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  3. Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
  4. Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

A:

This checks the actual mechanism rather than merely declaring success: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. The desired observed result is Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence. [R158 R158-Q0526; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

B:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence. [R158 R158-Q0526; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

C:

The proposed verify (Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0526; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

D:

The proposed verify (Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0526; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Question 527

Which statement most accurately flags a misleading shortcut to avoid in this Scrum-roles-and-accountabilities case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review.
  2. Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence.
  3. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  4. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

C:

The shortcut is mistaken: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. The appropriate response is to respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

A:

This is a supported decision, not the unsupported claim: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner.

B:

This is a relevant outcome to seek after the decision: Value priorities and technical execution responsibilities are clear and collaborative. 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: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

Question 528

Select TWO case-specific elements of a justified Scrum-roles-and-accountabilities resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review.
  2. Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.
  3. Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum.
  4. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
  5. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

A:

The case evidence identifies A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. The specified decision directly addresses it: Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0528; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

D:

This checks the actual mechanism rather than merely declaring success: Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. The desired observed result is Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence. [R158 R158-Q0528; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Incorrect Answers

B:

The proposed verify (Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0528; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

C:

This is a tempting but unsupported shortcut in this case: Substituting a manager's private task orders for both Product Owner and Developers' accountabilities is not Scrum. It does not show that Value priorities and technical execution responsibilities are clear and collaborative. The decision can be traced to the review evidence. [R158 R158-Q0528; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

E:

The proposed action (Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. Here, the relevant check is Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline. [R158 R158-Q0528; case R158-C132; CAPM domain 3, task 3.4; source SCRUM.]

Question 529

Which project-management decision best addresses the Kanban-WIP-limits situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
  2. Starting more cases whenever a worker is free can increase WIP and delay completion.
  3. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
  4. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.

Explanation

Correct Answer

A:

The case evidence identifies A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. The specified decision directly addresses it: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment. This can be checked using Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0529; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

B:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0529; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

C:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0529; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

D:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0529; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

Question 530

After a corrective decision on Kanban-WIP-limits, 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 service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Starting more cases whenever a worker is free can increase WIP and delay completion.
  2. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
  3. Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
  4. Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. The desired observed result is Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0530; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0530; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

B:

This option concerns a different Adaptive plan and methodologies situation: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. For the reported case, use this verification: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

C:

This option concerns a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. For the reported case, use this verification: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

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.