Distributed or remote teams are common in modern agile environments. According to the PMI Agile Practice Guide (Section 4.4 Working with Distributed Teams) and the PMBOK® Guide (6th Edition, Section 10.1), the agile practitioner must enable effective collaboration among all team members regardless of location. The guide recommends using video conferencing, collaborative workspaces, shared boards, and communication tools to simulate the benefits of co-location.

Mike Griffiths, in his PMI-ACP Exam Prep Book (Chapter 3: Team Performance), supports the use of collaboration tools to foster team cohesion and support agile values like communication and transparency, even when teams cannot be physically co-located.

Option A is correct: collaboration tools bridge the gap in distributed environments.

Option B and D promote siloing or team hierarchy, which undermines agile unity.

Option C moves away from agile values by emphasizing documentation over interaction.

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 comparing total scope (story points) and velocity, you can calculate the number of sprints each team expects:

Team A: 420 / 30 = 14 sprints

Team B: 280 / 20 = 14 sprints

Even though the story points are different, both teams estimate the same number of sprints, which means they estimate similar effort and duration relative to their own internal baselines. This aligns with the concept that story points are relative and not comparable across teams.

PMI Agile Practice Guide (Section 5.4: Velocity and Relative Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explain that velocity is a team-specific measure and cannot be directly compared between teams.

Option D is correct: both teams have estimated the same project size in their own context.

Options A and B incorrectly compare velocity between teams.

Option C is irrelevant; velocity is based on team experience, not technology assumptions.

In this situation, the Scrum Master observes that the developer is confused about a business rule during the daily coordination meeting. The best approach is to address the issue directly with the developer after the meeting. This ensures that the developer receives the clarification they need without disrupting the flow of the meeting or drawing unnecessary attention to the issue during the daily standup.

The correct answer is B – Meet face to face at regular intervals to enhance shared understanding.

While Agile favors colocation, it acknowledges that distributed teams are common. The Agile approach encourages face-to-face communication as the most effective means of information sharing. When colocation isn’t possible, periodic in-person meetings help establish team trust and understanding.

From the PMI Agile Practice Guide:

“Even with distributed teams, periodic face-to-face interactions are recommended to foster team cohesion and alignment. This is especially important during team formation and key planning activities.”

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

Mike Griffiths also advises:

“Remote teams benefit significantly from occasional in-person meetings. This improves relationships, shared understanding, and effectiveness in virtual collaboration.”

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

Why other options fall short:

A is about external support and not core to working agreements.

C undermines team transparency and agile principles of shared communication.

D could encourage fragmentation instead of collaboration.

Answer: B

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

A clear, shared vision statement is essential for alignment, motivation, and guidance. According to the PMI Agile Practice Guide (Section 2.3.1: Product Vision Statement), a strong vision statement enables team members and stakeholders to stay focused on what matters most, even as requirements evolve.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) stresses the importance of a shared understanding and active participation when forming the vision.

Option A is correct: it reinforces the value of shared vision and encourages stakeholder engagement.

Option B is helpful but doesn ' t ensure shared understanding across the team.

Option C risks misinterpretation and omits team collaboration.

Option D dismisses a core agile practice—vision clarity is crucial, even in a change-friendly environment.

According to the PMI Agile Practice Guide (Section 5.2 Requirements and User Stories) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), epics are large user stories that must be decomposed into smaller user stories for accurate planning and inclusion in sprints.

The two main drivers for breaking down epics are:

Size – Epics are typically too large to be completed in a single iteration and must be divided to create manageable pieces of work.

Priority – High-priority epics are decomposed early to allow the team to work on the most valuable items first.

This makes Option A the correct answer. The decision to decompose the epic is based on the need to fit it into sprint capacity and to align with backlog prioritization.

The correct answer is D – Confirm managers and stakeholders are invited to product review meetings. Agile promotes early and continuous feedback from stakeholders through regular reviews (e.g., sprint reviews or demos). Their active engagement ensures alignment with evolving business needs.

From the PMI Agile Practice Guide:

“Demonstrating working product increments at iteration reviews allows stakeholders to inspect progress, provide feedback, and align expectations. Agile teams rely on these sessions to validate whether the product meets business requirements.”

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

Mike Griffiths emphasizes:

“Frequent stakeholder reviews reduce risk by capturing early feedback. Stakeholder participation in iteration reviews ensures alignment and continuous validation of business goals.”

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

Incorrect options:

A includes only the team; stakeholders are critical to product validation.

B is insufficient—product owner alignment alone doesn’t ensure business alignment.

C refers to documentation, not collaboration.

Answer: D

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

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, it ' s important to continuously refine and prioritize requirements while managing dependencies. The team should work collaboratively to identify and prioritize the key dependencies that must be resolved to ensure that the user stories meet the Definition of Ready (DoR) criteria. By focusing on the highest priority dependencies first, the team can maintain progress while adapting to changes, rather than getting stalled trying to resolve all dependencies at once. This allows for more flexibility and efficient delivery.