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

To prevent the prioritization meeting from turning into a brainstorming session, the product owner should ensure that user stories are well-defined before they are added to the backlog. By reviewing the items with the product owner’s teammates (or stakeholders) beforehand, the product owner can clarify the details of the stories and ensure they are properly defined. This allows the team to focus on prioritization during the meeting, rather than spending time clarifying vague requests. This proactive approach improves the efficiency and effectiveness of the prioritization process.

Knowledge sharing and organizational learning are core elements of scaling agile. According to the PMI Agile Practice Guide (Section 8.4 Organizational Change Management) and the PMBOK® Guide (6th Edition, Section 10.2 Manage Communications), the project manager should actively disseminate lessons learned, best practices, and project outcomes to promote agile adoption across the organization.

Mike Griffiths reinforces in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) that continuous feedback loops and transparent communication are essential to agile transformation success.

Option D is correct because regular meetings specifically focused on sharing outcomes and learning from the pilot project help embed agile values and improve future implementations.

The correct answer is D – Advise the team of the risks and invite them to change.

Agile teams are encouraged to self-organize, but this should not result in the formation of silos, which can hinder collaboration and shared knowledge. As a servant leader, the Agile practitioner or Scrum Master should coach the team by facilitating discussions about the risks of silos (e.g., dependency bottlenecks, reduced flexibility) and encourage cross-functional collaboration.

From the PMI Agile Practice Guide:

“Agile leaders help teams reflect and improve. When silos form, the coach facilitates awareness of the impacts and invites the team to adopt knowledge sharing practices.”

(PMI Agile Practice Guide, Section 6.2 – Coaching the Agile Team)

Mike Griffiths states:

“Silos reduce adaptability and team learning. A coach should raise awareness and help the team find new behaviors that support agility and collaboration.”

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

Why other options fall short:

A escalates prematurely and undermines team self-management.

B enforces rules instead of fostering understanding.

C imposes a solution instead of empowering the team to solve its own issues.

Answer: D

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

In agile, work is considered “done” only when it meets the agreed-upon Definition of Done (DoD), which includes all aspects like coding, review, testing, and documentation. If there ' s disagreement about completion, the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance) recommends revisiting and aligning the DoD between the team and product owner.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) explains that without a clear and shared Definition of Done, misunderstandings about completion status can occur, especially with quality-related tasks like testing.

Option A is correct because aligning on the DoD resolves current and future misunderstandings.

Option B introduces unnecessary escalation.

Option C postpones resolution and does not solve the core issue.

Option D incorrectly assumes testing isn’t part of the story’s completion criteria.

The correct answer is A – Inform the stakeholder that all updates are provided in the sprint review sessions and encourage them to attend.

The Sprint Review is designed to provide transparency to stakeholders, demonstrate completed work, and gather feedback. Stakeholders should be encouraged to attend these events to stay updated and engaged.

From the PMI Agile Practice Guide:

“Sprint reviews are intended to engage stakeholders in reviewing completed work and discussing priorities. This event ensures transparency and encourages stakeholder collaboration.”

(PMI Agile Practice Guide, Section 5.5 – Stakeholder Engagement)

Mike Griffiths adds:

“Agile teams encourage stakeholder participation in regularly scheduled review meetings to maintain alignment and foster transparency.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options:

B adds non-Agile overhead and undermines Agile transparency mechanisms.

C and D are dismissive and uncollaborative, potentially damaging relationships.

Answer: A

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

The correct answer is D — Iteration Burndown Chart.

An iteration burndown chart provides daily updates about the team’s progress during an iteration (or sprint). It tracks the remaining work in the sprint backlog and helps both the team and stakeholders assess if the sprint goal is likely to be met. This visualization helps communicate real-time progress to key stakeholders and supports adaptive planning.

PMI Agile Practice Guide states:

“Burndown charts display work remaining in a timebox and are updated daily. They are effective for communicating iteration progress to the team and stakeholders.”

(PMI Agile Practice Guide, Section 5.6, Information Radiators)

PMBOK® Guide (6th Edition) and Mike Griffiths both emphasize using task boards and burndown charts as “information radiators” for transparency.

Mike Griffiths’ PMI-ACP Exam Prep Book elaborates:

“Iteration burndown charts are the most widely used artifact to track sprint progress. They offer insight into how much work remains and signal whether the team is on track to meet its sprint goal.”

Options A and B are long-term planning tools. Option C (velocity) is a forecasting metric and not updated daily.

Answer: D

=================================

The correct answer is B – Ensure there is a balanced mix of people who are experts and members with broad experience based on the work to be performed and determine training needs.

Scrum encourages cross-functional, self-organizing teams with complementary skills. Building a balanced team that reflects both depth and breadth of experience ensures optimal delivery while enabling team learning.

From PMI Agile Practice Guide:

“Agile teams are cross-functional. The team may need T-shaped skills—members with deep expertise in one area and a willingness to broaden knowledge in other areas. Creating balanced teams with knowledge diversity leads to better collaboration and learning.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths adds:

“Team selection should prioritize diversity of skill sets and the ability to collaborate, not just performance history. The goal is a team that can deliver value collectively, not as individuals.”

(Mike Griffiths, Chapter 4 – Team Performance)

Why the other options are not suitable:

A may reduce team diversity and discourage healthy conflict resolution.

C may not be feasible in distributed environments and is not a strict requirement.

D focuses on individual velocity contributions, which contradicts Agile’s team-based delivery focus.

Answer: B

The correct answer is B — Create a spike story to determine what needs to be done to use the new interface.

A spike is a special user story designed to address technical uncertainty or risk. It allows the team to explore, research, or prototype solutions within a time-box. Spikes are particularly useful for investigating unknowns such as integration with vendor systems.

PMI Agile Practice Guide:

“Spikes are used for research and exploration. They help teams gain knowledge about technology, functionality, or business domain that is necessary before estimating or implementing a feature.”

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

Mike Griffiths notes:

“Spikes reduce uncertainty and are valuable tools for backlog refinement. They are especially helpful when the team is unsure how to implement a requirement or integrate external components.”

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

Other options:

A may delay addressing the issue until the next monthly meeting.

C defers the issue rather than exploring it.

D assumes outsourcing is the only solution and may remove team ownership.

Answer: B

—

A cumulative flow diagram (CFD) is a powerful tool to visualize the flow of work across different stages of the process and identify where bottlenecks are occurring. By using a CFD, the team can see the buildup of work in specific columns, such as the " Ready to be tested " queue, and determine where delays are happening. Identifying bottlenecks is the first step in improving flow and addressing the slower delivery. Once the bottleneck is identified, the team can make adjustments to improve speed, such as optimizing the testing process or redistributing workload.

The correct answer is C – Meet with the team to discuss the issue and identify specific actions to reduce or eliminate the issue. Agile coaches facilitate team self-management, guide reflection, and encourage the team to solve performance issues collaboratively. Open discussion fosters ownership and accountability.

From the PMI Agile Practice Guide:

“Agile coaches guide teams through self-reflection and help them identify root causes of issues. Coaches support team-driven resolutions to behavioral and performance problems.”

(PMI Agile Practice Guide, Section 4.3 – Agile Coaching and Team Performance)

Mike Griffiths adds:

“Effective agile leadership involves enabling the team to identify and resolve their own challenges. Top-down directives may harm morale and self-organization.”

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

Incorrect options:

A and B bring in external control, undermining team autonomy.

D is punitive and contradicts agile principles of empowerment and trust.

Answer: C