Pass the PMI Agile PMI-ACP Questions and answers with ExamsMirror

Agile teams evaluate new tools or technologies throughspikes—time-boxed research or experimentation tasks. According to thePMI Agile Practice Guide (Section 5.2: Spikes and Exploration)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), the appropriate way to introduce new technology is toengage the teamin the decision and create abacklog itemfor a spike to evaluate its viability.

Option Cis correct: it follows agile collaboration and backlog grooming practices.

Option Askips team consensus and formal prioritization.

Option Bcontradicts self-organizing team principles.

Option Dmay delay necessary action and is better suited for process discussions, not technical trials.

The Scrum Master should act as a facilitator and protect the team from unnecessary distractions that do not add value. By attending the meetings in place of the team members, the Scrum Master can assess the meetings' value and determine if they are essential to the team's progress. If the meetings are unnecessary or inefficient, the Scrum Master can work with stakeholders to improve or remove them, ensuring that the team’s time is used productively and that they can focus on delivering value.

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

Mike Griffiths in hisPMI-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 Cis correct: logging technical debt as animpedimentbrings visibility and ensures discussion.

Option Amay indicate a problem, but it’s indirect.

Option Bdistorts estimation metrics and is not advised.

Option Dcould help but does not communicate impact explicitly.

Velocity is a measure of the amount of work a team can handle during a sprint, typically measured in story points. While it can fluctuate slightly from sprint to sprint, the goal is to have velocity stabilize over time, as this helps in forecasting future sprints and planning. An increase in velocity from 27 to 35 could indicate an improvement in the team's capacity to deliver, which should be celebrated if it aligns with the team's capabilities. However, a stable velocity over time is what typically matters for predictability and planning.

Upon joining a team, a Scrum Master should focus onfacilitating team collaboration, removing impediments, and creating a psychologically safe space. ThePMI Agile Practice Guide (Section 3.3: Scrum Master Role)andMike Griffiths (Chapter 3: Team Performance)stress that early efforts should center onservant leadership, helping the team identify and solve their own challenges.

Option Cis correct: supporting the team through facilitation reflects the core role of a Scrum Master.

Option Ais prescriptive and not aligned with cross-functional team philosophy.

Option Bmay be necessary later, but first, trust and team dynamics must be established.

Option Dfalls under the Product Owner’s responsibility, not the Scrum Master’s.

The correct answer is D – Turn the requests into user stories and prioritize them. In agile, all feature requests must be expressed in the form of user stories and added to the product backlog. Once added, they are prioritized collaboratively with the product owner and stakeholders, usually based on value, risk, and effort.

From PMI Agile Practice Guide:

“Product backlog refinement includes breaking down large items into user stories, reprioritizing items, and ensuring they are properly understood by the team. This activity is critical in ensuring the right items are worked on at the right time.”

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

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile teams transform customer needs into user stories during backlog grooming. These are then prioritized by the product owner to ensure maximum value is delivered early.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Option A ignores customer needs. Option B (ordering by complexity) does not consider value. Option C skips the important step of converting feature requests into properly structured backlog items.

Answer: D

=========

The correct answer is A – Add a task to the product backlog to allow the team time to investigate and experiment prior to estimating.

When the team lacks experience or clarity around a new feature or technical solution, they should perform a time-boxed research activity, known as a spike. Spikes allow the team to explore unknowns, validate assumptions, and gather information needed to provide accurate estimates.

From the PMI Agile Practice Guide:

“When the team is unable to estimate due to uncertainty, a spike can be added to the backlog. This allows time for research, experimentation, or prototyping to enable informed estimation.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning)

Mike Griffiths also writes:

“Spikes are used to investigate technical or functional elements. A spike helps reduce uncertainty and informs future planning and estimation.”

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

Why other options are less effective:

B (Wideband Delphi), C (Planning Poker), and D (Three-point estimation) are techniques for estimation, not suitable when the team lacks enough information to estimate in the first place.

Answer: A

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

In an Agile environment, fostering a culture of collaboration and effective communication is key to success, especially when working with a diverse team. By creating a shared vision, the project manager aligns the team towards common goals, which helps reduce misunderstandings. Using techniques to increase empathy and positive interaction ensures that team members understand and respect each other's different perspectives. This approach promotes a collaborative environment where diverse ideas can be valued and conflicts can be addressed constructively.

The correct answer is C – Invest in technology-collaboration tools to enable effective communication and ensure a common understanding of the scope, issues, and solutions.

Agile encourages high-bandwidth communication, preferably face-to-face. However, when working with distributed teams, modern collaboration tools serve as essential enablers of shared understanding and timely feedback, reducing the risk of miscommunication and rework.

From the PMI Agile Practice Guide:

“While agile prefers face-to-face communication, geographically dispersed teams must rely on tools to mimic these interactions as closely as possible. These include video conferencing, online whiteboards, and real-time collaboration platforms to create a shared understanding.”

(PMI Agile Practice Guide, Section 2.3 – Communication and Collaboration)

Mike Griffiths supports this as well:

“Remote teams need strong communication enablers. Collaboration tools help mitigate the challenges of distributed work by enabling transparency, synchronous discussions, and shared visibility of the work.”

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

Why the other options are less appropriate:

A assumes majority rule over inclusive engagement.

B is often impractical and does not reflect Agile’s adaptability.

D is vague and lacks actionable commitment.

Answer: C

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

Kanban is a visual management tool that helps teams improve workflow efficiency. One of its key principles is the use of a pull system, where work is pulled into the process when capacity allows, rather than being pushed into the system. This contrasts with a push system, where work is assigned or forced into the workflow regardless of capacity. This approach helps avoid bottlenecks and ensures work is handled efficiently.