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

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

Once the team has clarity on the user stories and agrees they are ready, the next step in agile planning is to estimate them. According to the PMI Agile Practice Guide (Section 5.2: Estimating) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile estimation techniques like story points or Planning Poker help the team gain a shared understanding of effort, complexity, and delivery time.

Option A is correct: estimating comes before development and guides prioritization and planning.

Option B prematurely dives into task-level detail before effort is understood.

Option C skips planning and development entirely.

Option D refers to retrospective, which comes after execution, not before.

The " Life Timeline " exercise is a technique used to build psychological safety and vulnerability-based trust. According to Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), exercises that encourage sharing personal stories and emotional journeys foster deep interpersonal connection, which is foundational to high-performance teams.

The PMI Agile Practice Guide (Section 4.3.2: Building Trust) emphasizes the role of emotional intelligence and trust-building in agile teams, stating that teams become high-performing when they feel safe to express themselves without fear of judgment.

Option B is correct: the exercise builds vulnerability and trust—key drivers of high performance.

Option A focuses on trust but doesn ' t emphasize vulnerability, which is central here.

Option C is too generic.

Option D misframes the purpose—it’s about building connection, not assessing competencies.

The correct answer is C – Work with product owners and turn product backlog items into potentially shippable product increments.

Agile is grounded in the principle of delivering value early and often. Agile teams deliver value by continuously converting high-priority product backlog items into working software or product increments. These increments are potentially shippable, meaning they meet the Definition of Done and could be released at any point if the business chooses. Collaboration with the product owner ensures that the most valuable features are prioritized and refined before development begins.

From PMI Agile Practice Guide:

“Agile teams focus on delivering small, valuable, and potentially shippable increments of working product on a regular basis. This allows for frequent feedback and ensures that teams are always working on the most valuable features.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Working software is the primary measure of progress in agile projects. Agile teams collaborate with product owners to break down backlog items into increments that can be developed, tested, and delivered within a single iteration.”

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

Option A contradicts agile principles, which emphasize cross-functional teams capable of analysis, development, and testing.

Option B is a supporting activity but does not directly increase value delivery.

Option D reflects traditional project management thinking and does not align with the iterative, adaptive nature of agile.

Answer: C

The correct answer is C – Ask the team to restate the requirements and review them with the client.

Clear communication and shared understanding are core Agile values. The best way to resolve confusion is through direct collaboration. Restating and reviewing requirements with the client fosters alignment and transparency, which reduces rework and frustration.

From the PMI Agile Practice Guide:

“Agile encourages frequent interaction with stakeholders to clarify requirements and reduce misunderstanding. Requirements are best elaborated through collaboration.”

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

Mike Griffiths supports:

“User stories and acceptance criteria should be understood by both team and stakeholders. If confusion arises, revisit and clarify together.”

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

Why not others?

A may boost morale but doesn’t resolve the confusion.

B is speculative and not customer-centric.

D risks building something without validation.

Answer: C

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

Agile emphasizes transparency and team self-organization. According to the PMI Agile Practice Guide (Section 4.3.3: Self-Organizing Teams) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), a common practice is to make work and issues visible to everyone and allow the team to collaboratively manage their workflow. Using a shared workspace or board helps prevent redundant efforts and improves efficiency.

Option D is correct: shared visibility and self-allocation promote team ownership.

Option A misuses the backlog—issues aren ' t typically prioritized by customers.

Option B is directive and may reduce collaboration.

Option C focuses on analysis, not immediate resolution or coordination.

The sprint review/demo is the meeting where the team shows completed work to stakeholders and gathers feedback. According to the PMI Agile Practice Guide (Section 5.3: Sprint Review) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), stakeholders such as department heads or executives should attend sprint demos to stay informed and provide input.

Option C is correct: sprint demos foster transparency and stakeholder involvement.

Option A is typically for the Scrum team and product owner.

Option B is for team internal coordination only.

Option D is reserved for team process improvement—not stakeholder participation.

The storming phase (from Tuckman’s model: Forming–Storming–Norming–Performing) is marked by conflict and role negotiation. The agile coach or Scrum Master plays a critical role in guiding teams through this phase with structured facilitation and conflict-resolution techniques.

According to the PMI Agile Practice Guide (Section 4.3.2: Team Development Stages) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), the agile coach must provide support, guidance, and tools to help the team evolve toward self-organization and maturity.

Option B is correct: effective facilitation helps the team progress toward high performance.

Option A promotes dysfunction.

Option C risks escalating unresolved conflict.

Option D is overly individual-focused and not team-centric.

As a servant leader, one of the key responsibilities is to protect the team from external distractions and interruptions that could affect their ability to focus and deliver value. This allows the team to work in a productive environment and maintain their focus on the important tasks, such as delivering the minimum viable product (MVP). By removing impediments and guarding against distractions, the servant leader enables the team to be more effective and efficient.

The correct answer is A – Ask the team for suggestions.

In Agile, the Scrum Master serves the team by facilitating problem-solving rather than dictating actions. When a team member falls behind, the first step is to bring the issue to the team (e.g., in a daily stand-up or task review session) and allow the team to self-organize around resolving the impediment—whether through swarming, pairing, or shifting workload.

From the PMI Agile Practice Guide:

“Teams are empowered to self-organize and solve problems collaboratively. The Scrum Master supports this by facilitating discussion and removing impediments—not by reassigning work unilaterally.”

(PMI Agile Practice Guide, Section 4.1 – Agile Mindset and Section 6.2 – Coaching Agile Teams)

Mike Griffiths also explains:

“The Scrum Master fosters a problem-solving culture. When issues arise, teams should explore solutions together—this builds ownership and improves trust.”

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

Why other options are less suitable:

B circumvents team collaboration and may lead to resentment or overburdening.

C may be needed later, but collaborative resolution should be the first step.

D escalates prematurely and is not aligned with servant-leadership principles.

Answer: A

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