Dev & UX: How not to be dicks to each other

This is the story of how dev and UX were thrown together and how it nearly killed us both. But how little by little we changed and learned about each other. Through interviews with designers and devs, and real life examples, we’ll talk about what worked, what failed spectacularly, and what we are doing today.

by Ruth Brown and Simon Young, from Agile UX 2015

Transcript

1. Dev & UX How not to be dicks to each other
6. - 2 methods
7. - 2 methods 3 screw ups
8. - 2 methods 3 screw ups 4 nailed-its
9. - 2 methods 3 screw ups 4 nailed-its 5 bottom lines
10. 1 - 2 methods 3 screw ups 4 nailed-its 5 bottom lines
11. One cupcake
15. Project was late
16. Project was late One deadline
17. Project was late One deadline Phase 2 phobia
18. Project was late One deadline Phase 2 phobia Design was scarce
19. 1 - 2 methods
20. 2 methods Waterfall…sort of
21. Research, design
22. Waiting, waiting Research, design
23. Waiting, waiting Build Research, design
24. Method #2 Agile.
27. 1 - 2 methods 3 screw ups
28. Screw up #1 Everything in one sprint
30. Roxy (Design)
31. Screw up #2 Design and dev too far apart
33. Kenese (Development)
34. Screw up #3 Changed squad direction quickly
35. Image of the Trade Me iPad app Then image of property app
36. 1 - 2 methods 3 screw ups 4 nailed-its
37. Nailed-it #2 1 Design : 2 Dev ratio
39. Ruth (Design)
40. Nailed-it #1 No squad until it’s completely resourced
42. Nailed-it #3 Location of design
43. Christine (Design)
44. Designer Designer Designer Designer and developers Developers Product Owner
45. Nailed-it #4 Adapted UX process quickly
50. 1 - 2 methods 3 screw ups 4 nailed-its 5 bottom lines
51. Bottom line #1 No dicks, teams need time to form
55. Christine (Design)
56. Bottom line #2 Team needs focus and trust
57. Sam (Test)
59. Bottom line #3 Design needs upfront time (but not too much)
61. Bottom line #4 Iteration needs to happen
62. Roxy (Design)
63. Bottom line #5 Rest of the business needs to understand Agile
64. Thanks!