PMI CAPM Practice Test 58
Question 570
For an original CAPM project delivery study scenario, consider: A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
- Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
- Reward engineers for maximizing story points and assume points have identical meaning across all teams and products.
- Check: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
- Change: Prioritize a small usable release that tests the key value hypothesis and sequence later capabilities based on observed feedback and constraints.
Explanation
Correct Answer
A:Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. Evidence: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
D:Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. Required intervention: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
Incorrect Answers
B:Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.
C:Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.
E:This option addresses a different CAPM project management topic (Minimum viable product and release planning) rather than the documented Velocity forecasting without productivity misuse decision.
Question 571
A CAPM project team analyst is reviewing this delivery scenario: A service team has thirty tasks in progress but only two can be tested at once, leading to long waiting queues and frequent context switches. An unsafe shortcut would be: Remove every work-in-progress limit and judge success solely by the number of items started each day. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Use a brief daily planning event for Developers to inspect progress toward their goal, coordinate next work and surface impediments for timely resolution.
- Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
- Remove every work-in-progress limit and judge success solely by the number of items started each day.
- Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
Explanation
Correct Answer
B:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
A:Use a brief daily planning event for Developers to inspect progress toward their goal, coordinate next work and surface impediments for timely resolution. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
D:Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 572
A project delivery review finds: A service team has thirty tasks in progress but only two can be tested at once, leading to long waiting queues and frequent context switches. The team proposes: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- An iteration is a timeboxed learning or delivery cycle; an increment is an integrated usable addition that meets the team's quality standard.
- Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
- The Daily Scrum is primarily for the Developers' adaptation and coordination; it is not an obligatory management interrogation or substitute for deeper problem-solving.
- Scrum has distinct complementary accountabilities within one team, and daily management interference is not a substitute for self-management.
Explanation
Correct Answer
B:Demonstrable success requires: Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests. This principle explains the proposed project response, which is: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
Incorrect Answers
A:An iteration is a timeboxed learning or delivery cycle; an increment is an integrated usable addition that meets the team's quality standard. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:The Daily Scrum is primarily for the Developers' adaptation and coordination; it is not an obligatory management interrogation or substitute for deeper problem-solving. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
D:Scrum has distinct complementary accountabilities within one team, and daily management interference is not a substitute for self-management. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 573
The project team has not approved a broad project-plan change. Available evidence indicates: A service team has thirty tasks in progress but only two can be tested at once, leading to long waiting queues and frequent context switches. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
- Review iteration length, backlog slicing, integration evidence, usable functionality and actual inspection feedback after each cycle.
- Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies.
- Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
Explanation
Correct Answer
D:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
A:This option addresses a different CAPM project management topic (Extreme Programming TDD and pairing) rather than the documented Kanban work-in-progress limits decision.
B:Review iteration length, backlog slicing, integration evidence, usable functionality and actual inspection feedback after each cycle. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 574
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A service team has thirty tasks in progress but only two can be tested at once, leading to long waiting queues and frequent context switches. The accountable project owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the project response meets the intended outcome? Select ONE best answer.
- Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations.
- Mandatory certifications remain traceable while customer-facing details can evolve through feedback without violating delivery dependencies.
- Early release evidence informs future scope and meets necessary quality and compliance requirements without carrying optional features first.
- Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests.
Explanation
Correct Answer
D:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion. The approved implementation step was: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
Incorrect Answers
A:Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
B:This option addresses a different CAPM project management topic (Hybrid predictive and adaptive governance) rather than the documented Kanban work-in-progress limits decision.
C:Early release evidence informs future scope and meets necessary quality and compliance requirements without carrying optional features first. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 575
An implementation sign-off request identifies the following problem: A service team has thirty tasks in progress but only two can be tested at once, leading to long waiting queues and frequent context switches. Which paired project management action and verification should close the review? Select ONE best answer.
- Change: Use an adaptive approach with short feedback cycles, a prioritized evolving backlog and clear product outcomes when needs remain uncertain. Verify: Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback.
- Change: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan. Verify: Compare team availability, historical completion, item size, dependencies and the goal against the proposed Sprint Backlog.
- Change: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more. Verify: Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
- Change: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets. Verify: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
Explanation
Correct Answer
C:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
A:Change: Use an adaptive approach with short feedback cycles, a prioritized evolving backlog and clear product outcomes when needs remain uncertain. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
B:This option addresses a different CAPM project management topic (Sprint planning capacity and goal) rather than the documented Kanban work-in-progress limits decision.
D:Change: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
Question 576
A CAPM project team analyst is reviewing this delivery scenario: A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck. An unsafe shortcut would be: Remove every work-in-progress limit and judge success solely by the number of items started each day. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
- Establish sufficiently available cross-functional capacity and fit compliance checkpoints into the chosen adaptive delivery cadence before committing to iteration goals.
- Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
- Remove every work-in-progress limit and judge success solely by the number of items started each day.
Explanation
Correct Answer
A:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
B:Establish sufficiently available cross-functional capacity and fit compliance checkpoints into the chosen adaptive delivery cadence before committing to iteration goals. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
D:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion. Use this instead: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
Question 577
A project delivery review finds: A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck. The team proposes: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Adaptive delivery intentionally learns from working increments and stakeholder evidence; it does not imply the absence of goals, risk controls or accountability.
- Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
- A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions.
- Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.
Explanation
Correct Answer
B:Demonstrable success requires: Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests.
Incorrect Answers
A:Adaptive delivery intentionally learns from working increments and stakeholder evidence; it does not imply the absence of goals, risk controls or accountability. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:This option addresses a different CAPM project management topic (Product backlog ordering and refinement) rather than the documented Kanban work-in-progress limits decision.
D:Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 578
The project team has not approved a broad project-plan change. Available evidence indicates: A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback.
- Check backlog ownership, sprint planning decisions, impediment handling and who actually updates the Sprint Backlog.
- Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
- Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
Explanation
Correct Answer
D:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
A:Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
B:Check backlog ownership, sprint planning decisions, impediment handling and who actually updates the Sprint Backlog. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:Audit request, start and finish timestamps and weekly completion totals for a sample of representative items. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 579
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck. The accountable project owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the project response meets the intended outcome? Select ONE best answer.
- The team can explain the user outcome and verify it through specific acceptance examples when the increment is reviewed.
- Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests.
- Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations.
- Stakeholder feedback affects product direction while internal process changes have owners and measurable follow-through.
Explanation
Correct Answer
B:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Incorrect Answers
A:This option addresses a different CAPM project management topic (User stories and testable acceptance) rather than the documented Kanban work-in-progress limits decision.
C:Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations. A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck.
D:Stakeholder feedback affects product direction while internal process changes have owners and measurable follow-through. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
Question 580
For an original CAPM project delivery study scenario, consider: A maintenance board shows every item in 'In Progress' even when work is blocked, so managers launch more tasks instead of resolving the testing bottleneck. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
- Remove every work-in-progress limit and judge success solely by the number of items started each day.
- Change: Establish sufficiently available cross-functional capacity and fit compliance checkpoints into the chosen adaptive delivery cadence before committing to iteration goals.
- Check: Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback.
- Check: Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
Explanation
Correct Answer
A:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion. Evidence: Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
E:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion. Required intervention: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
Incorrect Answers
B:Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
C:Change: Establish sufficiently available cross-functional capacity and fit compliance checkpoints into the chosen adaptive delivery cadence before committing to iteration goals. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.
D:Check: Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.