cert
cert-1
cert-2

Pass PMI CAPM Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
CAPM Exam - Verified By Experts
CAPM Premium Bundle
$29.98

CAPM Premium Bundle

$79.99
$109.97
  • Premium File 688 Questions & Answers. Last update: Nov 21, 2026
  • Training Course 123 Video Lectures
  • Study Guide 719 Pages
 
$109.97
$79.99
accept 19 downloads in last 7 days
block-screenshots
Purchase PMI CAPM Exam Training Products Individually
PMI CAPM Premium File
Premium File 688 Q&A
$76.99$69.99
PMI CAPM Video Training Course
Training Course 123 Lectures
$21.99 $19.99
PMI CAPM PDF Study Guide
Study Guide 719 Pages
$21.99 $19.99
PMI CAPM Practice Test 57

Question 560

For an original CAPM project delivery study scenario, consider: A specific payment story passes its business acceptance examples, but the increment lacks the shared performance checks required of every release. Select TWO complementary steps: the targeted correction and its strongest prechange validation.

  1. Check: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
  2. Check: Examine the team Definition of Done, item acceptance tests, code/test evidence and unresolved release quality controls.
  3. Treat passing one user demo as permission to skip all shared automated tests and operational readiness checks.
  4. Change: Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components.
  5. Change: Apply consistent Definition of Done quality standards to the increment and separately verify item-level acceptance criteria before treating work as complete.

Explanation

Correct Answer

B:

Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item. Required intervention: Apply consistent Definition of Done quality standards to the increment and separately verify item-level acceptance criteria before treating work as complete.

E:

Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item. Evidence: Examine the team Definition of Done, item acceptance tests, code/test evidence and unresolved release quality controls.

Incorrect Answers

A:

Check: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature. Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item.

C:

Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item.

D:

Change: Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components. A specific payment story passes its business acceptance examples, but the increment lacks the shared performance checks required of every release.

Question 561

A CAPM project team analyst is reviewing this delivery scenario: A manager converts one team's story points into individual productivity rankings and demands that each engineer match the highest-point colleague. An unsafe shortcut would be: Reward engineers for maximizing story points and assume points have identical meaning across all teams and products. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.

  1. Reward engineers for maximizing story points and assume points have identical meaning across all teams and products.
  2. Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
  3. Maintain transparent sprint or Kanban boards and appropriate progress charts, using actual completed work, blockers and scope changes to adapt the plan.
  4. Use a brief daily planning event for Developers to inspect progress toward their goal, coordinate next work and surface impediments for timely resolution.

Explanation

Correct Answer

B:

Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Incorrect Answers

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.

C:

This option addresses a different CAPM project management topic (Adaptive visibility with boards and burndown) rather than the documented Velocity forecasting without productivity misuse decision.

D:

Use a brief daily planning event for Developers to inspect progress toward their goal, coordinate next work and surface impediments for timely resolution. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 562

A project delivery review finds: A manager converts one team's story points into individual productivity rankings and demands that each engineer match the highest-point colleague. The team proposes: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets. Which project management principle most strongly supports the proposed response? Select ONE best answer.

  1. Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item.
  2. An iteration is a timeboxed learning or delivery cycle; an increment is an integrated usable addition that meets the team's quality standard.
  3. Adaptive delivery intentionally learns from working increments and stakeholder evidence; it does not imply the absence of goals, risk controls or accountability.
  4. 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

D:

Relevant validation before approval: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date. This principle explains the proposed project response, which is: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.

Incorrect Answers

A:

Definition of Done is a common quality commitment for the increment, while acceptance criteria express behavior expected of a particular backlog item. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

B:

An iteration is a timeboxed learning or delivery cycle; an increment is an integrated usable addition that meets the team's quality standard. 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:

Adaptive delivery intentionally learns from working increments and stakeholder evidence; it does not imply the absence of goals, risk controls or accountability. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 563

The project team has not approved a broad project-plan change. Available evidence indicates: A manager converts one team's story points into individual productivity rankings and demands that each engineer match the highest-point colleague. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.

  1. Examine the team Definition of Done, item acceptance tests, code/test evidence and unresolved release quality controls.
  2. Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
  3. Review item value, size, dependencies, acceptance criteria and selection evidence with Product Owner and delivery participants.
  4. Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback.

Explanation

Correct Answer

B:

Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. If confirmed, the proportionate intervention is: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.

Incorrect Answers

A:

Examine the team Definition of Done, item acceptance tests, code/test evidence and unresolved release quality controls. 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:

Review item value, size, dependencies, acceptance criteria and selection evidence with Product Owner and delivery participants. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

D:

Inspect uncertainty, availability of real users, increment release cost, safety dependencies and options to respond to feedback. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 564

A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A manager converts one team's story points into individual productivity rankings and demands that each engineer match the highest-point colleague. 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.

  1. The team can explain the user outcome and verify it through specific acceptance examples when the increment is reviewed.
  2. Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items.
  3. Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations.
  4. The team adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate.

Explanation

Correct Answer

B:

Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. The approved implementation step was: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.

Incorrect Answers

A:

This option addresses a different CAPM project management topic (User stories and testable acceptance) rather than the documented Velocity forecasting without productivity misuse decision.

C:

Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

D:

The team adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 565

An implementation sign-off request identifies the following problem: A manager converts one team's story points into individual productivity rankings and demands that each engineer match the highest-point colleague. Which paired project management action and verification should close the review? Select ONE best answer.

  1. 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.
  2. Change: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles. Verify: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
  3. Change: Establish sufficiently available cross-functional capacity and fit compliance checkpoints into the chosen adaptive delivery cadence before committing to iteration goals. Verify: Review team availability, dependency queues, specialist handoffs, release approval lead time and stakeholder participation between iterations.
  4. 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

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.

Incorrect Answers

B:

This option addresses a different CAPM project management topic (Extreme Programming TDD and pairing) rather than the documented Velocity forecasting without productivity misuse decision.

C:

This option addresses a different CAPM project management topic (Adaptive readiness in matrix organizations) rather than the documented Velocity forecasting without productivity misuse decision.

D:

Change: Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 566

A CAPM project team analyst is reviewing this delivery scenario: A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity. An unsafe shortcut would be: Reward engineers for maximizing story points and assume points have identical meaning across all teams and products. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.

  1. Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
  2. Reward engineers for maximizing story points and assume points have identical meaning across all teams and products.
  3. Divide product value into small vertical slices that can form usable increments within repeatable short iterations and inspect each with stakeholders.
  4. Preserve Product Owner accountability for product value and backlog ordering, Scrum Master support for Scrum effectiveness and Developers' ownership of the sprint execution plan.

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.

Incorrect Answers

B:

Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence. Use this instead: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.

C:

Divide product value into small vertical slices that can form usable increments within repeatable short iterations and inspect each with stakeholders. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

D:

This option addresses a different CAPM project management topic (Scrum accountabilities and team ownership) rather than the documented Velocity forecasting without productivity misuse decision.

Question 567

A project delivery review finds: A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity. The team proposes: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets. Which project management principle most strongly supports the proposed response? Select ONE best answer.

  1. Different project components can benefit from different delivery approaches when dependencies and acceptance boundaries are deliberately coordinated.
  2. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.
  3. 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.
  4. Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion.

Explanation

Correct Answer

B:

Relevant validation before approval: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.

Incorrect Answers

A:

Different project components can benefit from different delivery approaches when dependencies and acceptance boundaries are deliberately coordinated. 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:

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. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

D:

Kanban controls flow by limiting concurrent work; excess WIP amplifies queues and hides bottlenecks rather than improving completion. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 568

The project team has not approved a broad project-plan change. Available evidence indicates: A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.

  1. Review item value, size, dependencies, acceptance criteria and selection evidence with Product Owner and delivery participants.
  2. Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
  3. Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
  4. Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams.

Explanation

Correct Answer

B:

Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Incorrect Answers

A:

Review item value, size, dependencies, acceptance criteria and selection evidence with Product Owner and delivery participants. A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity.

C:

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.

D:

Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

Question 569

A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity. 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.

  1. Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests.
  2. The highest-priority feasible items are understood and can be delivered without hiding critical predecessor work or inflating scope mid-sprint.
  3. The team adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate.
  4. Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items.

Explanation

Correct Answer

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.

Incorrect Answers

A:

Work moves predictably through stages with fewer stalled items and transparent exceptions for urgent requests. Story points and velocity are relative to a team and may not compare meaningfully across teams; forecasts need stable context and recent empirical evidence.

B:

The highest-priority feasible items are understood and can be delivered without hiding critical predecessor work or inflating scope mid-sprint. 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:

The team adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate. A product owner projects completion dates from one unusually large sprint and ignores recent volatility, scope changes and team capacity.

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.

  1. Change: Use team-level historical throughput or velocity as a contextual forecasting aid, with ranges and explicit assumptions rather than individual performance targets.
  2. Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
  3. Reward engineers for maximizing story points and assume points have identical meaning across all teams and products.
  4. Check: Review several iteration completion totals, scope churn, availability changes and forecasting confidence before communicating a date.
  5. 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.

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