Slow down to go fast agile 2012 - slides 0

441 views
236 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
441
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Slow down to go fast agile 2012 - slides 0

  1. 1. Slow Down to Go Fast: Lessons Learned Shipping Bing Voice Search on Xbox James Waletzky Director of Development & QA Practices, Crosslake (formerly Dev Lead @ Microsoft) jamesw@crosslaketech.com Randy Santossio Senior SDET, Microsoft (Xbox) ransan@microsoft.comAgile 2012 Microsoft 1 1
  2. 2. Who is this James guy? http://blogs.msdn.com/b/progressive_development/Agile 2012 Microsoft 2 2J
  3. 3. The little engine that couldAgile 2012 Microsoft 3 3J
  4. 4. Who is this Randy guy?Agile 2012 Microsoft 4 4R
  5. 5. From that little Redmond startup…Agile 2012 Microsoft 5 5R
  6. 6. How is your short term memory? “Please jot down yourDory says… questions and save them for the end.”Agile 2012 Microsoft 6 6J
  7. 7. How to win the raceAgile 2012 Microsoft 7 7J
  8. 8. A gile vs. a gileAgile 2012 Microsoft 8 8R
  9. 9. Just Bing it!Agile 2012 Microsoft 9 9J
  10. 10. The internal workings Games Applications Movies TV Music Apps bing Voice to Text Controller Xbox Voice Input Input LIVE (Kinect)Agile 2012 Microsoft 10 10 R
  11. 11. Story time!Agile 2012 Microsoft 11 11 J
  12. 12. Once upon a time…Agile 2012 Microsoft 12 12 J
  13. 13. They lived in a world where…Agile 2012 Microsoft 13 13 R
  14. 14. Boundaries existedAgile 2012 Microsoft 14 14 R
  15. 15. Kick off!Agile 2012 Microsoft 15 15 J
  16. 16. Their first taskAgile 2012 Microsoft 16 16 J
  17. 17. Best buddies?Agile 2012 Microsoft 17 17 J
  18. 18. Test/Dev: Best Buddies?Agile 2012 Microsoft 18 18 J
  19. 19. The buddies worked together…Dev: Team: Dev: Team:• sends code • reviews code • fixes found • signs off on review changes bugs code • builds & tests • updates code • dev checks in new code review code • finds new bugsAgile 2012 Microsoft 19 19 R
  20. 20. They huddled every day around this archaic boardAgile 2012 Microsoft 20 20 R
  21. 21. Comprehensive documentation? Well, no…Agile 2012 Microsoft 21 21 J
  22. 22. Many dependencies, great responsibilityAgile 2012 Microsoft 22 22 R
  23. 23. We used Milestones “checkpoints” orAgile 2012 Microsoft 23 23 R
  24. 24. Nobody is perfectAgile 2012 Microsoft 24 24 J
  25. 25. “I got your back, Bro”Agile 2012 Microsoft 25 25 R
  26. 26. What’s this about “Exit Criteria”?Agile 2012 Microsoft 26 26 R
  27. 27. Reality hurtsAgile 2012 Microsoft 27 27 J
  28. 28. The answer? Begin with the end in mind!Agile 2012 Microsoft 28 28 J
  29. 29. It’s the thought that countsAgile 2012 Microsoft 29 29 J
  30. 30. Automation happens!Agile 2012 Microsoft 30 30 R
  31. 31. …but we didn’t automate everythingAgile 2012 Microsoft 31 31 R
  32. 32. Why NOT automate everything?Agile 2012 Microsoft 32 32 R
  33. 33. We all took responsibility for quality Quality Ownership Dev Test PM DesignAgile 2012 Microsoft 33 33 J
  34. 34. Working in lockstepAgile 2012 Microsoft 34 34 R
  35. 35. I Unit Tests! Real, unsolicited quotes from Xbox developers “Unit tests flagged a “Unit Tests make real bug in legacy me feel cuddly” code that I never would have found” “Thinking test-first “In God we trust. helped me get the Everything else we design right the unit test” first time” “Is it failing because of a problem in the code, “My unit tests revealed a or because I don’t subtle bug that never would understand the code” have been found otherwise [except potentially by the customer]”Agile 2012 Microsoft 35 35 J
  36. 36. No unit tests? You’ve got some ‘splaining to do!Agile 2012 Microsoft 36 36 J
  37. 37. Bugs still happenAgile 2012 Microsoft 37 37 R
  38. 38. Bugs were “bliss” to this teamAgile 2012 Microsoft 38 38 J
  39. 39. What should YOUR team do? Start “by the book”, and always follow the principles, but break agile as necessary Form dev/test buddies early Build quality in early – remove the walls Collaborate in person and in writing Create “done” definitions based on tests Automate pragmatically, using coverage to adapt Pay down your technical debt before it is long-termAgile 2012 Microsoft 39 39 J
  40. 40. Agile 2012 Microsoft 40 40
  41. 41. James Waletzky Director of Development & QA Practices, Crosslake (formerly Dev Lead @ Microsoft) jamesw@crosslaketech.com Randy Santossio Senior SDET, Microsoft (Xbox) ransan@microsoft.comAgile 2012 Microsoft 41 41

×