Sprint Planning Board

Shape the sprint goal, commit selected stories, and prioritize stretch tasks against velocity.

Overarching Sprint Goal

selectedCommitted Scope (Core Sprint Goal)

11 SP

SP:Days:

stretchStretch Scope (Pull in if early)

5 SP

SP:Days:

carryCarry-over Scope (From previous sprint)

2 SP

SP:Days:

Guide & Documentation

Scrum Sprint Planning & Scope Commitment Board

Align your agile team around a clear sprint goal, committed user stories, stretch candidates, and carry-over work. Track total story points against available developer capacity before the sprint begins.

How to Run Sprint Planning

Establish the Sprint Goal

Define an overarching, measurable product objective that unites the team's focus for the upcoming iteration.

Allocate Stories into Lanes

Sort estimated backlog items into Committed scope, secondary Stretch goals, and historical Carry-over tasks.

Verify Point Velocity

Ensure the selected story point sum matches your historical sprint velocity and developer capacity.

Planning Board Features

Multi-Lane Scope Slicing

Organize stories into Selected commitment, Stretch goals, and Carry-over with one-click lane migration.

Real-time Velocity & Effort Tally

Instantly aggregates total story points and developer days to prevent overcommitting the sprint.

Sprint Kickoff Markdown Export

Export the goal, commitments, and owners directly into Jira sprint descriptions, Slack channels, or Confluence.

Sprint Planning Best Practices

§1Never start planning without an agreed single-sentence Sprint Goal that explains the user value.
§2Limit stretch goals to no more than 10%–15% of your total sprint commitment.
§3Refine carry-over stories before pulling them into the new sprint to diagnose why they slipped.

Frequently Asked Questions

What should be included in a Sprint Goal?

A sprint goal explains what value will be unlocked for the user upon completion (e.g. 'Enable self-serve checkout recovery to reduce support tickets'). Avoid goals that simply list Jira keys.

How are stretch stories handled in Scrum?

Stretch stories are pre-refined candidate tasks that developers can pull in only if all committed stories are completed ahead of schedule.

Can I copy the sprint plan to Slack?

Yes, the 'Copy Sprint Plan' button generates cleanly formatted markdown ready to announce sprint kickoff in Slack, MS Teams, or Jira.

Related Agile & Developer Tools

Sprint Capacity Planner

Calculate available developer days and focus factor.

Scrum Poker

Estimate story points with team consensus voting.

Story Readiness Checklist

Confirm backlog items meet Definition of Ready.