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

According to the PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement), managing stakeholder expectations starts with establishing a shared vision and involving stakeholders in key activities like iteration reviews. This ensures transparency, feedback, and alignment on progress and priorities.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the idea that a common vision and shared goals foster trust and improve stakeholder relationships.

Option A is correct: a shared vision and active involvement lead to better stakeholder alignment.

Option B and C are partially right but limit collaboration or dismiss stakeholder input.

Option D is inconsistent with agile’s emphasis on open, continuous communication.

Agile promotes cross-team collaboration and shared understanding of goals, especially when dependencies exist. The PMI Agile Practice Guide (Section 4.3.1: Team Collaboration and Alignment) recommends using vision alignment and shared objectives to reduce silos and improve coordination. A vision-sharing session ensures that all teams understand the business context and mutual interdependencies, helping build accountability and improve collaboration.

Option B is correct: shared vision fosters alignment and commitment.

Option A is punitive and against agile values of collaboration.

Option C disrupts team stability and should not be a first step.

Option D addresses the symptom (delivery delay) but not the root cause (lack of shared vision/accountability).

In agile, information radiators—such as visual boards placed in common areas—are used to make project data accessible, transparent, and real-time. According to the PMI Agile Practice Guide (Section 7.1 Communication), visibility improves coordination across interdependent teams.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) recommends that agile teams use visible, shared artifacts such as task boards, burn charts, or Kanban walls to improve cross-team communication and reduce friction.

Option B is correct: a physical or virtual board offers transparency and encourages informal communication.

Option A is useful but not as effective for rapid visibility.

Option C is one-way and doesn’t support real-time updates.

Option D is reactive and could cause delays or misalignment.

The correct answer is A because an Agile leader, such as a Scrum Master, is a servant-leader and facilitator. The Scrum Master supports the development team by helping remove impediments and facilitating healthy team dynamics. When there is misalignment or interpersonal conflict, the Scrum Master should help the team explore the root causes and encourage self-directed resolution.

From PMI Agile Practice Guide:

“Agile coaches facilitate conflict resolution by helping individuals understand each other’s perspectives and guiding them to collaborative solutions. The goal is to promote team ownership of outcomes and reinforce healthy communication.”

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

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“The role of the Scrum Master is not to direct or micromanage the team, but to facilitate communication and remove barriers that prevent team members from collaborating effectively. In conflict scenarios, the Scrum Master should help the team uncover the root issue, then allow them to resolve it constructively.”

(Mike Griffiths, Chapter 4 – Team Performance)

Option B is slightly less effective than A because it escalates to the whole team before trying a focused resolution.

Option C abdicates responsibility and may allow conflict to worsen.

Option D contradicts agile’s emphasis on self-organizing teams.

Answer: A

=========

A team charter with clearly defined norms, rules, and agreements is a critical tool for promoting trust and collaboration, especially in a globally distributed team. It establishes a shared understanding of how the team will work together, addresses potential communication challenges, and helps create a collaborative and respectful environment. By having these norms in place, team members from different cultures and time zones can align their expectations and behaviors, which is essential for overcoming challenges and preventing conflicts. This approach helps to foster a positive and productive team dynamic.

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.

Story point estimation in agile is a collaborative team activity, and consensus is critical. Techniques like Planning Poker are designed to reveal differences in understanding. According to the PMI Agile Practice Guide (Section 5.2 Estimating Techniques) and Mike Griffiths (Chapter 6: Adaptive Planning), when there ' s a discrepancy in estimates, it is essential to discuss and understand the rationale behind differing views.

Option C is correct: the team should discuss and clarify to reach a shared understanding.

Option A ignores potential misunderstandings.

Option B unnecessarily delays estimation.

Option D is incorrect—the team, not the customer, estimates the effort.

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

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

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

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

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

Velocity is a team-specific, relative measure of work done in a sprint and should not be used to compare teams. The PMI Agile Practice Guide (Section 5.4: Estimation and Velocity) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) highlight that a consistent and predictable velocity is more valuable than simply trying to exceed estimates, which can lead to overcommitment or burnout.

Option C is correct: predictability and consistency are hallmarks of agile maturity.

Option A and B falsely equate velocity across teams.

Option D values overperformance, which may undermine sustainable pace.

The MoSCoW method (Must have, Should have, Could have, Won’t have) is a prioritization technique commonly used in agile to determine which stories deliver the most value. The PMI Agile Practice Guide (Section 5.1: Prioritization Techniques) lists MoSCoW as one of the methods used by product owners and teams to prioritize backlog items.

Option A is correct: MoSCoW is a proven agile prioritization method.

Option B is used for estimation, not prioritization.

Option C is not a standard agile prioritization method.