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

The correct answer is C – Ensure the team captures the technical dependencies as issues within the backlog and prioritize based on value optimization. In Agile, technical considerations are factored into backlog refinement and sprint planning. Dependencies should be visualized and managed as part of adaptive planning while still striving to deliver maximum value.

From the PMI Agile Practice Guide:

“Backlog items with technical dependencies should be identified and addressed collaboratively. Agile teams balance value with feasibility and technical constraints to optimize delivery.”

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

Mike Griffiths explains:

“While business value drives prioritization, technical constraints influence the ordering of stories. Agile planning is adaptive; dependencies and delivery risks are identified early and managed through backlog reordering.”

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

Incorrect options:

A may discard valuable features unnecessarily.

B risks accumulating technical debt and incomplete work.

D shifts responsibility away from the team and PO unnecessarily.

Answer: C

────────────────────────────────────

The best approach to resolving this conflict is collaborating, as it encourages open communication and active participation from all team members. In this case, the graphic designer’s non-participation is causing frustration within the team. The Scrum Master should facilitate a discussion where the designer can express their concerns, and the team can share why their attendance in meetings is important. By collaborating, the Scrum Master can help find a solution that addresses both the designer’s needs and the team's expectations, ensuring better teamwork and alignment moving forward. This approach encourages mutual respect and fosters a cooperative environment.

The correct answer is B — Establish a live video feed between the dispersed teams to enable spontaneous engagement and collaboration on issues.

Agile encourages face-to-face communication as the most effective form of knowledge sharing. For distributed teams, this means using video conferencing, virtual whiteboards, and real-time collaboration tools to replicate co-located team dynamics. This improves clarity, reduces misinterpretation, and accelerates problem-solving.

PMI Agile Practice Guide states:

“For distributed teams, using video conferencing, shared tools, and real-time collaboration platforms helps bridge communication gaps and maintains team cohesion. Face-to-face communication, even via video, remains the most effective method.”

(PMI Agile Practice Guide, Section 4.2 — Stakeholder Engagement)

Mike Griffiths also notes:

“Distributed teams must invest in communication technologies to reduce barriers. Real-time, visual communication enables faster resolution of issues and a shared understanding of tasks.”

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

Incorrect Options:

A involves centralized control and status reporting — not Agile.

C demands co-location, which may not be feasible.

D accepts poor performance instead of addressing root causes.

Answer: B

—

The correct answer is B – Manage communication between all team members and the customer to promote effective and transparent collaboration. Agile values open, direct, and frequent communication, particularly between team members and stakeholders. Transparency, collaboration, and shared understanding reduce misunderstandings and promote customer satisfaction.

From the PMI Agile Practice Guide:

“Agile values individuals and interactions over processes and tools. Frequent, open, and direct communication with stakeholders is essential. Agile teams are encouraged to engage stakeholders frequently to ensure alignment and transparency.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths emphasizes:

“Agile fosters transparency and trust through direct communication. Information should flow freely between all team members and stakeholders to facilitate quick feedback and mutual understanding.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

A and C limit communication and transparency.

D is useful for conflict resolution, but not for broad issue management or stakeholder communication.

Answer: B

────────────────────────────────────

In Agile, collaboration is important, but it should not disrupt the team’s ability to focus on sprint goals. The Scrum Master can address this situation by designating a single team member to represent the team in external meetings, which reduces the impact on the rest of the team’s working time. Additionally, establishing a capacity buffer helps ensure that the team has enough time for their tasks while accounting for the time needed for meetings. This solution maintains both collaboration and productivity without overwhelming the development team.

Planning Pokeris a well-known estimation technique where team members use numbered cards (usually Fibonacci series) to estimatestory point valuesbased on relative size. It’s aconsensus-based estimation method, as described in thePMI Agile Practice Guide (Section 5.2: Estimation Techniques)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Estimating Techniques).

Option Dis correct:Planning Pokeris explicitly designed for estimating stories in terms of points.

Option A (Parametric)is more common in traditional (predictive) planning.

Option B (One-to-one comparison)refers to relative sizing without collaboration.

Option C (Affinity)is another agile technique but typically used forgrouping stories into size buckets, not direct story point consensus estimation.

In Agile, transparency and communication within the team are key. The team member should log the concern into the risk register to formally track the issue and share it with the team at the next standup. This allows the entire team to discuss and assess the situation collaboratively, ensuring that the concern is addressed and managed collectively. This approach aligns with the self-organizing nature of Agile teams, where team members are responsible for working together to find solutions.

When calculating cycle time, it's important to consider delays and bottlenecks in the process. Cycle time refers to the total time taken for a single unit of work to go through the entire process from start to finish. By identifying and understanding delays or bottlenecks, the team can gain insights into where improvements can be made to optimize the flow and reduce overall cycle time. This approach helps in identifying inefficiencies and improving the team's ability to deliver value more effectively.

The correct answer is A – Educate the QA manager that in agile, quality is integrated from the beginning to the end of the project. Agile emphasizes “built-in” quality through test-first approaches, continuous integration, and Definition of Done. Addressing resistance through education helps clarify that quality is a core part of Agile—not an afterthought.

From the PMI Agile Practice Guide:

“Agile does not remove quality controls; rather, it integrates them throughout the development process. Quality is everyone’s responsibility and is embedded through practices such as TDD, automated testing, and continuous feedback.”

(PMI Agile Practice Guide, Section 3.5 – Quality and Agile)

Mike Griffiths adds:

“In Agile, quality is not sacrificed. It is a fundamental principle. Teams ensure quality by defining acceptance criteria, using continuous integration, and practicing test-first development.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B may be helpful tactically, but doesn’t address the underlying concern.

C misrepresents technical debt.

D places too much QA responsibility on the product owner.

Answer: A

────────────────────────────────────

In Agile, one of the key principles is to provide continuous feedback and integration throughout the development process, ensuring that components are tested, integrated, and iterated upon regularly. By separating the work into three teams that work independently and only integrate at the end, the strategy risks delaying feedback and potentially causing integration problems. This approach could lead to significant issues when the components are eventually integrated, as they may not work together as expected due to lack of ongoing collaboration and integration. Therefore, working in parallel with proper continuous feedback and integration is crucial in Agile to minimize risks and ensure smooth delivery.