February 2010
M T W T F S S
« Jan   Mar »
1234567
891011121314
15161718192021
22232425262728

How to decide the length of a Sprint cycle – Part of Scrum




When you decide on using Scrum for your project development needs, one of the important questions is about the length of the Scrum cycle to be used. Not an easy decision in any way for the team, and something that the ScrumMaster has an important role in deciding. One thing to keep in mind is – the official length of a Sprint cycle is 30 days, but it is done as per the needs of the team. Here are some of the factors to keep in mind while discussing the length of the Sprint cycle:
- Planning and meeting time: Every Sprint cycle needs the following set of meetings, Sprint Planning, Sprint Review (including demo), and Sprint Introspection. As long as you can ensure that by reducing the time of the Sprint cycle, these meetings do not end up taking a larger percentage of the Sprint cycle, you are fine with reducing the time period of the Sprint Cycle.
- Ability to break down the requirements: The Sprint team executes on the user stories generated by the team. If the Product Owner cannot reduce the user stories into discrete enough levels that the team can execute in the shorter Sprint Cycles, then maybe the team is not ready yet to move to shorter Sprint Cycles.
- Eventually the Sprint cycle that needs to be adopted is the one that works the best for the team. Imposing a cycle that makes the team under too much pressure or does not have enough pressure needs to watched and then the best one implemented. A team that is mature will be able to do shorter Sprint cycles with much greater ease.
- When the team is working on a product where there is a need to move quickly, such as a team that needs to release patches, or new features for a web product (based on competitor analysis), then having a shorter Sprint cycle works much easier. Having a Sprint cycle that is a month or more could mean missing out against competitors.
- Having a shorter release means that the team can measure its performance far easier as compared to longer Sprint cycles where the performance can only be measured after a period of time in which it is too late to make corrections. This is problematic if the final release is only 2-3 months away.



Leave a Reply

  

  

  

* Copy this password:

* Type or paste password here:

9,786 Spam Comments Blocked so far by Spam Free Wordpress

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>