PMI-ACP Exam Dumps : PMI Agile Certified Practitioner (PMI-ACP)

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 — Create a space on the board to prioritize the threats, along with an update on the actions that are in progress and what still needs to be done.

Agile promotes visual management and transparency. By using a dedicated section on the team board (information radiator), risks can be prioritized, tracked, and made visible to the entire team, enabling ongoing awareness and proactive response.

PMI Agile Practice Guide:

“Information radiators can be used to display risk burndown charts, prioritization, and mitigation plans, allowing teams to manage and address risk openly.”

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

Mike Griffiths:

“Making risks visible and tracking them alongside features fosters collective ownership and ensures proactive handling.”

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

Incorrect options:

A is reactive and lacks persistent visibility.

B may create fatigue and be seen as micromanagement.

C involves the sponsor unnecessarily and doesn’t address day-to-day risk management.

Answer: D

—

Relying solely on the developers' experience with similar systems to define functionality can be limiting and potentially result in misaligned expectations with actual user needs. Effective Agile teams should focus on understanding and addressing the needs of end users, leveraging continuous feedback from customers, and engaging stakeholders directly. This ensures the product is built to meet real user expectations and can evolve as necessary based on user input. Instead of relying on previous experience, the team should be focused on co-creating value with customers through collaboration, feedback, and agile practices like user stories and regular testing.