In Kanban, one of the most effective ways to reduce variability in cycle time is by ensuring a consistent size of work items. According to the PMI Agile Practice Guide (Section 5.7 Flow-based Agile - Kanban), maintaining uniformity in work item size helps stabilize the system and supports reliable forecasts. Large or complex stories increase variability and unpredictability.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) recommends splitting large user stories and maintaining size thresholds for items on the board to ensure flow efficiency.
Option C aligns best with this practice: establishing a policy for breaking down large stories and adjusting WIP accordingly will help standardize flow, minimize cycle time variation, and improve predictability.

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 agile lead should evaluate the team ' s capacity and help them select user stories that align with around
80% of their available capacity for the iteration. This approach takes into account potential issues or interruptions and helps ensure the team is not overcommitting. By selecting user stories based on a realistic understanding of the team's capacity, the team is more likely to meet their commitments and avoid incomplete work. This method promotes sustainable work practices and helps the team maintain a predictable velocity over time.

The correct answer is D - A list of questions for the team and customer representative.
In Agile, creating a shared product vision is a collaborative effort that begins with open dialogue. The team should prepare insightful, value-driven questions to understand the customer's needs, pain points, desired outcomes, and business drivers. This supports co-creation of the vision rather than relying on rigid documentation.
PMI Agile Practice Guide:
"A shared product vision aligns the team and stakeholders. Early collaboration and asking the right questions help establish understanding and purpose." (PMI Agile Practice Guide, Section 2.2 - Agile Mindset) Mike Griffiths:
"Visioning meetings are facilitated conversations where teams and stakeholders explore product goals and user needs. Questions-not documents-drive clarity." (PMI-ACP Exam Prep, Chapter 1 - Agile Principles and Mindset) Incorrect options:
* A implies a rigid, document-driven mindset-contrary to Agile.
* B assumes the backlog exists before visioning.
* C is too early for acceptance criteria before vision alignment.

The correct answer is C - Ensure that members begin to self-organize as small teams with efficiently distributed skills.
Agile emphasizes self-organizing teams. When teams are too large, splitting into smaller teams is a good practice (Scrum recommends 5-9 members per team). However, rather than top-down assignment, the Scrum Master should enable and support self-organization. Teams should be encouraged to form organically while ensuring knowledge-sharing and cross-functional capabilities.
From the PMI Agile Practice Guide:
"Agile leaders support team self-organization by creating an environment of trust and encouraging the team to determine how best to accomplish their work." (PMI Agile Practice Guide, Section 5.2 - Team Composition) Mike Griffiths writes:
"Agile teams are self-organizing, and the role of the leader is to facilitate the conditions for that to occur, not to direct assignments." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance) Why other options are less appropriate:
* A suggests command-and-control behavior, which is contrary to Agile values.
* B makes assumptions about comfort levels and may ignore skill diversity.
* D disregards team input and imposes a solution, limiting buy-in and trust.