We all know the importance of product designers and developers working more closely together. One approach to achieving this is ‘dual-track delivery’. But we shouldn’t think of dual-track delivery as separate tracks, because they’re not. About Ant Boobier: Ant Boobier is Practices Lead at BNZ and has been doing Agile for more years than he cares to remember. RAD in the 90s, XP in the 2000s and a magic mix of Lean UX and Agile today. He is a people geek who loves a good experiment.

1. The Art of Dual Track Development
Ant Boobier
@antboobier
Practices Lead– BNZ

2. digital
Ant Boobier
Practices Lead
@antboobier
anthony_boobier@bnz.co.nz
linkedin.com/in/antboobier

3. “It doesn’t
matter how
well you build
an unwanted
feature”
“It will always
be unwanted”

4. Discovery work
• Focus on fast learning and validation

5. • Focus on predictability and quality
Delivery work

6. 2 activities happening in parallel

8. Dual track development, is 1 product
team responsible for:
• ongoing discovery and delivery
activities
• measuring itself against outcomes
rather than features shipped

9. Jeff Patton

10. Does this model
fit in my head ?!

11. Merge the bubbles

12. “There is no single product
discovery process just as
there is no single product
development/delivery
process”
Marty Cagan

14. Agilists are
magpies

15. All this cool stuff, looks to empirically achieve the
same stuff…

22. Personas

23. Walk in their shoes
(not matter how stinky)

24. Customer journey map

27. Wireframe

28. Spike it

30. Yes, that’s a
learning
activity too

31. Make a
Change
(or)

33. “We are what we repeatedly do.
Excellence then, is not an act but a habit”

35. What’s a kata ?

36. Focus on a clear goal

37. Metrics grounded in research

38. Things that need to be true for our
product to succeed

39. “Assumption”

40. What is the minimum experiment you can
create to quickly test your assumption ?

42. Be intentional on how you do things

44. Thanks for listening