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

When the team determines that the highest-priority item will take longer than expected in the current sprint, it is essential to engage the product owner. The product owner is responsible for maintaining the product backlog and defining the priority of work items. By scheduling a meeting with the product owner, the team can collaboratively reassess the priorities and make adjustments based on the evolving understanding of the work required.

The product owner can help determine if the current high-priority item should be moved to the next sprint or if other adjustments to the backlog are needed. This ensures that the team is always focused on delivering the most valuable work within the given sprint time frame. Engaging with the product owner fosters collaboration and ensures alignment between the team and stakeholders, maintaining flexibility and focus on delivering customer value.

The correct answer is D – Implement a spike to enhance creativity by experimenting with new techniques and process ideas in order to discover more efficient and effective ways of working.

A spike is a time-boxed research or prototyping activity used to explore uncertainty, investigate a technology, or gain deeper knowledge of an implementation. Spikes are especially useful when a team lacks familiarity with certain technologies, as they reduce risk and support better estimation.

From the PMI Agile Practice Guide:

“Spikes are a type of exploration that agile teams use when they are uncertain about a technology or technique. They are time-boxed research efforts aimed at reducing risk and improving future delivery.”

(PMI Agile Practice Guide, Section 5.3 – Spikes)

Mike Griffiths further explains:

“Spikes allow the team to gain knowledge needed to understand a technical or design problem. They are particularly useful when the team lacks domain or technical experience and are often used to improve estimation accuracy.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why other options fall short:

A and B manipulate iteration length without addressing the core problem (lack of technical knowledge).

C increases overhead without solving the learning gap or preventing the root cause (rework).

Answer: D

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

answers and comprehensive explanations drawn from authoritative sources including the PMI Agile Practice Guide, PMBOK® Guide, Mike Griffiths’ PMI-ACP Exam Prep Book, and Andy Crowe’s PMI-ACP Exam materials.

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

The best answer is D because the project lead should foster psychological safety. In agile teams, people need to feel safe to share opinions, challenge ideas, raise concerns, and provide feedback without fear of blame, embarrassment, or punishment. This is especially important in international or cross-cultural teams where communication styles may differ.

Option A may help with meeting structure, but emphasizing rules does not necessarily make people feel safe. Option B is passive and may allow silence to continue. Option C may help in some cases, but separate meetings do not solve the root issue in team discussions. Option D directly addresses the problem by improving the team environment.

PMI-ACP explicitly includes fostering psychological safety, encouraging dialogue, soliciting constructive feedback, and promoting a collaborative team environment.

=========

To support quick feature delivery while maintaining quality, the best approach is to automate integration, testing, and deployment activities. This aligns with the principles of Continuous Integration and Continuous Deployment (CI/CD), which streamline processes and reduce the manual effort required to test and deploy software. This approach can help the team to quickly release features with confidence that they meet quality standards, reducing manual errors and speeding up the delivery cycle.

The correct answer is C – Facilitate a conversation about the user story between the development team and the product owner. In Agile, collaboration, self-organization, and face-to-face conversation are foundational principles for resolving disagreements and achieving a shared understanding.

According to the PMI Agile Practice Guide:

“The agile practitioner facilitates healthy communication and constructive dialogue between the product owner and the development team to align understanding and priorities. Agile coaches and Scrum Masters serve the team by removing obstacles to collaboration, not by acting as decision-makers.”

(PMI Agile Practice Guide, Section 6.3 – Facilitating Agile Practices)

Further, the guide emphasizes:

“Effective teams discuss issues collaboratively. When disagreements arise, the agile leader’s role is to facilitate communication and resolution through shared understanding, not to dictate decisions.”

(PMI Agile Practice Guide, Section 4.1 – Agile Mindset and Behaviors)

Mike Griffiths’ PMI-ACP Exam Prep Book also states:

“Agile encourages close collaboration between business and technical teams. When conflicts arise regarding a user story, the agile practitioner’s role is to facilitate meaningful discussions to ensure mutual understanding and team-driven resolution.”

(Mike Griffiths, Chapter 4 – Team Performance)

Why the other options are incorrect:

A undermines team self-organization and implies a command-and-control model.

B is confrontational and goes against agile values of respect and collaboration.

D contradicts the facilitative role of the agile practitioner, who should not act as an authoritative decision-maker.

Thus, the most agile-consistent approach is to enable conversation and clarity between roles.

Answer: C

The retrospective is the agile ceremony designed for teams to inspect and adapt their process based on actual performance. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives), discussing velocity issues and delivery concerns during retrospectives allows the team to collaboratively identify improvement actions.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) also notes that retrospectives are the best setting to discuss variations in velocity and refine estimation or planning practices based on empirical evidence.

Option C is correct: the retrospective is where the team adapts based on reality.

Option A may come later but doesn’t address the root issue.

Option B goes against agile principles of stable teams and empirical planning.

Option D is reactive and may mask underlying process issues.

Pull communication is most effective for a distributed team working across multiple locations, especially when task-oriented communications and discussion boards are involved. With pull communication, team members can access information when needed, such as through shared documents, wikis, or discussion boards. This ensures that communication is effective and available asynchronously, allowing the team to collaborate and stay informed without needing to be online at the same time. This method is particularly useful when managing a geographically dispersed team.

A quick mock-up (or prototype) is a highly effective way to visually represent the product ' s features and functionality to stakeholders. This allows stakeholders to get a tangible sense of what the product will look like and how it will work. By iterating on this mock-up and adjusting it based on feedback, the team can build consensus and gain stakeholder approval more effectively. This approach encourages active collaboration and ensures that the product aligns with stakeholder expectations early in the development process.

Kanban is continuous and can lead to burnout or low morale due to lack of visible milestones. The PMI Agile Practice Guide (Section 5.7: Flow-based Agile) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance) suggest that recognizing and celebrating milestones or delivery points is essential to maintain motivation, especially in long-running Kanban teams.

Option A is correct: celebrating completed work gives the team a sense of closure and achievement, improving engagement.

Option B might help temporarily but doesn’t address the root motivational issue.

Option C adds pressure and is counterproductive.

Option D may improve flow but doesn ' t directly address the lack of visible progress recognition.