How long is a Sprint?

A Sprint is one month or less. Most teams settle on 2 weeks — short enough to get feedback quickly, long enough to build something meaningful.

Can you change Sprint length mid-project?

You can, but it's disruptive. Consistent Sprint length lets the team build a rhythm and improve velocity tracking over time. Only change it when there's a structural reason the whole team agrees on.

What happens to unfinished work at the end of a Sprint?

Unfinished items return to the Product Backlog. They don't automatically carry over. The Product Owner re-evaluates priority before the next Sprint Planning.

Can you add work to a Sprint once it has started?

The Scrum Guide allows scope to be negotiated between the Product Owner and Developers — but the Sprint Goal stays fixed. In practice: resist additions unless something critical breaks. Every addition is a tradeoff against what the team already committed to.

Who can cancel a Sprint?

Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete — for example, because of a major business pivot or a cancelled contract. It's rare and should be treated as a serious event.

What is the Sprint Goal?

The Sprint Goal is a single objective that gives the Sprint meaning and direction. It's not a task list — it's the answer to 'what should be true at the end of this Sprint?' A good Sprint Goal lets the team say no to mid-sprint interruptions.

Foundation7 min read

What is a Sprint?

A Sprint is the heartbeat of Scrum — a fixed-length working period, usually two weeks, during which the team commits to a Sprint Goal and delivers a working Increment. The goal of a Sprint isn't to finish everything on the list. It's to learn something meaningful and build something real.

Sprint definition

A Sprint is a fixed-length period (one month or less) in which a Scrum team produces a Done Increment. All Scrum work happens inside Sprints — Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective are all contained within it. Once a Sprint starts, its duration doesn't change.

The Sprint Goal — the most skipped part of Scrum

Most teams have a task list for their sprint. Fewer have an actual goal. The difference is significant: a task list tells you what to do; a Sprint Goal tells you what should be true when you're done. When something urgent appears mid-sprint — and it always does — the Sprint Goal is the team's answer to 'should we interrupt what we're doing?' If the new work doesn't threaten the goal, it waits.

How long should a Sprint be?

Technically, one day to one month. In practice, the question narrows to two weeks vs. four weeks, and two weeks wins almost every time — not because it's a rule, but because four weeks is too long to hide problems. A month-long sprint means a month before you find out that the design assumption was wrong.

1 week

Fast feedback, but barely enough time to build something reviewable. Good for teams doing continuous deployment.

2 weeks

The industry standard. Enough time to complete meaningful work, short enough to course-correct before too much is built on a wrong assumption.

4 weeks

Technically Scrum, but you lose most of the benefit of short cycles. Usually a sign of large batch thinking.

What happens inside a Sprint?

Four events are contained within every Sprint. They're not optional ceremonies — they're the inspection and adaptation mechanisms that make Scrum work.

Sprint Planning

Opens the Sprint. The team sets the Sprint Goal and selects Product Backlog items they can deliver. Duration: up to 8 hours for a one-month Sprint.

Daily Scrum

A 15-minute daily sync for Developers to inspect progress toward the Sprint Goal and adapt their plan. It's not a status report.

Sprint Review

At the end of the Sprint, the team presents the Increment to stakeholders. The Product Backlog is adapted based on feedback. This is the external inspection point.

Sprint Retrospective

The team inspects how they worked — processes, tools, interactions — and identifies one or two improvements to implement next Sprint.

What happens to unfinished work?

Work that isn't completed doesn't automatically roll over to the next Sprint. It goes back to the Product Backlog, where the Product Owner re-evaluates it. This isn't a failure — it's information. Why wasn't it finished? Was it too big? Was there a hidden dependency? The retrospective is where you diagnose it, not where you hide it.

Frequently asked questions

Is a Sprint the same as an iteration?

Mostly yes — both are time-boxed development cycles. 'Iteration' is used in XP and SAFe; 'Sprint' is Scrum-specific. The mechanics are the same.

Can the Sprint length differ between teams?

Yes. Different teams in the same organization can run different Sprint lengths. What matters is that each team is consistent with itself.

Do Sprints run back-to-back?

Yes. A new Sprint starts immediately after the previous one ends. There's no gap or planning week between Sprints.

Test your Scrum knowledge

Take the free Scrum Quiz — role-based questions aligned to the 2020 Scrum Guide.

Take Scrum Quiz →