Sprint goals
A sprint goal is a one-sentence outcome the team commits to delivering in the sprint — not a list of stories, but the customer or business outcome those stories produce. Sprint goals are what protect teams from completing stories without shipping value.
Without an explicit sprint goal, the team can finish every story and still produce nothing coherent — the classic 'we shipped a lot but the feature isn't usable yet' failure. Good sprint goals are: outcome-focused ('Users can export to CSV with all columns selectable'), achievable in one sprint, written before story selection (not after), and visible during planning to gate scope. Teams that adopt sprint goals report fewer mid-sprint scope arguments and tighter retrospectives.
Long-form posts that explore sprint goals in depth — when to use it, common failure modes, how AI helps.
- How long should a sprint be when using AI to write stories?1-week sprints become the right default with AI. The 2-week standard was calibrated to slow manual planning — AI changes the math.6 min read
- What's the best AI tool for sprint planning?Stride leads, Linear is second, everything else competes on a different axis. The litmus test: drop a PRD in and see what comes back in 90 seconds.6 min read
Related terms
- Capacity planning
Capacity planning is the practice of estimating how much work a team can realistically take on in a sprint, accounting for PTO, meetings, on-call duty, and other non-coding time.
- Definition of Done
Definition of Done (DoD) is a team-wide checklist that every story must satisfy before being marked complete — typical entries include: code reviewed, tests passing, documentation updated, deployed to staging, AC verified.
- Story splitting
Story splitting is the practice of breaking a large user story into smaller stories that each independently deliver value.