What Bugs Taught Us About People

What Bugs Taught Us About People

How we created a bug rotation system at Etsy, and what we learned in the process. I used these Etsy listings in my talk:

http://etsy.me/1npk3Dz

Df2e97f18b5802e199d4920552a52d34?s=128

Rafe Colburn

January 30, 2014
Tweet

Transcript

  1. What Bugs Taught Us About People

  2. None
  3. over 23 million items listed

  4. more than $1 billion in sales in 2013

  5. 30 million users

  6. 60 million visitors per month

  7. None
  8. 60 deploys per day

  9. Varying degrees of code ownership

  10. Around 1000 open bugs

  11. None
  12. Fixler

  13. Bug Rotation 1.0

  14. Engineers attend one day per month

  15. One manager per week

  16. Engineers choose which bugs they want to fix

  17. Anticipated Benefits

  18. The early days

  19. We picked the low hanging fruit

  20. The era of discontent

  21. Paradox of Choice

  22. Unclear priorities

  23. Perceived lack of value

  24. Static schedule

  25. Engineering manager fail

  26. Why clean up other people’s messes?

  27. 6 months in: time to reconsider?

  28. Should we kill it?

  29. Uh oh, support loves bug rotation

  30. How do we tighten the feedback loop?

  31. Bug Rotation 2.0

  32. Support prioritizes the bugs

  33. Less bug rotation required

  34. Work in pairs

  35. Designated manager

  36. Opt out allowed

  37. What did we achieve?

  38. What did we learn?

  39. Mandates kill enthusiasm

  40. People want to collaborate

  41. You have to iterate on process

  42. Thank you!