PMI Updated PMI-ACP Exam Questions and Answers by kyle

In Agile, estimates are initially based on previous experiences or expert opinions, but as the team progresses through sprints, they gain more insight into the project’s actual complexity and the team ' s capacity. Agile estimates evolve over time based on the team ' s velocity, which reflects how much work the team can realistically handle. This is why the actual scope and timelines can differ from initial estimates. The agile lead should emphasize that the initial estimates were helpful for understanding feasibility, but the true estimates are refined continuously as the team gains more experience and understanding of the work, and as complexities or dependencies become clearer during each sprint.

The correct answer is C – The team should discuss their definition of done (DoD) and make changes to ensure there is common understanding of the acceptance criteria.

A shared understanding of what “done” means ensures consistent quality across team members. When this understanding is missing, defects and inconsistencies arise. The Definition of Done (DoD) should be reviewed and updated collaboratively to set a clear standard for completeness and quality.

From the PMI Agile Practice Guide:

“The Definition of Done provides a shared understanding of when work is complete. This includes quality criteria, testing, and documentation. It should be revisited regularly to maintain alignment.”

(PMI Agile Practice Guide, Section 5.2 – Definition of Done)

Mike Griffiths emphasizes:

“Quality issues often result from unclear or inconsistent DoD. Revisiting and refining it ensures consistent expectations across the team.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why the other options are incorrect:

A (TDD) may help, but won’t solve the fundamental alignment issue.

B accepts a problem without resolving it.

D imposes a process without team collaboration, which is not agile.

Answer: C

══════════════════════════════════════════════════

This situation introduces technical uncertainty. In agile, such scenarios are best addressed by spikes or incremental implementation and early feedback. The PMI Agile Practice Guide (Section 5.2 Spikes and Experimentation) suggests that uncertain work should be prototyped, tested early, and shown during sprint reviews for feedback and learning.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution) recommends testing high-risk integrations early and iteratively, rather than over-planning.

Option D is correct: developing, testing, and demonstrating early minimizes risk and aligns with agile principles.

Option A leans toward waterfall-style planning and over-documentation.

Option B incorrectly assumes non-functional requirements are less valuable—they’re critical in many systems.

Option C may delay necessary architectural work and increase risk.

The correct answer is D — Facilitate a team retrospective.

A drop in team morale and performance signals the need for a structured conversation where the team can reflect, diagnose root causes, and propose changes. Retrospectives are the Agile mechanism for identifying and addressing performance issues in a collaborative, non-blaming environment.

PMI Agile Practice Guide:

“Retrospectives allow teams to reflect on their performance, discuss what ' s working or not, and commit to improvement actions. This is the key mechanism for continuous team development.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths affirms:

“Team disengagement often stems from unresolved issues or lack of empowerment. Retrospectives are critical for rebuilding engagement, trust, and improving team dynamics.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A skips team-level resolution and risks undermining trust.

B manipulates metrics without solving the root problem.

C is useful for daily progress updates but not for deep reflection.

Answer: D

—

—