Engineering

2 Fast 2 Furious: When Organizations become too Agile

By | | 1 min read


Summary
Taken from JAX Conference Keynote 2012 in Mainz: Declaring yourself Agile no longer means you're automatically cool or competitive. It might have in the olden days, when teams would be considered agile if they did 5 releases a year--but the word today has assumed a completely different meaning.

Taken from JAX Conference Keynote 2012 in Mainz:

Declaring yourself “Agile” no longer means you’re automatically cool or competitive. It might have in the olden days, when teams would be considered agile if they did 5 releases a year–but the word today has assumed a completely different meaning. Now, many organizations will happily admit to doing multiple releases a day. The problem is this: the majority of self-styled agile teams focus on speed, innovation and change, but very few focus on results.

This session takes a look at what happens when organizations become too agile, and how this addiction can become terminal for the business. We’ll cover real-life examples outlining the challenges and pain points of organizations striving to be agile. It will also offer top tips for dev teams to do agile the “right” way, helping them better manage change and understand the real impact that frequent releases have upon their business.

Slides available here on Slideshare.