Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

What does the Scrum Guide mean by "a development effort" (in the context of Sprint durations)?

Last post 03:20 pm February 28, 2018 by Andrew McKenzie
2 replies
03:44 pm February 23, 2018

Hi all,

I'm trying to understand the meaning of this phrase in the Scrum Guide (especially the boldface portion):

Sprints have consistent durations throughout a development effort.

Specifically, what I am wondering is: what is the maximum frequency at which a team can modify its sprint durations, and yet still be doing "Scrum by the Scrum Guide"? In other words, what period is referred to by "a development effort"? Is it through the life of a product, a release, a totally subjective time-frame that the team determines?

(NOTE: To be clear, I'm not asking for rules / best practices around selecting Sprint duration. I understand that there are many reasons to avoid changing sprint duration, and also various rationales and recommendations around shorter vs. longer Sprints.)


07:13 pm February 23, 2018

"Throughout a development effort" refers to the time taken until the Product Backlog is exhausted, or the Product Owner determines there would be insufficient value in continuing with further Sprints. Hence it is the life of the product.

If Sprint duration is amended by a team, for whatever reason, then they will need to re-establish consistency for the remainder of the development effort. Failure to do so will compromise the efficacy of empirical process control.

11:01 pm February 27, 2018

Thanks, Ian!