Guide to Transitioning_Cohn
Fall 2007 Scrum Gathering: London
Wednesday, 14 November, 15.30-17.00
“Succeeding with Agile: A Guide to Transitioning”
Presenter: Mike Cohn, CST, Mountain Goat Software, USA
Transitioning to an agile development process is unlike most transitions an organization may make. Many transitions begin when a strong, visionary leader plants a stake in the ground and says, “Let’s take our organization there.” Other transitions start with a lone team thinking, “Who cares what management thinks, let’s do this.” The problem in transitioning to agile is that neither of these approaches alone is likely to lead to the long-term sustainable change required. Transitioning to agile is harder than many other corporate transitions because the transition process must be congruent with development process we are trying to adopt. We cannot, for example, wish to adopt an agile process because we believe in the power of self-organizing teams but then use a transition process that is not itself self-organizing. Nor can we adopt agile because it acknowledges the inherent uncertainty in precisely planning a project but then hope to precisely plan the transition to agile.