Many programs, projects and enterprises are starting to consider transforming to agile ways of working. Some start with just stand-ups. Some then call it Scrum. Others start with execution, follow it with up-front analysis and design, and then call it ‘agile’. For many, the resultant transformation is too painful with hideous results. For some, though, the result is a thing of beauty and not a beast. What is the secret to changing from Waterfall to Agile? What are the pitfalls? How do you stay on track? How do you incorporate traditional project reporting? What is the recipe to the potion for a transformation that can be celebrated rather than treated as a curse?
[gigya embed id=”preziEmbed_3d67fcce1762bcd307e276baf28dd0ac7e60b456″ name=”preziEmbed_3d67fcce1762bcd307e276baf28dd0ac7e60b456″ src=”http://prezi.com/bin/preziloader.swf” type=”application/x-shockwave-flash” allowfullscreen=”true” allowFullScreenInteractive=”true” allowscriptaccess=”always” width=”475″ height=”400″ bgcolor=”#ffffff” flashvars=”prezi_id=3d67fcce1762bcd307e276baf28dd0ac7e60b456&lock_to_path=0&color=ffffff&autoplay=no&autohide_ctrls=0″ ]
This presentation made at the ACS Agile SIG in August and the LAST Conference in Melbourne in 2012, looks at Zen Ex Machina’s learnings from coaching the transformation of recent projects from Waterfall to Scrum. It looks at the psychology of learning Scrum behaviour, the symbiotic relationship necessary to create between the Scrum Master and Product Owner, and the habits – bad and good – that can hinder or help the process along. Overall, he’ll cover the learning lifecycle of Scrum for new teams and what it takes to increase your chances of becoming agile.
If your an agile coach, just knowing Agile, or Scrum, or how to set up a Kanban board won’t be enough to get you though the complexities involved in successfully performing the role and being an agile leader. Seek to expand your knowledge and capabilities and practice intentionally as part of your own continuous improvement.