PMI Updated PMI-ACP Exam Questions and Answers by josh

According to the PMI Agile Practice Guide (Section 7.2.2), one of the key responsibilities of the agile practitioner is to actively engage stakeholders throughout the development cycle—not just during review meetings. Agile frameworks promote continuous collaboration and frequent feedback. Merely attending sprint reviews is passive participation and may lead to missed alignment on expectations.

Mike Griffiths also emphasizes in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) that stakeholder satisfaction requires more than periodic visibility—it requires ongoing interaction and inclusion in decision-making and backlog refinement sessions. This deepens shared understanding and reduces the risk of late-stage surprises.

Hence, answer B is correct because proactive stakeholder engagement with the product owner fosters mutual understanding, timely feedback, and course correction—ensuring the product aligns with expectations.

The correct answer is A — Practicing the servant leadership style of working with an agile team.

Servant leadership is foundational to Agile. The agile project leader serves the team by removing impediments, supporting their needs, and promoting transparency. Using information radiators and being involved in team progress reflects servant leadership in action.

PMI Agile Practice Guide:

“Agile leaders act as servant leaders. They support the team, remove obstacles, and foster a transparent, collaborative environment.”

(PMI Agile Practice Guide, Section 6.2 – Coaching and Servant Leadership)

Mike Griffiths:

“Servant leadership is about enabling the team to succeed. Agile leaders serve by ensuring the team has what it needs, while maintaining visibility through information radiators.”

(PMI-ACP Exam Prep, Chapter 1 – Agile Principles and Mindset)

Incorrect options:

B and C are valid Agile behaviors but not the most specific or complete match.

D references feedback loops but not leadership style.

Answer: A

—

A spike is a time-boxed research activity used in Agile to explore uncertainties or unknowns, such as dependencies in this case. If the product owner is unsure about the risks related to migrating to a new version of a database, they can request a spike from the team. This will allow the team to investigate the dependencies, assess potential risks, and gather the necessary information to move forward with the user story. This helps reduce uncertainty and makes it easier to make informed decisions about the next steps.

Agile teams embrace change and collaborate with customers to deliver value. The PMI Agile Practice Guide (Section 2.1: Agile Mindset) supports responding to change—even late in the development cycle—if it results in business value. The team should accept the new goal, replan with the product owner, and adjust scope or priority if needed, rather than resist or escalate.

Option A is correct: it reflects the agile value of responding to change and delivering early value.

Option B is too rigid and contrary to agile principles.

Option C implies a punitive model that does not align with collaborative agile contracts.

Option D introduces unnecessary cost and overhead without first trying to replan collaboratively.