100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 540
Which observed result supports acceptance of the XP-technical-practices corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
- Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.
- Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.
- Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.
Explanation
Correct Answer
B:The stated result demonstrates the case acceptance condition: Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. It depends on the decision Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; source ECO.]
C:The proposed outcome (Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; source ECO.]
D:The proposed outcome (Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; source ECO.]
Question 541
Which project-management decision best addresses the XP-technical-practices situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.
- 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.
- Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
Explanation
Correct Answer
A:The case evidence identifies A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. The specified decision directly addresses it: 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. This can be checked using Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0541; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
B:The proposed action (Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.) comes from 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. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0541; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
C: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 regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
D:This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. [R158 R158-Q0541; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Question 542
After a corrective decision on XP-technical-practices, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
- Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.
- Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
- Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
Explanation
Correct Answer
A:This checks the actual mechanism rather than merely declaring success: Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. The desired observed result is Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. [R158 R158-Q0542; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
B:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.) comes from 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. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0542; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
C:This option concerns 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. For the reported case, use this verification: Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
D:This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. [R158 R158-Q0542; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Question 543
Which statement most accurately flags a misleading shortcut to avoid in this XP-technical-practices case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence.
- Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
- Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
- 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
C:The shortcut is mistaken: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. The appropriate response is to 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.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. It is not an unsupported assumption.
B:This is an appropriate independent test of the proposed decision: Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
D:This is a supported decision, not the unsupported claim: 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. It responds to the actual project issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions.
Question 544
Select TWO case-specific elements of a justified XP-technical-practices resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
- 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.
- Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
- 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.
- Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
Explanation
Correct Answer
A:This checks the actual mechanism rather than merely declaring success: Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. The desired observed result is Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. [R158 R158-Q0544; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
D:The case evidence identifies A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. The specified decision directly addresses it: 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. This can be checked using Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0544; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
B:The proposed action (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.) comes from 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. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0544; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
C:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.) comes from 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. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline. [R158 R158-Q0544; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
E:This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The decision can be traced to the review evidence. [R158 R158-Q0544; case R158-C136; CAPM domain 3, task 3.4; source ECO.]
Question 545
Which project-management decision best addresses the Scaled-coordination-boundary situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
Explanation
Correct Answer
B:The case evidence identifies Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. The specified decision directly addresses it: Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment. This can be checked using Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0545; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
A:The proposed action (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.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0545; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
C:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. [R158 R158-Q0545; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
D:The proposed action (Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0545; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Question 546
After a corrective decision on Scaled-coordination-boundary, 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: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
- Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.
Explanation
Correct Answer
A:This checks the actual mechanism rather than merely declaring success: Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. The desired observed result is Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. [R158 R158-Q0546; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
B:The proposed verify (Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0546; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
C:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. [R158 R158-Q0546; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
D:The proposed verify (Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0546; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Question 547
Which statement most accurately flags a misleading shortcut to avoid in this Scaled-coordination-boundary case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls.
- Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.
- Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
Explanation
Correct Answer
A:The shortcut is mistaken: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. The appropriate response is to establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.
Incorrect Answers
B:This is a relevant outcome to seek after the decision: Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. It is not an unsupported assumption.
C:This is a supported decision, not the unsupported claim: Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment. It responds to the actual project issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task.
D:This is an appropriate independent test of the proposed decision: Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. It is not the invalid shortcut.
Question 548
Select TWO case-specific elements of a justified Scaled-coordination-boundary resolution : the decision and its direct evidence. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.
- Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
Explanation
Correct Answer
B:The case evidence identifies Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. The specified decision directly addresses it: Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment. This can be checked using Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0548; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
E:This checks the actual mechanism rather than merely declaring success: Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. The desired observed result is Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. [R158 R158-Q0548; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
A:The proposed action (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.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0548; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
C:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls. [R158 R158-Q0548; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
D:The proposed verify (Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit. [R158 R158-Q0548; case R158-C137; CAPM domain 3, task 3.4; source ECO.]
Question 549
Which project-management decision best addresses the Scaled-coordination-boundary situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- 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.
- Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
Explanation
Correct Answer
C:The case evidence identifies Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. The specified decision directly addresses it: 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. This can be checked using Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0549; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
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: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0549; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
B:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0549; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
D: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: Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
Question 550
After a corrective decision on Scaled-coordination-boundary, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
- Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.
- 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
B:This checks the actual mechanism rather than merely declaring success: Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. The desired observed result is Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
C:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.) comes from 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. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
D:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.) comes from 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. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests