Sprint Planning

Sprint planning kicks off each sprint, bringing the Product Owner, Scrum Master, and development team together to define what will be delivered and how.

Structure:

• Part 1 - What: PO presents highest-priority items and proposes a sprint goal. The team selects items they can commit to
• Part 2 - How: Team discusses technical approach, breaks items into tasks, and creates a delivery plan

Inputs:

• Refined product backlog with estimated items
• Team capacity (accounting for leave and commitments)
• Previous sprint velocity
• Sprint goal proposed by the Product Owner

Outputs:

• Sprint goal (agreed by PO and team)
• Sprint backlog (selected items with tasks)
• Initial plan for the first few days
• Identified risks or dependencies

Best practices:

• Ensure items are refined before planning
• Use velocity as a guide, not a mandate
• Do not over-commit - leave buffer
• Focus on the sprint goal, not just filling capacity
• Timebox to 2-4 hours for a 2-week sprint
• The team decides commitment - not PO or management