This document discusses strategies for adopting Agile practices stealthily within an organization. It suggests avoiding mentioning Agile publicly and focusing Agile efforts on critical code through techniques like test-driven development, pair programming, and code dojos. Other recommendations include iterative planning over long-term planning and motivating employees intrinsically rather than through bonuses. The overall aim is to gain benefits of Agile while keeping costs low initially during cultural transition.

1. Agile in Stealth Mode
kaizen WIP kaikaku flow value
stream mapping visualize
work flow cycle
time lead time throughput
TPS build failed CFD
created by
Zsolt Fabók
me@zsoltfabok.com October 25, 2011 @
twitter: @ZsoltFabok evoline, Cluj Napoca, RO

2. reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance

3. Question: Why does an organisation want to do Agile in
stealth 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?)

4. Don't mention Agile or Lean in public
Believe or not it is working. Seriously.
I tried it.

5. It is proven that TDD costs more:
source: http://www.typemock.com/blog/2009/03/05/the-cost-of-test-driven-development/

6. Don't 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 fail
reference: http://www.zsoltfabok.com/blog/2011/05/narrow-down-what-to-test/

7. Pair programming only for critical code parts
like financial or core functionalities
Remember that it means double cost!

8. Keep coding dojos. One hour a week doesn't
cost as much as a coach
photo: http://www.josetteorama.com/events/nicholas-tollervey-on-code-dojo/

9. Virtualization is cheap. Build up your own local
build, staging and production environment
photo: http://www.infoq.com/articles/Continous-Delivery-Patterns

10. Don't 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 Beck
source: http://www.infoq.com/presentations/responsive-design

11. Use motivation 3.0 (Drive by Daniel H.Pink) and stop
giving personal bonuses
reference: http://www.danpink.com/drive

12. 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