Free PMI PMI-ACP Practice Exam with Questions & Answers | Set: 6

The correct answer is D – Assume the team member's tasks to meet iteration goals and notify the Product Owner. Agile teams are self-organizing and accountable. High-performing teams take ownership of shared goals and redistribute work as needed to maintain commitment.

From the PMI Agile Practice Guide:

“High-performing agile teams collaborate to deliver sprint goals, adapting to changes such as unavailability of team members. They adjust workload and communicate impacts transparently.”

(PMI Agile Practice Guide, Section 4.3 – Team Performance and Self-Organization)

Mike Griffiths explains:

“When team composition changes, the team must redistribute work to ensure delivery. Ownership, trust, and flexibility are core traits of high-performing agile teams.”

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

Incorrect options:

A signals dysfunction and abdicates team responsibility.

B implies external management of team staffing.

C violates the principle of self-organization.

Agile teams operate on the principle ofinspect and adapt. According to thePMI Agile Practice Guide (Section 5.6 Retrospectives)andPMBOK® Guide 6th Edition (Section 3.7), retrospectives are designed forexperimentation and safe failure. Teams should be encouraged to try new process improvements and assess their impact. If the result is not positive, it’s an opportunity for collective learning—not for blame.

Mike Griffiths states in hisPMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement)that leaders shouldfoster a culture of experimentation, where teams are praised for trying new approaches, even if they fail. This maintains psychological safety and continuous learning.

Thus,Option Ais correct: Commending the attempt and facilitating a team discussion to explore alternatives is consistent with agile values and promotes team maturity.

The Definition of Done (DoD) is a shared understanding of what it means for work to be considered complete. It is typically defined by the project sponsor and project team in collaboration. The DoD outlines the criteria that must be met for user stories, features, or tasks to be considered done, ensuring alignment between stakeholders and the development team. While the product owner, Scrum master, and stakeholders may influence the criteria, the final agreement on what constitutes "done" is determined by the project team and sponsor.

The correct answer is D — A list of questions for the team and customer representative.

In Agile, creating a shared product vision is a collaborative effort that begins with open dialogue. The team should prepare insightful, value-driven questions to understand the customer’s needs, pain points, desired outcomes, and business drivers. This supports co-creation of the vision rather than relying on rigid documentation.

PMI Agile Practice Guide:

“A shared product vision aligns the team and stakeholders. Early collaboration and asking the right questions help establish understanding and purpose.”

(PMI Agile Practice Guide, Section 2.2 – Agile Mindset)

Mike Griffiths:

“Visioning meetings are facilitated conversations where teams and stakeholders explore product goals and user needs. Questions—not documents—drive clarity.”

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

Incorrect options:

A implies a rigid, document-driven mindset—contrary to Agile.

B assumes the backlog exists before visioning.

C is too early for acceptance criteria before vision alignment.

Answer: D

—

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

The project manager should ensure that risks are clearly visible to all team members so that everyone is aware of potential issues and can take action as necessary. Displaying the RAID log visually makes it easy for the team to see the status of risks, assumptions, issues, and dependencies in real-time. This encourages the team to follow up on risks and keep them top of mind, facilitating more proactive management of potential threats to the sprint's success. This approach also helps in maintaining transparency and continuous monitoring of risks throughout the sprint.

When an agile team's velocity is slowing down, it is essential to regularly evaluate and adjust how the team is performing. By using feedback loops in every sprint, the team lead can continuously assess the team's progress, identify bottlenecks, and address issues early on. These feedback loops, typically discussed in sprint retrospectives, provide an opportunity for the team to identify the root causes of challenges, such as miscommunications, and make improvements to ensure better performance in future iterations. This approach promotes ongoing reflection and adaptation, which are core principles of Agile.

The correct answer is D – Facilitate a just-in-time exploration of the functionality by the customer and the team.

Agile promotes emergent planning and just-in-time elaboration. When a customer cannot clearly define how a feature should function, collaborative exploration at the point of need (just-in-time) ensures shared understanding, timely feedback, and minimized waste.

From the PMI Agile Practice Guide:

“User stories are deliberately kept light to encourage conversation. These conversations often occur just before the story is scheduled for development—known as just-in-time elaboration.”

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

Andy Crowe also explains:

“Agile teams defer detail until the last responsible moment. This supports flexibility and better understanding through collaboration. Facilitating exploration sessions when needed helps clarify expectations and reduce uncertainty.”

(Andy Crowe, PMI-ACP Exam Prep, Chapter 5 – Value Delivery)

Why other options are less suitable:

A may be helpful for technical uncertainty, but the issue here is lack of functional clarity from the customer.

B (iteration 0) is more of a preparatory stage; it is not typically used mid-project.

C suggests decomposition but without resolving the lack of understanding; it assumes the problem is granularity, not clarity.

Hence, the correct agile action is to engage collaboratively at the point of need: D

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

To improve collaboration, it's essential that the team members understand the importance of the project vision statement and feel empowered to contribute. Setting clear expectations ensures that all participants know the purpose of the meeting and their role in contributing. By encouraging everyone to share their ideas and perspectives, the team can reach a consensus or at least acknowledge differing views in a constructive way. This fosters a collaborative environment where team members feel their input is valued.

The correct answer is C – Work with the stakeholder directly rather than go through different layers of people. Agile emphasizes direct communication and collaboration with stakeholders to reduce miscommunication and ensure clarity. When requirements differ depending on who is asked, the agile practitioner must go directly to the source for clarification and alignment.

From PMI Agile Practice Guide:

“Face-to-face conversation is the most effective method of conveying information to and within a development team. Agile encourages working directly with stakeholders and product owners to minimize miscommunication.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement; Agile Manifesto Principle #6)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“To reduce noise and confusion, agile practitioners are encouraged to engage stakeholders directly rather than relying on intermediaries or second-hand interpretations.”

(Mike Griffiths, Chapter 1 – Agile Principles and Mindset)

Option A contradicts agile’s value of responding to change. Option B is an indirect solution that does not eliminate confusion. Option D is internal to the team and doesn’t resolve inconsistencies from stakeholder communication.

Answer: C

=========