PMI PMI-ACP - PMI Agile Certified Practitioner (PMI-ACP)

The correct answer is C — Conducted an end-of-phase demonstration.

Agile emphasizes continuous feedback. Regular demonstrations (e.g., sprint reviews or product demos) allow stakeholders, including the customer, to inspect the product increment and provide real-time feedback. Had the team demoed the product, they might have discovered the deficiencies before release.

PMI Agile Practice Guide states:

“A demo or review allows stakeholders to inspect the product increment and provide feedback. Demonstrations reduce the risk of unmet expectations and confirm that the team is building the right product.”

(PMI Agile Practice Guide, Section 5.7 – Reviews and Demos)

Mike Griffiths writes:

“Agile avoids large, end-of-phase validations. Instead, customer feedback is solicited at the end of every iteration through structured demos. This allows for early course correction and alignment with expectations.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Other options:

A is a waterfall artifact and not aligned with agile workflows.

B is analysis-heavy and doesn’t ensure real stakeholder feedback.

D (retrospective) improves process, not product validation.

Answer: C

The correct answer is C – Ask the team to restate the requirements and review them with the client.

Clear communication and shared understanding are core Agile values. The best way to resolve confusion is through direct collaboration. Restating and reviewing requirements with the client fosters alignment and transparency, which reduces rework and frustration.

From the PMI Agile Practice Guide:

“Agile encourages frequent interaction with stakeholders to clarify requirements and reduce misunderstanding. Requirements are best elaborated through collaboration.”

(PMI Agile Practice Guide, Section 5.3 – Backlog Refinement)

Mike Griffiths supports:

“User stories and acceptance criteria should be understood by both team and stakeholders. If confusion arises, revisit and clarify together.”

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

Why not others?

A may boost morale but doesn’t resolve the confusion.

B is speculative and not customer-centric.

D risks building something without validation.

Answer: C

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

The correct answer is D — The team should reevaluate time and cost estimates to reflect the latest understanding of the work effort.

Agile supports progressive elaboration and adaptive planning. When actual effort consistently exceeds estimates, it signals a need to recalibrate estimation practices. The team should revisit their velocity, estimation techniques, and potentially re-estimate upcoming work with improved understanding.

PMI Agile Practice Guide:

“Agile uses adaptive planning, where teams update estimates based on new information. This supports better forecasting and risk management.”

(PMI Agile Practice Guide, Section 5.3 – Estimation and Velocity)

Mike Griffiths:

“Estimation accuracy improves over time. Agile teams regularly inspect estimation practices and adjust based on historical data and team maturity.”

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

—

The correct answer is B – Discuss the issue with the team in the daily stand-up meetings. Agile emphasizes transparency, collaboration, and self-organization. The daily stand-up is an appropriate forum to raise and discuss workload distribution so the team can adjust and support each other.

From the PMI Agile Practice Guide:

“Daily stand-ups are a tool for fostering open communication, uncovering impediments, and adjusting the plan for the day. It enables the team to help each other balance workloads and remove bottlenecks.”

(PMI Agile Practice Guide, Section 5.2 – Daily Stand-Ups)

Mike Griffiths explains:

“Team members should use stand-ups to discuss challenges. If someone is overloaded, the team can identify ways to redistribute work to maintain balance and avoid burnout.”

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

Incorrect options:

A escalates the issue unnecessarily and bypasses team self-management.

C is too narrow and private for a team-based issue.

D adds administrative burden without solving the underlying problem.

Answer: B

────────────────────────────────────

A user story that is too large to complete in one sprint is considered an epic. Agile teams should split it into smaller, valuable, testable stories. The PMI Agile Practice Guide (Section 5.2: User Stories and Decomposition) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend breaking down large stories and renegotiating sprint scope collaboratively with the product owner.

Option C is correct: this aligns with collaborative planning and story decomposition.

Option A is rigid and dismisses collaboration.

Option B promotes unsustainable practices.

Option D violates the principle of fixed-length iterations.

Agile emphasizes transparency and team self-organization. According to the PMI Agile Practice Guide (Section 4.3.3: Self-Organizing Teams) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), a common practice is to make work and issues visible to everyone and allow the team to collaboratively manage their workflow. Using a shared workspace or board helps prevent redundant efforts and improves efficiency.

Option D is correct: shared visibility and self-allocation promote team ownership.

Option A misuses the backlog—issues aren ' t typically prioritized by customers.

Option B is directive and may reduce collaboration.

Option C focuses on analysis, not immediate resolution or coordination.

The correct answer is C – Create an environment of continued learning by providing opportunities for team members to develop their skills as generalized specialists.

Agile encourages the concept of “T-shaped” team members—individuals who have deep expertise in one area and broad skills across multiple areas. Promoting cross-skilling and continued learning reduces risk, increases collaboration, and helps build a resilient, self-sustaining team.

From the PMI Agile Practice Guide:

“Teams should strive to become cross-functional and develop generalized specialists who can collaborate effectively across domains.”

(PMI Agile Practice Guide, Section 5.2 – Building High-Performing Teams)

Mike Griffiths notes:

“Agile promotes team learning. Encouraging members to grow as generalized specialists reduces reliance on single individuals and improves flexibility.”

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

Other options:

A helps but is not sufficient on its own.

B is a solid practice but doesn ' t directly promote skills growth.

D goes against Agile values of team development and empowerment.

Answer: C

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

The correct answer is B – Set expectations regarding the appropriate level of details requested during this stage. In Agile, early project stages are focused on vision, strategy, and high-level planning, not detailed documentation. The agile practitioner must educate stakeholders on progressive elaboration and set realistic expectations about how information is delivered over time.

From the PMI Agile Practice Guide:

“In the early stages of an agile project, requirements and plans are intentionally kept at a high level. Agile practitioners work closely with stakeholders to set appropriate expectations and explain how details will emerge iteratively.”

(PMI Agile Practice Guide, Section 2.4 – Agile Project Initiation and Stakeholder Expectations)

Mike Griffiths reinforces this:

“During project inception, agile practitioners should clarify that detailed specifications evolve through iterative planning. Setting appropriate expectations is critical to building trust and maintaining alignment.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 2 – Agile Principles and Stakeholder Engagement)

Incorrect options:

A contradicts agile principles of just-in-time elaboration.

C is too rigid and may alienate stakeholders.

D abdicates responsibility and doesn’t help manage expectations.

Answer: B

────────────────────────────────────

Velocity is a team-specific, relative measure of work done in a sprint and should not be used to compare teams. The PMI Agile Practice Guide (Section 5.4: Estimation and Velocity) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) highlight that a consistent and predictable velocity is more valuable than simply trying to exceed estimates, which can lead to overcommitment or burnout.

Option C is correct: predictability and consistency are hallmarks of agile maturity.

Option A and B falsely equate velocity across teams.

Option D values overperformance, which may undermine sustainable pace.

The correct answer is A – Hold a meeting with the team and the Product Owner to develop the team charter, working agreement, guiding principles, and product vision. This collaborative approach fosters shared understanding, ownership, and alignment early in the project.

From the PMI Agile Practice Guide:

“The team chartering process includes developing working agreements, clarifying the product vision, defining team norms, and establishing the team ' s mission. Early alignment builds trust and commitment.”

(PMI Agile Practice Guide, Section 4.3 – Team Charter and Working Agreements)

Mike Griffiths elaborates:

“A strong start includes co-creating team values, the product vision, and working agreements. Doing this together builds a strong foundation for delivery.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 2 – Agile Principles and Chapter 4 – Team Formation)

Incorrect options:

B separates the Product Owner from the team early on.

C reverses the roles—vision should be owned by the Product Owner.

D is helpful, but not a prerequisite for team alignment and success.

Answer: A