What Is a Sprint? Length, Rules and a Good Sprint Goal

In Scrum, a Sprint is a fixed-length period of one month or less in which the team produces a usable piece of the product. It’s the heart of Scrum: planning, the daily meetings, the review and the retrospective all happen inside a Sprint. As soon as one Sprint ends, the next begins.

For the big picture of Scrum, start with What is Scrum?

Where does the idea of a Sprint come from?

Teams working with long plans usually find out how far off course they are only when the work is finished. A Sprint reduces that risk: every few weeks you produce something that works, get real feedback and correct course. That way you never risk more than one Sprint’s worth of effort.

How long should a Sprint be?

According to the Scrum Guide, a Sprint lasts one month at most. Most teams choose two weeks. These questions help you pick the right length:

• How often do you need feedback? With high uncertainty, shorter Sprints let you learn faster.
• How many weeks does a meaningful piece take? A Sprint should be long enough to produce a usable increment.
• How heavy is the planning overhead? In very short Sprints, planning and review take up a larger share of the time.

Whatever length you choose, keep it fixed. Rhythm matters for the predictability of the team and its stakeholders.

The rules of the Sprint

• No changes are made that would endanger the Sprint Goal.
• Quality doesn’t drop; the Definition of Done isn’t compromised.
• The Product Backlog is refined as needed; scope can be renegotiated with the Product Owner as more is learned.
• A Sprint can only be cancelled if its goal becomes obsolete, and only by the Product Owner.

Sprint Planning: three questions

Every Sprint starts with three questions the team answers together:

1. Why? How will this Sprint add value to the product? The answer is the Sprint Goal.
2. What? Which items from the Product Backlog will be selected to reach the goal?
3. How? In which steps, and by whom, will the selected work get done?

For a one-month Sprint, planning takes at most eight hours; for shorter Sprints it is usually proportionally shorter.

How to write a good Sprint Goal

A Sprint Goal isn’t a list of unrelated tasks; it’s a one-sentence purpose. A good Sprint Goal:

• Describes value: not “finish 5 stories” but “customers can see their order status in the app.”
• Leaves room to manoeuvre: the goal stays valid even if the path to it changes.
• Is measurable: at the end of the Sprint you can clearly say whether it was met.

Common mistakes with Sprints

• Treating the Sprint as a deadline. A Sprint isn’t a box of commitments; it’s a learning loop.
• Filling every Sprint to full capacity. Teams that leave no room for the unexpected and for improvement overflow all the time.
• Quietly carrying unfinished work into the next Sprint. Work carried over without talking about why it wasn’t finished repeats the same problem.
• Changing priorities constantly mid-Sprint. That’s not a Sprint problem but a prioritisation problem; often the work’s flow needs to be made visible.

A note from the field: if your team keeps missing Sprints because of external dependencies, the problem isn’t the Sprint length but where the work waits. Measuring flow and making waiting visible helps more than shortening the Sprint.

Frequently asked questions

Is a Sprint the same as an iteration? They’re similar ideas. Sprint is Scrum’s name for an iteration, defined by rules such as a fixed length, a Sprint Goal and a usable increment.

Is there a gap between Sprints? No. A new Sprint starts the moment the previous one ends; the review and the retrospective are part of the Sprint.

What happens to unfinished work? It goes back to the Product Backlog and is re-prioritised. Whether it’s selected again is decided in the next Sprint Planning.

---

Why do your Sprints overflow, and where does the work wait? Let’s look together with our free 360 assessment.