Sprint Lengths - 2 week vs 30 days
I want to implement Scrum, but I can't decide on a Sprint length. Ken Schwaber seems to relate that 30 days it the defacto... but I can't imagine waiting 30 days without the possibility of changing direction or reprioritizing.
Our projects usually only last 1-3 months using the waterfall method and moving to Scrum would probably mean less opportunity to fine tune.
I was thinking about 1 week sprints, but this seems like Scrum Micro Management.
Having 2 week sprints would probably be ideal, but I want to know if others out there were able to implement this successfully. What are the downsides? Is it more work/less work/same about of work to manage a team with shorter sprints?
BTW... 3 week sprints seem odd to me, who does a 3 week sprint? Why not just make it 4 weeks. ;)
Answer
I've worked on teams doing 1, 2 and 4 week sprints. It really is dependent on your organization. I prefer 1 or 2 week sprints. The current team I'm running is at 4 week sprints because we are coordinating efforts of 12 different products. I'm looking to move them to 2 week iterations soon.
The key thing to defining length is getting to "done, done". For some teams, this means in production. For others, it may mean verified by the business to meet their needs using an internal release. I'd start by defining done, done, then looking at how to structure your sprints around that. Ideally all stories are getting to done at the end of the sprint - and you aren't just doing Scrummerfall.