The length of the srpint

Last post 05:23 pm June 24, 2015
by Ian Mitchell
2 replies
04:18 am June 23, 2015

Hey! I would like to ask what should be taken into consideration while choosing the length of the sprint. Scrum Guide informs us about risks of the long spring only.
Thank you in advance for your help.

02:56 pm June 24, 2015

The Scrum Guide isn't too explicit on this but we can draw some inferences...

Some things to consider --
Familiarity or comfort with the technology being used?
Market conditions (e.g. competing products)?
How often can the Product Owner and any concerned stakeholders be available?
Scrum Team maturity (i.e. are they just starting off or...?)

Typically, the shorter the better. We're seeing a lot of Teams working in 2-week cycles.

05:23 pm June 24, 2015

The chosen sprint length should help the Product Owner to maximize the release of value. The management of business risk and the observation of a suitable Definition of Done will be considered. This is the most important factor.

Next to consider is the team's duty to the organization, including any practices and standards which might shape the team's cadence. If this is to the detriment of product value then these practices and standards ought to be challenged.

There are certainly other considerations, including team constraints such as skill level. However the needs of the product and the organization are paramount. If these interests cannot be served to at least a minimally acceptable DoD, then no sprint length can ever be appropriate.