1. TDD is a long-term investment that may not show results for months, so customers need to understand it requires patience. 2. Teams may not be experienced enough with TDD and would benefit from drills or training before adopting it. 3. TDD principles are more difficult to apply to legacy code that lacks tests, but training can help use TDD effectively anyway. 4. TDD is primarily an internal design tool, not just for catching bugs, so its design benefits need emphasis over external quality assurances.

1. TDD and more than
9000 tries to sell it
to a customer
created by Anuar Nurmakanov
1

2. About me
Kazakhstan, Karaganda
Lead Software
Engineer
XP/EngX Practices fan
Agile Believer
And I love Java!
2

3. TDD Knowledge
Pyramid
3

4. Heard about TDD
Practice TDD
somehow
Do it in right way
Can coach and
help with TDD
Can sell it!
No one knows what is like to be
a seller...
4

5. Sometimes it is impossible to sell TDD to a customer?
We cannot explain that TDD might be good for a project?
5

6. Just because of
Reason 1
6

7. They need results, ROI, better
team performance
7

8. TDD is long-term investment
first results might be shown after a
couple of months and may be even
later
8

9. You just need to make
sure that customer
understands that it is
long-term investment?
9

10. Just because of
Reason 2
10

11. A team is not in the best TDD
form
11

12. May be just some need to work
on their TDD form
12

13. TDD must become one of the good habits when you
write code, and everyone should be in awesome TDD
form
13

14. You need to request TDD
Drills or any other TDD
trainings for your team
before you start selling
TDD to your customer?
14

15. Just because of
Reason 3
15

16. You are lucky to work with Legacy Code =))))
Legacy Code means low coverage, wrong testing pyramid and etc - it's
just a place where you are afraid to make a step
16

17. Some TDD
principles do
not work
when your
code is
legacy code
17

18. Your team should be
trained to use TDD even if
they work with any legacy
code?
18

19. Just because of
Reason 4
19

20. You sell it as a tool for improving EXTERNAL quality
You make promises that it will help to catch bugs
Many other things
20

21. If they add more
QA(Automation)
engineers in your team
In most of the cases customers
can achieve the same
And that's their usual
reply
21

22. TDD is more about INTERNAL
quality
TDD is about good DESIGN first(even
if it brings some other benefits)
22

23. Do not focus on bugs and
regression, make sure
that you can explain that
TDD is a DESIGN tool
23

24. Just because of
Reason 5
24

25. You sell it as a silver bullet
And forget about other engineering
practices
25

26. Do not forget about other XP
practices
26

27. Better control
Code Review Pair Programming
helps to control quality of
tests
helps to apply TDD and share
knowledge about TDD
27

28. TDD is not silver bullet
and often does now work
without other XP
practices
28

29. Conclusion
29

30. Do you sell debugging
techniques?
30

31. Do you sell IDE Hot Keys?
31

32. You
Just
Use it!
32

33. Do you need to sell
TDD then?
33

34. You can
Just
Use it!
34

35. 35

36. Thank you for your time!
36