Skip to content

What's the ideal Sprint length

November 20, 2009 by Jack Milunsky

Introduction

I may have blogged about this previously. I have written so many blogs, I can't recall any more. However questions regarding Sprint length surface on the forums regularly.

As per usual, the answers one must give always depends on the context and every context is different than the next. So let me start with the context - this is an excerpt of a post on the scrum development group on Yahoo. Incidentally, Yahoo groups is a good place to hang out. You learn a lot from all the questions and the different contexts facing teams around the world.

The Context

A team of 5 members currently working with 10-day sprints. They haven't managed in the previous 5 sprints to have 100% of the User Stories completed. It is typically around 60-70% completeness.

There is proposal to increase the sprint duration to 15 days "because doing review meetings and planning every 10 days is a lot of overhead" according to the team.

My thoughts

Let me start out by stating some facts ...

The official Scrum sprint length is 30 days. However I don't think (I don't have facts to back me up on this but it's the sense I get from all the communications on all the forums) there are many teams working to 30 days any more.

Much of the Agile community agrees that shorter Sprints are better. So 2 week Sprints and even 1 week Sprints are becoming more the norm.

Why are shorter Sprints better?

1. Well we have learned from the Lean folks that shorter Sprints means less work-in-progress which means shorter cycle times and overall less waste.

2. Additionally, shorter Sprints tends to stress your process, revealing any flaws. Like no automated build process, automated test harnesses our unit test frameworks. Fixing these flaws has a tendency to provide leaps in productivity gains for your organization.

So assuming you buy the argument that shorter Sprints are better. My initial quick answer to the question is don't try to lengthen the Sprint. Rather try to figure out why you're only hitting 60% - 70% of your originally committed goals.

By the way, 60% - 70% may not be that bad, after all you have a team that is currently demonstrating a consistent output Sprint after Sprint.

So that leads me to think that either the story point estimation is not consistent, or the team is just over-committing. So I would suggest that they do the following.

Try to really assess what is going on in the retrospective. Let team members speak freely about their thoughts on the matter.

I would definitely spend a little bit of time re-assessing the size of a few completed items i.e. if the story was 10 points originally, what would they estimate the size now, after the fact. Re-assessing the relative size may well fix the problem.

Some folks, most notably Ron Jefferies, would argue why do you need to get your estimation down pat. Well in my opinion for one, predictability goes a long way to help remove team stress. So its great for a team to say we can commit to say 100 points and deliver between 90 and 110 each Sprint. The business will love you for this.

Whats good about this problem in and of itself is that Scrum is doing what it's supposed to do; surface issues for the team to resolve. And if the team feels that going to 15 day Sprints is the right thing to do, so be it - it might well be. But I would try to first figure out why 2 weeks is not cutting it. Many teams make it work so it should be doable.

Hope this helps if you're in the same boat. If not at least if it provides food for thought!

Jack
agilebuddy

About the Author: As COO and Scrum Master, Jack Milunsky heads software development at Brightspark. Jack is an early adopter of Scrum and has a great passion for early stage startups. Jack is co-creator of Agilebuddy, a next generation Scrum Application SaaS. Jack combines over 18 years of experience managing software development teams both large and small. You can follow Jack for great tips on Agile at http://twitter.com/agilebuddy

Comments

Re: What's the ideal Sprint length

November 20, 2009 by mregazzi-anonymous (not verified), 2 years 10 weeks ago
Comment id: 4120

Hi Jack,

I'm relatively new to Scrum, not to software development. I think that there are some situations shorter sprint is a better solution (2 weeks, 1 is too short in my opinion).
There are two things we must keep in mind tailoring the process: time-boxing and "the art of possible": time-boxing simply helps to keep focused, meanwhile we must give our customer some useful "thing" (business value). if we just need time-boxing, maybe our approach to customer is not correct.

At the same time I'm wondering a (big) project with two sprint sizes:
four weeks for the first 2/3 sprints, when it's more difficult to develop something really valuable, when the team is still forming and not performing yet, ecc.
2 weeks for the following sprints

But would the product owner prefer to attend sprint review 2 times a month, with the possibility to change requirements more frequently but with a greater effort with less valuable increments, or would he/she prefer longer sprints ? And the team (more changes = less focus) ?

p.s. Now we are in the middle of the sprint number 8, 2 weeks each sprint.

Matteo

sprint length

November 23, 2009 by Jack Milunsky (not verified), 2 years 10 weeks ago
Comment id: 4136

I am not of the opinion that teams should switch sprint lenths and certainly not to accomodate the PO's availability and schedule.

The Sprint is all about cadence. You want to get the team in a rythm. And so it's important for teams to figure out what's best for them.

Shorter sprints really stress a team's core capabilities and really surface issues that can be automated for example. So shorter sprints make teams better at what they do in my opinion.

We also know that from the research in Lean, shorter sprints tend to reduce over-all cycle time and this is a desired affect you want to get.

Thanks for your comments

Regards
jack

1 Week Sprints

December 14, 2009 by Mike Benner (not verified), 2 years 7 weeks ago
Comment id: 4389

We run one we sprints at my company and as you stated it definitely stresses the systems in place. We know very quickly if something is not right and can address it. It has caused the "underestimated" argument to come up a few times, but usually we find it is an over commitment issue. We don't adjust the size of our sprints to accommodate not hitting our commitment, but we do lower the committed velocity to a more realistic and accurate number after about the 2nd or 3rd iteration.

in favour of 2 week sprints

December 16, 2009 by Urs Enzler (not verified), 2 years 7 weeks ago
Comment id: 4418

Hi Jack (and all others)

We use 2 week sprints.
One additional reason for this time frame is that 2 weeks is about the duration that I can keep something in my mind (things the PO told the team during the planning meeting). No chance to recall much in the third week.

Therefore, shorter sprints minimize (only minimize - not eliminate!) the repeated discussion of user stories. They may be discussed to get more detail but not to repeat the same again in the sprint.

Cheers
Urs

P.S. the CAPTCHA on this blog are very hard to read over here!

Probably one day longer than

January 17, 2010 by Pariuri (not verified), 2 years 2 weeks ago
Comment id: 5150

Probably one day longer than the spring length the team has chosen? :-)
Seriously though. I have worked in one and two week sprints and my favorite is the one week model. We found that there is less time for things to go astray, and the team has to demo at the end of each week. So you get more focus on the delivery.
I would have thought though the type of work also plays a part. If your building something where one week does not normally result in something to demo but two weeks would, two weeks has to be better.

Your music is amazing. You

January 23, 2012 by Anonymous (not verified), 1 week 4 days ago
Comment id: 20817

Your music is amazing. You have some very talented artists. I wish you the best of success. job site

This is an interesting

January 23, 2012 by Anonymous (not verified), 1 week 4 days ago
Comment id: 20819

This is an interesting article and has been very helpfull. I will check back again soon to read the other articles. Thanks canon pixma mx882 all in one

I think you have raised a

January 23, 2012 by Anonymous (not verified), 1 week 4 days ago
Comment id: 20820

I think you have raised a very good topic that has generated good discussion among the users of your site. it helped me learning a lot. kingston memory cards

I don’t even know how I ended

January 24, 2012 by buy domain in india (not verified), 1 week 3 days ago
Comment id: 20821

I don’t even know how I ended up here, but I thought this post was good. I don’t know who you are but definitely you are going to a famous blogger if you aren’t already Cheers!

good article

January 25, 2012 by seo forum (not verified), 1 week 2 days ago
Comment id: 20826

Great information you've provided us with here. Thanks so much for sharing. Nice site too Have a great one we offer best

I am really enjoying reading

January 25, 2012 by vijaysbhagat (not verified), 1 week 2 days ago
Comment id: 20829

I am really enjoying reading your well written articles.sony e reader store It looks like you spend a lot of effort and time on your blog. I have bookmarked it and I am looking forward to reading new articles...!

this is really nice to

January 26, 2012 by Anonymous (not verified), 1 week 1 day ago
Comment id: 20830

this is really nice to read..informative post is very good to read..thanks a lot! Orlando Web Design

I was very pleased to find

January 27, 2012 by zalina jopin (not verified), 1 week 22 hours ago
Comment id: 20832

I was very pleased to find this site. I wanted to thank you for this great read!! I definitely enjoyed every little bit of it and I have you bookmarked to check out the new stuff you post.Thanks for sharing this useful information! Hope that you will continue with the kind of stuff you are doing. free cell phone spy software

I strongly agree with your

January 27, 2012 by Join Scentsy (not verified), 1 week 18 hours ago
Comment id: 20833

I strongly agree with your thought. It's pleasure near me i read your article.

Informative article

January 27, 2012 by cheap backlinks (not verified), 1 week 12 hours ago
Comment id: 20836

I admire the valuable information you offer in your articles.
I will bookmark your blog and visit here often.

Many thanks regarding giving

January 27, 2012 by vijaysbhagat (not verified), 1 week 10 hours ago
Comment id: 20838

Many thanks regarding giving everybody a really breathtaking possiblity to read in detail using this web site.philips sonicare It is usually so great plus filled with a good time for me personally as well as my business office friends to search your website practically 3 times weekly to review the most recent takes you could have. And indeed, I'm so actually surprised together with your shocking information you give. Some a couple of items on this page tend to be ultimately the best I have ever experienced.

assuming you buy the argument

January 28, 2012 by guyziiz (not verified), 6 days 19 hours ago
Comment id: 20843

assuming you buy the argument that shorter Sprints are better. My initial quick answer to the question is don't try to lengthen the Sprint. Rather try to figure out why you're only hitting 60% - 70% of your originally committed goals.happy birthday

wonderful post

January 28, 2012 by NJHWDP (not verified), 6 days 19 hours ago
Comment id: 20844

wonderful post shared by Jack Milunsky on the topic what is ideal sprint length. good information shared. thanks for the post. - NJHWDP

I am hoping the same best

January 29, 2012 by super (not verified), 5 days 14 hours ago
Comment id: 20845

I am hoping the same best effort from you in the future as well. In fact your creative writing skills has inspired me. Funny Clip

Get Your Ex Back

January 31, 2012 by Get Your Ex Back (not verified), 3 days 15 hours ago
Comment id: 20856

If your home has issues with the foundation then you urgently need foundation repair. A bad foundation can be very harmful for the structure of the home..Get Your Ex Back

franchising awards

January 31, 2012 by franchising awards (not verified), 3 days 11 hours ago
Comment id: 20857

Stumbled across your blog and WAS amazed Instantly With All That Is the Useful information on it. Great post, just what i was looking for and i am looking forward to reading your other posts soon. franchising awards

I recently came across your

January 31, 2012 by MikeHenry (not verified), 3 days 10 hours ago
Comment id: 20858

I recently came across your blog and have been reading along. I thought I would leave my first comment. I don’t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.
Cell phone repair mississauga
iphone repair mississauga
Cell phone unlocking mississauga
mississauga iphone repair

Informative article

February 1, 2012 by seo (not verified), 2 days 13 hours ago
Comment id: 20875

I think you have raised a very good topic
that has generated good discussion among the users of your site.
it helped me learning a lot

franchising laws

February 1, 2012 by franchising laws (not verified), 2 days 12 hours ago
Comment id: 20876

There are so many comments here that are really interesting I am so impress to your blog. franchising laws

fast food franchise

February 1, 2012 by fast food franchise (not verified), 2 days 11 hours ago
Comment id: 20877

It is a freat pleasure to post and read comments on this page keep it up guys. fast food franchise

mobility scooters

February 3, 2012 by mobility scooters (not verified), 16 hours 27 min ago
Comment id: 20887

You make me understand. It is knowledge for me. Great post of helping me.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

Best of AgileSoftwareDevelopment.com