Agile in Stealth Mode kaizen WIP kaikaku flow value stream mapping visualize work flow cycle time lead time throughput TPS build failed CFDcreated byZsolt Fabókme@zsoltfabok.com October 25, 2011 @twitter: @ZsoltFabok evoline, Cluj Napoca, RO
Question: Why does an organisation want to do Agile instealth mode?Answer: ● Because Agile means change, and change is scary ● Because working in Agile costs more in a short term (rhetorical question: why do managers still think in short term?)
Dont mention Agile or Lean in publicBelieve or not it is working. Seriously. I tried it.
It is proven that TDD costs more:source: http://www.typemock.com/blog/2009/03/05/the-cost-of-test-driven-development/
Dont test everything, narrow down what to test code parts which ● are often used by customer ● changes frequently ● work with financial data ● are more likely will failreference: http://www.zsoltfabok.com/blog/2011/05/narrow-down-what-to-test/
Pair programming only for critical code partslike financial or core functionalities Remember that it means double cost!
Keep coding dojos. One hour a week doesnt cost as much as a coachphoto: http://www.josetteorama.com/events/nicholas-tollervey-on-code-dojo/
Virtualization is cheap. Build up your own local build, staging and production environmentphoto: http://www.infoq.com/articles/Continous-Delivery-Patterns
Dont plan ahead for more than a month, because the environment changes so frequent that most of the planning effort is going to be waste. ● Do Iterative planning ● Use responsive design by Kent Becksource: http://www.infoq.com/presentations/responsive-design
Use motivation 3.0 (Drive by Daniel H.Pink) and stop giving personal bonusesreference: http://www.danpink.com/drive
Thank you very much for your attention! For more check out my website: http://zsoltfabok.com/ or follow me on RSS: http://www.zsoltfabok.com/ blog/?feed=rss2 and Twitter: @ZsoltFabok