Agile encouragesteam collaborationandself-organization. If a team member feels underutilized, the team should be encouraged to engage that person more fully, leveraging their skills across tasks. According to the PMI Agile Practice Guide (Section 4.3: Team Performance)andMike Griffiths' PMI-ACP Exam Prep Book (Chapter 3: Team Development), the agile practitioner supports healthy team dynamics and facilitates inclusive participation.
* Option Cis correct: promoting team-level inclusion helps resolve underutilization and fosters engagement.
* Option Ais a last resort and undermines team stability.
* Option Breframes the issue as a performance problem when it may not be.
* Option Dunnecessarily escalates what should be resolved within the team.

The principles of Extreme Programming (XP) focus on improving software quality and responsiveness to changing customer requirements. The key principles include:
* Rapid feedback: Getting feedback quickly from customers or stakeholders to ensure that the development process is on track.
Assume simplicity: Focusing on simplicity in the design and code to avoid overengineering and to ensure the software is easy to understand and modify.
* Incremental change: Delivering software in small, manageable increments that can be easily adjusted based on feedback.
* Embrace change: Being flexible and adaptable, especially in response to new requirements or changes in technology or business needs.
* Quality work: Ensuring high-quality software by emphasizing practices such as automated testing, continuous integration, and refactoring.

The correct answer is C - Ask management to ensure that the resource is available to only one project at a time.
Agile promotes dedicated, stable teams over multitasking. Task-switching reduces productivity and leads to context-switching overhead. If a key resource is overburdened and switching between multiple projects, the best solution is to secure focused commitment by escalating to management for support.
PMI Agile Practice Guide:
"Agile teams should be dedicated and work on one project at a time. Splitting attention across multiple efforts reduces velocity and quality due to context switching." (PMI Agile Practice Guide, Section 6.1 - Team Composition) Mike Griffiths highlights:
"Effective agile teams are stable, long-lived, and dedicated. Shared resources create bottlenecks, undermine predictability, and impair team dynamics." (PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A may solve bandwidth issues but not focus or ownership.
* B addresses symptoms, not the core issue of divided focus.
* D tolerates a harmful practice that contradicts agile team stability.

Predictable flow in agile is achieved by reducing variability in story size and complexity. According to the PMI Agile Practice Guide (Section 5.7: Flow-based Agile and Kanban), working with small, similarly sized user stories increases throughput predictability and improves cycle time.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) supports breaking large stories into smaller, testable chunks as a way to stabilize delivery and forecasting.
* Option A is correct: small user stories reduce variability and support predictable flow.
* Option B supports testability but doesn't directly improve flow.
* Option C and D are too broad or conceptual to specifically improve predictability.

The correct answer is D - Work with the team to ensure that acceptance criteria is being properly defined and understood.
Incomplete work that fails to meet stakeholder expectations often results from unclear or misunderstood acceptance criteria. Clarifying the definition of "done" and ensuring alignment between the Product Owner and development team can drastically reduce rework and defects.
From the PMI Agile Practice Guide:
"Clear and testable acceptance criteria help ensure shared understanding. Quality issues frequently stem from misaligned expectations or vague requirements." (PMI Agile Practice Guide, Section 5.2 - Definition of Done and Acceptance Criteria) Mike Griffiths writes:
"Teams must understand what success looks like for each story. Poorly defined or misunderstood acceptance criteria are a major cause of defects and missed expectations." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 - Problem Detection and Resolution) Other options explained:
* A (spike) is used for research or uncertainty-not fixing misunderstood requirements.
* B (burndown chart) helps track progress, not resolve defects.
* C may help indirectly but doesn't address the core problem of unclear requirements.