PMI CAPM Practice Test 60
Question 590
For an original CAPM project delivery study scenario, consider: A Kanban board shows ten completed items weekly, yet a manager says that number is the median time customers waited for each item. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components.
- Change: Distinguish lead time from request to completion, cycle time from start of work to completion and throughput as units completed per time period.
- Treat weekly throughput as identical to elapsed lead time and exclude all waiting queues from customer service metrics.
- Check: Review whether the meeting updates the work plan, exposes blocked flow and assigns follow-up without lengthy unrelated problem resolution.
- Check: Audit request, start and finish timestamps and weekly completion totals for a sample of representative items.
Explanation
Correct Answer
B:Acceptance: Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations.
E:Acceptance: Stakeholders receive accurate waiting-time and work-time measures rather than misleading counts presented as elapsed durations. Flow measurements answer different questions about service predictability and should be tied to consistent stage definitions.
Incorrect Answers
A:Change: Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components. A Kanban board shows ten completed items weekly, yet a manager says that number is the median time customers waited for each item.
C:Flow measurements answer different questions about service predictability and should be tied to consistent stage definitions.
D:Check: Review whether the meeting updates the work plan, exposes blocked flow and assigns follow-up without lengthy unrelated problem resolution. Flow measurements answer different questions about service predictability and should be tied to consistent stage definitions.
Question 591
A CAPM project team analyst is reviewing this delivery scenario: A high-defect product team adds end-of-quarter regression testing yet refuses to consider frequent automated feedback or small safe code changes. An unsafe shortcut would be: Call the project Extreme Programming because engineers sit together while skipping any automated verification. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles.
- Refine and order product backlog items by value, risk, dependency and readiness, splitting oversized work before selecting a feasible increment.
- Call the project Extreme Programming because engineers sit together while skipping any automated verification.
- Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Incorrect Answers
B:This option addresses a different CAPM project management topic (Product backlog ordering and refinement) rather than the documented Extreme Programming TDD and pairing decision.
C:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:Use an appropriate hybrid approach with controlled milestone and compliance gates plus adaptive learning within uncertain product components. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 592
A project delivery review finds: A high-defect product team adds end-of-quarter regression testing yet refuses to consider frequent automated feedback or small safe code changes. The team proposes: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- A user-oriented backlog item communicates beneficiary and intended value, while acceptance criteria clarify observable behavior without prescribing every implementation detail.
- Scaling introduces explicit alignment and dependency management; large planning events should not erase the need to inspect and adapt when evidence changes.
- XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
- Product inspection and team process reflection address different questions; both feedback loops help adaptive planning remain effective.
Explanation
Correct Answer
C:Relevant validation before approval: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
Incorrect Answers
A:This option addresses a different CAPM project management topic (User stories and testable acceptance) rather than the documented Extreme Programming TDD and pairing decision.
B:Scaling introduces explicit alignment and dependency management; large planning events should not erase the need to inspect and adapt when evidence changes. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:Product inspection and team process reflection address different questions; both feedback loops help adaptive planning remain effective. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 593
The project team has not approved a broad project-plan change. Available evidence indicates: A high-defect product team adds end-of-quarter regression testing yet refuses to consider frequent automated feedback or small safe code changes. 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.
- Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies.
- Review team availability, dependency queues, specialist handoffs, release approval lead time and stakeholder participation between iterations.
- Review iteration length, backlog slicing, integration evidence, usable functionality and actual inspection feedback after each cycle.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Incorrect Answers
B:Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
C:Review team availability, dependency queues, specialist handoffs, release approval lead time and stakeholder participation between iterations. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:Review iteration length, backlog slicing, integration evidence, usable functionality and actual inspection feedback after each cycle. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 594
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A high-defect product team adds end-of-quarter regression testing yet refuses to consider frequent automated feedback or small safe code changes. 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.
- Small changes remain testable and integrated with meaningful feedback and reduced escaped defects.
- Teams can synchronize releases, identify constraints early and adjust plans without hidden cross-team dependency failures.
- Mandatory certifications remain traceable while customer-facing details can evolve through feedback without violating delivery dependencies.
- Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Incorrect Answers
B:Teams can synchronize releases, identify constraints early and adjust plans without hidden cross-team dependency failures. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
C:Mandatory certifications remain traceable while customer-facing details can evolve through feedback without violating delivery dependencies. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 595
An implementation sign-off request identifies the following problem: A high-defect product team adds end-of-quarter regression testing yet refuses to consider frequent automated feedback or small safe code changes. Which paired project management action and verification should close the review? Select ONE best answer.
- 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.
- 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: Preserve Product Owner accountability for product value and backlog ordering, Scrum Master support for Scrum effectiveness and Developers' ownership of the sprint execution plan. Verify: Check backlog ownership, sprint planning decisions, impediment handling and who actually updates the 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.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Incorrect Answers
B:This option addresses a different CAPM project management topic (Lead time cycle time and throughput) rather than the documented Extreme Programming TDD and pairing decision.
C:This option addresses a different CAPM project management topic (Scrum accountabilities and team ownership) rather than the documented Extreme Programming TDD and pairing decision.
D:This option addresses a different CAPM project management topic (Kanban work-in-progress limits) rather than the documented Extreme Programming TDD and pairing decision.
Question 596
A CAPM project team analyst is reviewing this delivery scenario: Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases. An unsafe shortcut would be: Call the project Extreme Programming because engineers sit together while skipping any automated verification. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles.
- Call the project Extreme Programming because engineers sit together while skipping any automated verification.
- Plan an achievable sprint around a coherent Sprint Goal, available capacity and selected product backlog items with an actionable delivery plan.
- Coordinate cross-team objectives, dependencies, capacity and integration cadence through appropriate scaled planning while preserving feedback and autonomy.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Incorrect Answers
B:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
C:This option addresses a different CAPM project management topic (Sprint planning capacity and goal) rather than the documented Extreme Programming TDD and pairing decision.
D:Coordinate cross-team objectives, dependencies, capacity and integration cadence through appropriate scaled planning while preserving feedback and autonomy. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 597
A project delivery review finds: Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases. The team proposes: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Product inspection and team process reflection address different questions; both feedback loops help adaptive planning remain effective.
- Adaptive approaches need timely decisions, collaboration and feedback; organizational constraints can undermine iteration reliability unless explicitly addressed.
- XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
- Scaling introduces explicit alignment and dependency management; large planning events should not erase the need to inspect and adapt when evidence changes.
Explanation
Correct Answer
C:Relevant validation before approval: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
Incorrect Answers
A:Product inspection and team process reflection address different questions; both feedback loops help adaptive planning remain effective. Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases.
B:Adaptive approaches need timely decisions, collaboration and feedback; organizational constraints can undermine iteration reliability unless explicitly addressed. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:Scaling introduces explicit alignment and dependency management; large planning events should not erase the need to inspect and adapt when evidence changes. Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases.
Question 598
The project team has not approved a broad project-plan change. Available evidence indicates: Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Review whether the meeting updates the work plan, exposes blocked flow and assigns follow-up without lengthy unrelated problem resolution.
- Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams.
- Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies.
- Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
Explanation
Correct Answer
D:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels. Confirm afterward that: Small changes remain testable and integrated with meaningful feedback and reduced escaped defects.
Incorrect Answers
A:Review whether the meeting updates the work plan, exposes blocked flow and assigns follow-up without lengthy unrelated problem resolution. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
B:Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
C:Identify target users, key problem, smallest meaningful end-to-end behavior, test metric and safe release dependencies. Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases.
Question 599
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases. 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 adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate.
- Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items.
- Each short iteration can complete a meaningful tested increment without hidden resource contention or skipped mandatory controls.
- Small changes remain testable and integrated with meaningful feedback and reduced escaped defects.
Explanation
Correct Answer
D:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels. The approved implementation step was: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles.
Incorrect Answers
A:The team adapts its plan and resolves or escalates blockers while the meeting stays focused and proportionate. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
B:Forecasts show defensible ranges and the team is not incentivized to inflate estimates or conceal incomplete items. Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases.
C:Each short iteration can complete a meaningful tested increment without hidden resource contention or skipped mandatory controls. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
Question 600
For an original CAPM project delivery study scenario, consider: Two developers adopt pair programming but never rotate perspectives or maintain tests, assuming two people at one keyboard automatically guarantee defect-free releases. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Check: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
- Change: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles.
- Check: Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams.
- Change: Apply consistent Definition of Done quality standards to the increment and separately verify item-level acceptance criteria before treating work as complete.
- Result: Small changes remain testable and integrated with meaningful feedback and reduced escaped defects.
- Result: Stakeholder feedback affects product direction while internal process changes have owners and measurable follow-through.
Explanation
Correct Answer
A:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels. Acceptance: Small changes remain testable and integrated with meaningful feedback and reduced escaped defects.
B:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels. Evidence: Review automated test behavior before and after changes, code integration frequency, defect escape and pairing outcomes in a sample feature.
E:XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels. Required intervention: Use appropriate XP engineering practices such as test-driven development, pair collaboration and continuous integration to shorten quality feedback cycles.
Incorrect Answers
C:Check: Map fixed regulatory handoffs, emerging user needs, change authority, integration milestones and schedule coupling across workstreams. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.
D:This option addresses a different CAPM project management topic (Definition of Done and acceptance criteria) rather than the documented Extreme Programming TDD and pairing decision.
F:Result: Stakeholder feedback affects product direction while internal process changes have owners and measurable follow-through. XP emphasizes technical practices that support safe frequent change; pairing and tests need purposeful execution rather than ceremonial labels.