PMI CAPM Practice Test 52
Question 510
For an original CAPM project delivery study scenario, consider: A subscription service starts a sprint with vague oversized items that lack shared understanding and cannot be estimated or tested before the next review. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Hold a Sprint Review to inspect product outcomes with stakeholders and adapt future backlog, and a separate Retrospective to improve the team's work practices.
- Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
- Check: Review item value, size, dependencies, acceptance criteria and selection evidence with Product Owner and delivery participants.
- Treat every unrefined feature as equally ready and work only in the order stakeholders sent their email requests.
- Change: Refine and order product backlog items by value, risk, dependency and readiness, splitting oversized work before selecting a feasible increment.
Explanation
Correct Answer
C:A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions. Required intervention: Refine and order product backlog items by value, risk, dependency and readiness, splitting oversized work before selecting a feasible increment.
E:A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions. Acceptance: The highest-priority feasible items are understood and can be delivered without hiding critical predecessor work or inflating scope mid-sprint.
Incorrect Answers
A:Change: Hold a Sprint Review to inspect product outcomes with stakeholders and adapt future backlog, and a separate Retrospective to improve the team's work practices. A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions.
B:Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items. A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions.
D:A product backlog is an evolving ordered list, not a frozen requirements contract; refinement improves transparency and selection decisions.
Question 511
A CAPM project team analyst is reviewing this delivery scenario: A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants. An unsafe shortcut would be: Fill the sprint to maximum historical story points regardless of holiday calendars and refuse to define a Sprint Goal. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
- Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more.
- Divide product value into small vertical slices that can form usable increments within repeatable short iterations and inspect each with stakeholders.
- Fill the sprint to maximum historical story points regardless of holiday calendars and refuse to define a Sprint Goal.
Explanation
Correct Answer
A:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Incorrect Answers
B:Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Divide product value into small vertical slices that can form usable increments within repeatable short iterations and inspect each with stakeholders. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
D:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 512
A project delivery review finds: A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants. The team proposes: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- An MVP is a deliberately limited evidence-gathering product outcome, not a low-quality unfinished artifact or a list of every requested enhancement.
- XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
- Scrum has distinct complementary accountabilities within one team, and daily management interference is not a substitute for self-management.
- Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Explanation
Correct Answer
D:Demonstrable success requires: The iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
Incorrect Answers
A:An MVP is a deliberately limited evidence-gathering product outcome, not a low-quality unfinished artifact or a list of every requested enhancement. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
B:This option addresses a different CAPM project management topic (Extreme Programming TDD and pairing) rather than the documented Sprint planning capacity and goal decision.
C:Scrum has distinct complementary accountabilities within one team, and daily management interference is not a substitute for self-management. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 513
The project team has not approved a broad project-plan change. Available evidence indicates: A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Compare team availability, historical completion, item size, dependencies and the goal against the proposed Sprint Backlog.
- Review shared service interfaces, dependency board, coordination objectives and the teams' ability to replan after integration feedback.
- Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback.
- Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
Explanation
Correct Answer
A:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Incorrect Answers
B:Review shared service interfaces, dependency board, coordination objectives and the teams' ability to replan after integration feedback. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
D:Audit request, start and finish timestamps and weekly completion totals for a sample of representative items. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 514
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants. 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.
- Product goals guide ordered work while Developers manage delivery and the Scrum Master helps remove systemic impediments.
- Early release evidence informs future scope and meets necessary quality and compliance requirements without carrying optional features first.
- The iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
Explanation
Correct Answer
D:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Incorrect Answers
A:Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
B:Product goals guide ordered work while Developers manage delivery and the Scrum Master helps remove systemic impediments. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Early release evidence informs future scope and meets necessary quality and compliance requirements without carrying optional features first. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 515
An implementation sign-off request identifies the following problem: A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants. Which paired project management action and verification should close the review? Select ONE best answer.
- Change: Coordinate cross-team objectives, dependencies, capacity and integration cadence through appropriate scaled planning while preserving feedback and autonomy. Verify: Review shared service interfaces, dependency board, coordination objectives and the teams' ability to replan after integration feedback.
- 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: Distinguish lead time from request to completion, cycle time from start of work to completion and throughput as units completed per time period. Verify: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
- 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.
Explanation
Correct Answer
D:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Incorrect Answers
A:Change: Coordinate cross-team objectives, dependencies, capacity and integration cadence through appropriate scaled planning while preserving feedback and autonomy. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
B:Change: Visualize flow stages and blocked work, apply realistic work-in-progress limits and finish existing items before starting more. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Change: Distinguish lead time from request to completion, cycle time from start of work to completion and throughput as units completed per time period. A team with three developers on leave chooses as much sprint work as last month solely because the previous sprint had more participants.
Question 516
A CAPM project team analyst is reviewing this delivery scenario: A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations. An unsafe shortcut would be: Fill the sprint to maximum historical story points regardless of holiday calendars and refuse to define a Sprint Goal. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Maintain transparent sprint or Kanban boards and appropriate progress charts, using actual completed work, blockers and scope changes to adapt the plan.
- Use a brief daily planning event for Developers to inspect progress toward their goal, coordinate next work and surface impediments for timely resolution.
- Fill the sprint to maximum historical story points regardless of holiday calendars and refuse to define a Sprint Goal.
- Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
Explanation
Correct Answer
D:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Incorrect Answers
A:Maintain transparent sprint or Kanban boards and appropriate progress charts, using actual completed work, blockers and scope changes to adapt the plan. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
B:This option addresses a different CAPM project management topic (Daily Scrum purpose and impediments) rather than the documented Sprint planning capacity and goal decision.
C:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 517
A project delivery review finds: A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations. The team proposes: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan. 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.
- Flow measurements answer different questions about service predictability and should be tied to consistent stage definitions.
- Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item.
- Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Explanation
Correct Answer
D:Demonstrable success requires: The iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
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. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
B:Flow measurements answer different questions about service predictability and should be tied to consistent stage definitions. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:This option addresses a different CAPM project management topic (Definition of Done and acceptance criteria) rather than the documented Sprint planning capacity and goal decision.
Question 518
The project team has not approved a broad project-plan change. Available evidence indicates: A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Compare team availability, historical completion, item size, dependencies and the goal against the proposed Sprint Backlog.
- Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step.
- Review team availability, dependency queues, specialist handoffs, release approval lead time and stakeholder participation between iterations.
- Review shared service interfaces, dependency board, coordination objectives and the teams' ability to replan after integration feedback.
Explanation
Correct Answer
A:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee. Confirm afterward that: The iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
Incorrect Answers
B:Inspect stage WIP, throughput, blocked duration and before-after cycle time for the actual constrained work step. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Review team availability, dependency queues, specialist handoffs, release approval lead time and stakeholder participation between iterations. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
D:Review shared service interfaces, dependency board, coordination objectives and the teams' ability to replan after integration feedback. A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations.
Question 519
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations. 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 iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
- Mandatory certifications remain traceable while customer-facing details can evolve through feedback without violating delivery dependencies.
- Stakeholders understand remaining work and impediments with honest forecasts rather than cosmetic percent-complete numbers.
- Each cycle produces transparent progress toward a usable outcome and any incomplete item remains visible instead of being renamed done.
Explanation
Correct Answer
A:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee. The approved implementation step was: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
Incorrect Answers
B:Mandatory certifications remain traceable while customer-facing details can evolve through feedback without violating delivery dependencies. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
C:Stakeholders understand remaining work and impediments with honest forecasts rather than cosmetic percent-complete numbers. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
D:Each cycle produces transparent progress toward a usable outcome and any incomplete item remains visible instead of being renamed done. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
Question 520
For an original CAPM project delivery study scenario, consider: A team assembles unrelated small backlog items into a sprint without identifying the outcome that should unite delivery and stakeholder expectations. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
- Change: Refine and order product backlog items by value, risk, dependency and readiness, splitting oversized work before selecting a feasible increment.
- Check: Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies.
- Fill the sprint to maximum historical story points regardless of holiday calendars and refuse to define a Sprint Goal.
- Check: Compare team availability, historical completion, item size, dependencies and the goal against the proposed Sprint Backlog.
Explanation
Correct Answer
A:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee. Acceptance: The iteration has an agreed outcome and credible work forecast without routine overcommitment caused by absent contributors.
E:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee. Required intervention: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
Incorrect Answers
B:This option addresses a different CAPM project management topic (Product backlog ordering and refinement) rather than the documented Sprint planning capacity and goal decision.
C:Check: Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies. Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.
D:Sprint planning accounts for why the work matters, what can be done and how Developers expect to do it; past throughput is supporting evidence, not a commitment guarantee.