Friday, February 03, 2012

Release Duration and Enterprise Agility

You ever wonder why your cellphone Apps seem like they have a new version every day or two? Dan Greening doesn't have to wonder, he knows why, they make better products, faster. - jj


Short release duration—the time from starting development on a feature set until it is tested for value, for example when customers pay for an upgrade—is an implied goal of agile methods and lean product management. Short release durations help companies test market theories to maximize profit, identify and mitigate deployment and usability problems, exercise the entire value chain of internal processes, and diagnose accumulating technical debt.


Attempting to reduce release duration may help drive agile behavior through a company. Shorter release durations motivate automated testing, high-availability architectures and streamlined configuration and deployment.


As an added bonus, release duration can be easy to compute: Finance departments often collect relevant data to satisfy capitalization and depreciation rules.
Citrix Online release duration history



After Citrix Online adopted Scrum [suth2011] and Enterprise Scrum [gree2010], release duration dropped from an average of over 35 months to less than 4 months, better than what it had as a small startup. Its market share rose during the same period. Data from another company, PatientKeeper, also seems to indicate that short release durations correlate with more profitable outcomes.


On February 7, 2012 at 11:00am EST, Scrum.org will host a webcast where I will explain how to measure release duration, how different forms of technical debt cause release duration to increase, and how limiting release duration can motivate paying down technical debt. Click here to register for the webcast.


On February 27 and 28th, 2012 in Los Angeles, Jeff Sutherland, Scott Downey and I will be teaching techniques to help you achieve similar outcomes, at our Certified ScrumMaster course in Los Angeles, . Click here to register for the Certified ScrumMaster course.


Dan Greening is an agile management consultant, specializing in enterprise-level agility, lean product management and finance. Dan joined Citrix Online in 2007, and became its Director of Engineering Productivity and User Experience from 2008 to 2011. He developed an agile portfolio management process. Dan co-founded several startups. He has been Principal Investigator on three National Science Foundation SBIR grants. He holds a Ph.D. in computer science from UCLA. Dan can be reached at dan@greening.org.


References

[gree2010]
Daniel Greening, “Enterprise Scrum: Scaling Scrum to the Enterprise Level,” 2010 43rd Hawaii International Conference on System Sciences (HICSS), Koloa, Kauai, Hawaii January 5-8, ISBN: 978-0-7695-3869-3 (10 pages)
[suth2011]
Jeffrey V Sutherland, D. M. van Solingen and Eelco Rustenberg, The Power of Scrum, CreateSpace (2011), ISBN 978-1463578060.

1 comment:

steeplebob said...

I agree short Cycle Time correlate to better quality and greater productivity. You seem to imply causality such that the imposition of short release cycles will manifest Agile behaviors. I think it may be the other way around: Agile practices will lead to shorter release cycles.