1 / 82

Lessons Learned Through Dogfooding

Lessons Learned Through Dogfooding. Mario Rodriguez. Senior Program Manager. Team Foundation Server. How not to “screw up” like we did. Opening the Kimono. me. Joined Microsoft in 2002 as a tester in the Xbox group. Project Gotham Racing, AI in Forza Motorsport

octavius
Download Presentation

Lessons Learned Through Dogfooding

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons Learned Through Dogfooding Mario Rodriguez Senior Program Manager Team Foundation Server

  2. How not to “screw up” like we did Opening the Kimono

  3. me Joined Microsoft in 2002 as a tester in the Xbox group. Project Gotham Racing, AI in Forza Motorsport Worked in Version Control for three years (branch visualization patent) Responsible for the platform to run TFS on Windows Azure

  4. Possible Agenda • How we use Visual Studio and Team Foundation Server to build Visual Studio and Team Foundation Server. How much dogfood are we talking about? • Lessons we’ve learned along the way. How did it taste? What have we learned?

  5. Dogfood? Really?

  6. TFS at Microsoft • 42 instances • 19,700 unique users • 6,154 team projects • 7.9 million work items • 95% of the data is version control

  7. Team Foundation Server - How big is big? • 1,032,045,223 files • 2,024,223 checkins • 911,432 work items • 3,612 unique users • 17.3 TB of data • Largest table: 3.1TB; 4.3 billion rows

  8. 116 scenarios Scenario Scenario Scenario 1,562 experiences Experience Experience Experience Experience Experience 7,902 user stories User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story

  9. 7,902 user stories 11,962 areas and iterations 2 million check-ins 1 billion files

  10. 8 1 Lessons we learned 3 10 5 2 4 9 6 7

  11. We started too aggressive

  12. Phase your rollouts and react/learn along the way 10

  13. We bite more than we can chew

  14. It’s impossible to ship everything in the box 9

  15. We did not practice Agile

  16. Dev11 3 weeks 8 TFS 2010 6 weeks TFS 2008 10 – 12 weeks January February March

  17. Execution Sprint 4 Sprint 3 STABILIZATION Sprint 2 Sprint 6 Sprint 1 Sprint 5 Milestone Y Milestone X 3-week sprints

  18. Sprint Done List • Stories done • Sprint review/video • Retrospective • Bugs triaged Sprint 3 Sprint 2 Sprint 1

  19. Agile development leads to better decision making 8

  20. Agile development leads to better everything 8

  21. We introduced too much process

  22. 56 visible fields!

  23. 96 visible fields!

  24. Autonomy, Mastery, Purpose It requires resisting the temptation to control people, and instead doing everything we can to reawaken their deep-seated sense of autonomy.” – Daniel Pink, Drive • Autonomy– The urge to direct our own lives • Mastery – The desire to get better and better at something that matters • Purpose – The yearning to do something that we do in the service of something larger than ourselves.

  25. Autonomous Teams, Central Reporting • Independent teams • Self-defined processes • One main cadence • One reporting system • One leadership team

  26. Simplify the process and provide autonomy to your teams 7

  27. We tried to do everything in Visual Studio

  28. 6

  29. Visual Studio is not a project management tool 6

  30. We made some bad calls on reporting

  31. Deeper integration with Office • More out of the box

  32. Reporting must be easy 5

  33. We went fast … really fast

  34. 2008 Beta1 2005 Beta1

  35. Managing Debt • ZBB • Exit Criteria • Bug jail

  36. Debt kills 4

  37. We were not serious about upgrade

  38. Upgrade, upgrade, upgrade! 3

  39. Powerful but Simple … What?

  40. Powerful Powerful and Simple

More Related