Skip to main content

Quick Poll Results: Sprint Duration

Following the discussions both elsewhere and on this blog about sprint duration, the questions poses itself - what is the preferred sprint length? So I ran a poll.

And the winner is... 2 weeks.

According to this very scientific survey (1 week on my blog, 228 Visitors, 50 votes), the most popular sprint duration is 2 weeks, followed by (early leader) 3 weeks, which lost by one vote.

The final results are:
1 week2 (4%)
2 week18 (36%)
3 week17 (34%)
4 week5 (10%)
1 month5 (10%)
longer, but fixed5 (10%)
variable1 (2%)

How long should the sprint be? There are many right answers, some of which argued for longer sprints:
  • The longest time you can shield your team from changes in work
  • bigger/harder stories imply longer sprints

But most argued for shorter sprints:
  • It should be short compared to the length of the project
  • Quicker response to changes/new information
  • More and earlier data points for measuring velocity
  • Achieving closure - there is a feeling of success associated with a successful sprint - the more often the better
  • Agility (and ROI) - the shorter sprint sprint, the quicker you can get functionality to the customer or user
  • Feedback - the sprint end is a chance to learn from the customer and from yourselves - the more often the better
  • Reliability of Commitment - the deadlines are nearer, the committments fresher in your memory
Very short sprints, i.e. 1 week are appropriate for very short projects, say 1 month. To do a 4 week project in 1 sprint, or even 2, does not leave much opportunity for feedback.

Mike Cohn pointed out:
3-week sprints have become very popular over the last 12-18 months. Before then most teams considered them odd ;) Seriously, it's a recent change for most teams
And the closing word:
The preferred sprint duration is the one that works best for your team :)
--Dmitry Beransky
I'll second that!

Thanks to Dmitry, Ben, Ash, Ilja, Paul, Kiran, Paddy, and Brett for their comments, as well as to everyone who voted!


savaged said…
I note some teams have a variable sprint duration. Is this a "Scrum smell" or is there any merit in it?
Peter said…
Hi Savaged,

It's considered to be a smell. According to Jeff Sutherland's latest Scrum-But test, an iteration length of 4 weeks or less is good. If the sprint length is longer or variable, this has been found to be a sign of lower performance.


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…