1 / 44

Agile Transformation How we’ve changed the way we run our business

Agile Transformation How we’ve changed the way we run our business. Buck Hodges Director of Development, VS Cloud Services. The Journey. Visual Studio 2010. Visual Studio 2012. Visual Studio 2013. Visual Studio 2008. Visual Studio. 2008. 2009. 2010. 2011. 2012. 2013. 2014.

kosey
Télécharger la présentation

Agile Transformation How we’ve changed the way we run our business

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. Agile TransformationHow we’ve changed the way we run our business Buck Hodges Director of Development, VS Cloud Services

  2. The Journey Visual Studio 2010 Visual Studio 2012 Visual Studio 2013 Visual Studio 2008 Visual Studio 2008 2009 2010 2011 2012 2013 2014

  3. The Journey Public Preview June 2012 Limited Preview Sept 2011 Released! Oct 2012 Visual Studio 2010 Visual Studio 2013 Visual Studio 2012 Visual Studio 2008 Team Foundation Service Visual Studio 2008 2009 2010 2011 2012 2013 2014

  4. Why change in the first place?

  5. “Firms today experience a much higher velocity of business change. Market opportunities appear or dissolve in months or weeks instead of years.“ Diego Lo Giudice and Dave West, Forrester February 2011 Transforming Application Delivery

  6. We needed… A process with a more rapid delivery cadence A process that enabled us to react to feedback A process that enabled us to plan & learn A process that enabled us to stay connected A process that emphasized continuous quality A process that let us measure success

  7. First, let’s talk about roles & teams…

  8. Our Roles Program Manager – Responsible to ensure we’re building the right thing. Development – Responsible to ensure we’re building products that are fast, reliable, and well engineered. QA – Responsible to ensure we’re building high quality products that meet customers needs.

  9. Organization Chart Program Management Development Testing

  10. Teams Program Management Development Testing

  11. Teams Version Control • Cross-discipline • 8-12 people • Led by their triad • Intact for 12-18 months • Autonomous backlog

  12. Team Rooms

  13. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  14. Before Planning M1 M2 2 years

  15. Before Beta RTM Code Test & Stabilize Code Test & Stabilize

  16. After 3 weeks 2 years

  17. 3 Week Sprints Deployment Sprint Planning Done! Week 1 Week 1 Week 1 Week 2 Week 2 Week 2 Week 3 Week 3 Week 3 Sprint 56 Sprint 58 Sprint 57

  18. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  19. Feedback - Before ? ? Code Test & Stabilize Code Test & Stabilize Planning Beta RTM

  20. Feedback - After ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

  21. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  22. The Basics Sprint 3-week sprints Season 6 month season Vision 18 month vision 3 6 18

  23. Planning & Learning - Before Planning M1 M2

  24. Planning & Learning - After 6 month plan 18 month vision Planning Spring Fall Spring Fall

  25. Planning & Learning - After 6 month plan 18 month vision Planning Spring Fall Spring Fall

  26. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  27. Staying connected Chat Chat Chat Chat Chat Chat Every 3 sprints we sit down with the team for a “chat”

  28. Team “Chats” Version Control • What’s next on your backlog? • How are you doing with regards to debt? • Any issues?

  29. Team “Chats”

  30. Team “Chats”

  31. Sprint Mails The sprint plan What we accomplished Week 1 Week 1 Week 1 Week 2 Week 2 Week 2 Week 3 Week 3 Week 3 Sprint 56 Sprint 58 Sprint 57

  32. Sprint Mails

  33. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  34. Quality - Before • Multi-year cycles • Milestones and stabilizations • Debt

  35. Quality- Before Code Complete Code Test & Stabilize Code Test & Stabilize Planning Beta RTM

  36. Quality- After

  37. Managing Quality • Bug cap • Setup & upgrade – every sprint • Feature flags – separate engineering and disclosure

  38. Rolling Tests

  39. The service and the box • Same code base used for both • Adapted to the cloud • Work in a single branch • Gated checkin only builds • Rolling test system, including upgrade tests • Disruptive changes integrated at the beginning of a sprint • Merge to production branch, quarterly update CTPs

  40. Agenda Rapid cadence Reacting to feedback Planning & learning Staying connected Continuous quality Measuring success

  41. Build, Measure, Learn Build Learn Measure We had this… 30% … we decided we could do better, and made a few changes

  42. Build, Measure, Learn Build Measure So we did this… 50% +20% increase

  43. Summary We’ve changed how we run our business It’s helping us improve the product We’re using our own tools

  44. Thank you!

More Related