Sprint Planning
A collaborative Scrum event at the start of each sprint where the team selects backlog items, defines the sprint goal, and creates a plan for delivery.
In-Depth Explanation
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
Business Context
Effective sprint planning ensures the team starts each sprint with a clear, achievable plan aligned with business priorities, reducing wasted effort and increasing predictability.
How Clever Ops Uses This
Clever Ops holds sprint planning at the start of every sprint with Australian client stakeholders, ensuring PO priorities are clear, capacity is realistic, and both parties are aligned on upcoming deliverables.
Example Use Case
"During planning, the team reviews velocity of 35 points, notes one member on leave (reducing to ~28), and selects 27 points of work aligned with the sprint goal."