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

The correct answer is C – Show the stakeholder the progress radiators for the project.

Progress radiators, such as task boards, burndown charts, and Kanban boards, visually communicate the status of work in progress, completed items, and remaining scope. They are effective tools for quickly bringing stakeholders up to speed without interrupting the team or requiring extensive reporting.

From the PMI Agile Practice Guide:

“Progress is tracked and made visible using information radiators such as burndown charts, task boards, and velocity charts. These tools allow stakeholders to monitor project health in real time.”

(PMI Agile Practice Guide, Section 3.5 – Information Radiators)

Mike Griffiths emphasizes:

“Transparency and visibility are essential in agile. Information radiators keep stakeholders informed and promote collaboration without relying on status reports.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Agile Monitoring and Control)

Other options explained:

A and D offer limited insights or are inappropriate for immediate understanding.

B is valuable but time-limited; radiators provide continuous insight.

Answer: C

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

The correct answer is A – Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints. In Agile, risk is actively managed and addressed as part of the backlog. When the risk threshold is exceeded, the team should explicitly identify risk-related tasks and bring them into visibility for planning and execution.

From the PMI Agile Practice Guide:

“Agile teams manage risk by incorporating risk mitigation tasks directly into the backlog and addressing them early. Risk exposure is reviewed frequently, and responses are prioritized based on value and urgency.”

(PMI Agile Practice Guide, Section 6.7 – Risk Management)

Also from the PMBOK® Guide (6th Edition):

“Risks should be integrated into project activities. Agile teams identify, analyze, and prioritize risks continuously and handle them as regular backlog items.”

(PMBOK® Guide, Section 11.5 – Risk Response Planning)

Mike Griffiths further supports this by noting:

“Agile teams track risks visually and use backlog prioritization techniques to ensure they’re addressed appropriately.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

B suggests padding estimates, which is an anti-pattern.

C is arbitrary and not recommended.

D delays risk response and contradicts proactive risk management.

Answer: A

Before the workshop, the team members should read and identify relevant user stories from the product backlog that directly contribute to the goal of developing the feature for receiving and resolving customer complaints. This ensures that the stories being worked on are well-understood and aligned with the release goal.

The team should also consider the possible risks associated with each selected user story, such as technical challenges or dependencies. Additionally, they should evaluate the value each story adds to the final user (customer), ensuring that the team focuses on delivering maximum value in the release.

The correct answer is D – Confirm managers and stakeholders are invited to product review meetings. Agile promotes early and continuous feedback from stakeholders through regular reviews (e.g., sprint reviews or demos). Their active engagement ensures alignment with evolving business needs.

From the PMI Agile Practice Guide:

“Demonstrating working product increments at iteration reviews allows stakeholders to inspect progress, provide feedback, and align expectations. Agile teams rely on these sessions to validate whether the product meets business requirements.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement and 5.2 – Reviews)

Mike Griffiths emphasizes:

“Frequent stakeholder reviews reduce risk by capturing early feedback. Stakeholder participation in iteration reviews ensures alignment and continuous validation of business goals.”

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

Incorrect options:

A includes only the team; stakeholders are critical to product validation.

B is insufficient—product owner alignment alone doesn’t ensure business alignment.

C refers to documentation, not collaboration.

Answer: D

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

When teams face conflicts about priorities or direction, they should fall back on agile values and principles . According to the Agile Manifesto and PMI Agile Practice Guide (Section 2.2 Agile Mindset) , decisions should be grounded in values such as collaboration, sustainability, simplicity, and delivering customer value .

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) highlights that teams should be self-organizing , and consensus should emerge from aligning decisions with core agile values—rather than defaulting to top-down directives or contractual obligations.

Option A is correct: referring to the agile framework and team values enables internal resolution in a collaborative and value-driven way.

Option B (contracts) and Option C (priority list) are more rigid and transactional.

Option D bypasses the team’s ability to self-resolve, which is not ideal for a mature agile team.

Technical debt refers to the accumulated cost of suboptimal design or code, often due to shortcuts or lack of refactoring. The PMI Agile Practice Guide (Section 5.5 Quality and Technical Debt) recommends treating technical debt as an impediment that should be logged, tracked, and discussed openly so it can be prioritized and addressed.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution) advises teams to be transparent about technical debt and elevate its visibility so that product owners and stakeholders can make informed decisions.

Option C is correct: logging technical debt as an impediment brings visibility and ensures discussion.

Option A may indicate a problem, but it’s indirect.

Option B distorts estimation metrics and is not advised.

Option D could help but does not communicate impact explicitly.

In agile, especially under conditions of uncertainty or anticipated changes , teams should focus on collaborative product development , including ongoing backlog refinement and continuous product reviews . This approach is endorsed by the PMI Agile Practice Guide (Section 5.1 Product Backlog and Refinement) and Section 7.2 (Engaging Stakeholders) , which emphasize frequent interaction with the product owner and iterative feedback loops to adapt quickly.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the practice of refining the backlog regularly and conducting frequent reviews to stay aligned with stakeholder expectations.

Option B is correct: continuous collaboration with the product owner supports flexible, value-driven delivery.

Option A is only a partial measure.

Option C promotes a waterfall mindset.

Option D ignores the nature of changing requirements.

The correct answer is B — Balance risk reduction and value-adding activities in the next iteration.

Agile recommends actively managing risks as part of iteration planning. While delivering customer value remains a top priority, severe risks should be mitigated as early as possible. The team should consider allocating capacity in the next sprint to reduce risk while still maintaining delivery focus.

PMI Agile Practice Guide states:

“Agile teams incorporate risk mitigation work into iteration planning. Teams should prioritize high-impact risks early and balance risk management with delivering customer value.”

(PMI Agile Practice Guide, Section 7.3 – Agile Risk Management)

Mike Griffiths supports this:

“Agile does not separate risk management into a different process—it is embedded within backlog prioritization. Addressing risk early can prevent downstream impacts, and teams must weigh risk vs. value regularly.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A disrupts current iteration goals and contradicts agile time-boxing.

C ignores the severity of the risk.

D escalates unnecessarily—agile promotes team-level decision-making first.

Answer: B

—

To assess process efficiency , agile teams use value stream mapping to identify waste, delays, and non-value-adding steps . According to the PMI Agile Practice Guide (Section 5.5 Process Analysis and Value Stream Mapping) , value stream analysis helps determine how efficiently a process converts inputs into valuable outputs, making it ideal for supporting customer inquiries on operational performance.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Continuous Improvement) reinforces the value of using value stream mapping for both software development processes and operational workflows to increase transparency and drive improvements.

Option B is correct: reviewing the value stream provides a structured way to evaluate efficiency.

Option A and D are important for team improvement and performance but don’t focus on process activity efficiency .

Option C relates to value prioritization , not operational efficiency.