1. Leading Your Company into a Unit Testing State of Mind Roy Osherove Gil Zilberfeld

2. Poll  Tell us about your experience Poll Box  What would you like to learn? Question Box

3. My Experience

4. Want to share your stories?

5. It’s been a long road…  And now you have to convince Your team Your manager Other teams

6. You’re a champion!

7. Forces Environment  Management  Champion (you!) Implementation  Technical  Process

8. Dealing with resistance  Make people in charge of the change  Identify problem spots before beginning, and prepare them with good answers  Consult with key people before starting  Start incrementally, with simplest things  Start with a “pilot” project or team  Create mini champions  Send people to a course to convince them  Bring an outside consultant

9. Emotional reasons  Job Security  Bad past experiences with specific practices  Feeling of loss of control  Distrust  Feeling cozy  Fear of change  Fear of words “Agile”, “Extreme”, “Pair programming”..

10. Would vs. should  Why should people change We already know  Why would people change All the “logical” reasons are not enough How to convince them What makes them tick What makes them “anti” “what’s in it for me?”  Pain  Solution

11. How can I change people?  You can’t. You need to convince them to change themselves.  Give them an option

12. Don’t do it alone!

13. Where do I start?  Create buzz  Complain But only complaining doesn’t help  Talk about the solution

14. In your team  Teach others to write tests  Continue to write tests  Do it as part of code review

15. Get visible  Results  Metrics

16. What else?  Talk about the competition  Learn more

17. What’s next?  Continue  Create a movement  Lead  Be a change agent

18. And then…  Make change happen in other teams!

19. Summary  It’s hard  It’s been done before  It’s all about people  You won’t be alone too long  Fame and fortune awaits

20. Technical reasons 1. Not implementing supporting engineering practices 1. CI, Automated, test tools 2. Implementing technical practices badly 3. Too much Technical hardship Automated builds\tests\feedback..

21. Process Problems 1. “Full” process instead of small steps (just unit testing) 2. Not understanding where unit testing fits in the current process 3. Not including the whole team in decisions