Sprint planning is a time-boxed meeting that kicks off each Scrum sprint (typically 1-4 weeks) where a team selects backlog items and breaks them into concrete tasks. Defined in the Scrum Guide since 1995, it serves two purposes: align the team on a sprint goal and commit to a realistic scope. This template captures the sprint goal, selected stories, task breakdown per story, and risks — useful as a shared artifact during the meeting and as a reference during daily standups.
Sprint planning is the meeting that kicks off each sprint in the Scrum framework, where the team decides what to deliver in the next 1 to 4 weeks. Originally defined by Jeff Sutherland and Ken Schwaber in the 1995 Scrum Guide, the meeting is time-boxed to 8 hours for 4-week sprints (proportional for shorter ones) and follows a two-part structure: first the team defines a sprint goal (what this cycle will deliver to end users), then selects product backlog items and breaks them into concrete tasks with estimates. Success depends on a well-refined backlog before the meeting — items should follow INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable). Common mistakes: pulling more than historical velocity supports or failing to commit to a clear sprint goal.