XP gave us test driven as a design tool. People who did not understand that the tests drove the design, work more bad tests to accompany more bad code. Today, more people are interested in validation product designs that live on top of programming designs.

1. Test Driven Product:
Applying Test Driven Thinking
to the Product World
David Hussman

2. Test Driven Product
Applying Test Driven Thinking to the Product World
David Hussman
Product
Kent Beck
(wanna be)

3. I did not write this …
Product
Kent Beck
(wanna be)
… but it had a big impact on me

4. And speaking of books …
… this one made a mark as well

5. Let’s reflect a bit …

6. Once upon a conference …

7. We were out to “test infect” people

8. We were keenly focused on “unit tests”

9. “If something is good,
let’s do it more (or all the time)”
-
“If something hurts,
let’s do it until it does not”

10. And the ideas became “sticky” …

11. TDD (Test Driven Development)
Test First Development
Make it work, make it right
Red, Green, Clean
Etc.

12. As TDD exploded, we questioned it further

13. Sometimes it was good

14. We learned that
“tests told the story of the code”

15. We showed that the tests had value that
went far beyond finding bugs

16. Sometimes the popularity was not good

17. Bad tests led to more bad code
“When the design thinking was lost, so was the process”

18. We over focused on developers

19. Some of us started looking for
something new …

20. Questions so far?

21. Enter ATDD
(Acceptance Test Driven Development)

22. Don’t start working on a story
before you’ve expressed the tests in code

23. “Pair programming” became “pairing”
Dev & Test - Dev & Prod - Test & Prod - etc.

24. “Test Driven Development”
was refactored to “Test Driven”
(sometimes)

25. Story tests (acceptance tests) added
context and clarified stories

26. Where unit tests told the story of the code,
story tests told the story of the product
(sometimes)

27. Often, story tests told the product story

28. Often times, “acceptance criteria”
lost site of product learning and
over focused on definition of done

29. We were still seeing problems

30. We were getting better but still building
to much of the wrong thing

31. Enter product driven development

32. Questions so far?

33. Here is a simple, non-tech example …
They’re refocused on impact

34. Here is a product development example

35. Here is a multi-team example

36. Universe of
all Product
Ideas
They’re all following a simple process …
Product
Choices
Collaborative Framing
Pragmatic Personas
Story Mapping
User Interviews
Market Research
Customer Journeys
Opportunity Mapping
Story Splitting
Validation Measures
Story Writing
Prototyping
… narrowing choices w/ validation measures (product tests)

37. Story telling produces tons of product tests
Here why (and how) it works

38. A vehicle that promotes design thinking …
… also produces product tests

39. Product tests are best expressed as
measurable impact in production

40. Impact can be measured and viewed like this

41. Behavior can be changed like this
Impact Driven Development

42. Simply put:
don’t start working on a story until you
discuss how you will measure the impact

43. Let’s close with an extreme example

44. Experiments running in production that help
Inform and produce better customers experiences

45. Test Driven Product:
Applying Test Driven Thinking
to the Product World
David Hussman
Questions?