Plan a sprint your team can actually finish
The two most common sprint failures are over-committing and having no real goal. This builder fixes both: it sums your story points against capacity and warns when you’ve taken on too much, and it forces a single, outcome-focused sprint goal at the top instead of a loose pile of tasks.
How it works
You enter a sprint goal, start date, length in working days, team size and velocity (capacity in story points). Then you list the stories you’re committing to, one per line, with points in parentheses. The tool parses the points from each line, totals them, and compares the total to your capacity — showing the percentage used or an over-capacity warning. It also computes the sprint end date by counting business days only, skipping weekends. Finally it assembles a full plan with the goal, dates, committed points, the numbered story list with acceptance-criteria placeholders, a definition-of-done checklist, a risks-and-dependencies section and the ceremony list.
Example and tips
Enter velocity 30 and stories totalling 36 points and the builder flags “OVER CAPACITY — cut scope” so you trim before the sprint starts, not three days in. Enter 24 points against the same capacity and it shows “80% of capacity”, leaving healthy slack for the unexpected.
- Keep the sprint goal to one sentence describing the outcome, not the task list.
- Plan to roughly 80% of velocity — reserve buffer for bugs, reviews and interruptions.
- Tighten the definition of done to your team’s reality so “done” means shippable, not “code written”.