Sprint Planning

Correct Answer: Break down the story into smaller parts and focus on items that can be completed independently

Breaking down the story into smaller parts that can be completed independently is the optimal strategy because: 1. It allows the team to make progress on portions of work they can control 2. It maintains team velocity and productivity 3. It follows Agile principles of delivering incremental value 4. It reduces dependency risks and bottlenecks The other approaches are less effective because: Scheduling multiple inter-team coordination meetings adds complexity and delays, potentially slowing down the entire sprint process. Adding buffer time to estimations is a risky approach that does not address the core dependency issue and may lead to sprint overruns. Moving the entire story to the next sprint is an overly cautious approach that delays value delivery and may not solve the underlying dependency challenge if the other team's timeline shifts.

Correct Answer: Calculate available person-days and subtract planned absences and team events

The most effective way to create a capacity forecast is to calculate available person-days and subtract planned absences and team events. This method provides the most accurate and realistic forecast because: - It considers actual available working days - Accounts for known time off and commitments - Includes team ceremonies and events - Provides a concrete basis for sprint planning Other approaches are less effective because: Using historical velocity to multiply person-days mixes two different measurement systems and could lead to inaccurate forecasting. Applying an arbitrary 15% reduction to previous sprint story points lacks scientific basis and fails to account for actual team availability. Estimating daily work hours multiplied by sprint duration oversimplifies the forecast and may not account for meetings, events, and other commitments that affect actual capacity.

Correct Answer: Facilitate a balanced 60-40 split between Sprint Goal discussion and detailed task planning

The approach of a 60-40 split between Sprint Goal discussion and detailed task planning is optimal because: It provides the right balance between strategic and tactical planning during Sprint Planning: 1. The majority of time (60%) focuses on understanding the Sprint Goal and its value, ensuring team alignment and commitment 2. The remaining time (40%) allows adequate time for breaking down work into manageable tasks 3. This ratio maintains focus on delivering value while ensuring proper execution planning Why other approaches are suboptimal: - A 30-70 split places too much emphasis on technical details at the expense of understanding the strategic goals - An 80-20 ratio dedicates too much time to high-level discussions, leaving insufficient time for proper task planning - Allowing the Product Owner to dominate 75% of the meeting contradicts Scrum's collaborative nature and reduces development team engagement The 60-40 split promotes balanced participation and ensures both strategic understanding and tactical planning receive appropriate attention.