2. There is no single way Agile is done at Microsoft This is the Developer Division’s story 3 week sprints Scrum at the team level Emphasis on self-managed teams Top-down and bottom-up Expanding to DevOps

3. 2 years

4. PlanningM1M2

5. PlanningM1M2 Specs ?

6. PlanningM1M2 Specs We knew exactly what to build, and we knew it was right!

7. PlanningM1M2 We had a perfect schedule and knew exactly when it would be ready!

8. CodeTest & StabilizeCodeTest & Stabilize We now had perfect estimates and we understood how it would all come together!

9. CodeTest & StabilizeCodeTest & Stabilize Code Complete We wrote all the code months before we shipped a release.

10. CodeTest & StabilizeCodeTest & Stabilize Stabilize We now just needed to stabilize the code and get it ready to ship to customers

11. A: Very well in the era in which it was born. But… Q: How did it work?

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

13. Roles Organization Teams Cadence Plan Practices Alignment Autonomy Autonomy, Mastery, Purpose http://www.youtube.com/watch?v=u6XAPnuF jJc

14. Sprint 3-week sprints Season 6 month season Vision 18 month vision

15. Program Manager – Responsible to ensure we’re building the right thing. Engineer – Responsible to ensure we’re building products that are fast, reliable, and well engineered.

16. Program ManagementEngineering

17. Program ManagementEngineering

18. Cross discipline 10-12 people Self managing Autonomous backlog Intact for 12-18 months Physical team rooms

19. PMEngineering

20. Yes, we do have some remote individuals. It’s the exception, not the rule. We aim for remote teams, not remote disciplines.

21. 3 weeks

22. Week 1Week 2Week 3 Week 1Week 2Week 3 Week 1Week 2Week 3 Sprint 69 Sprint 68 Sprint 70 Deployment Sprint Planning Done!

23. What we accomplished Week 1Week 2Week 3 Week 1Week 2Week 3 Week 1Week 2Week 3 Sprint 69 Sprint 68 Sprint 70 The sprint plan

24. Plan Accomplished

25. CodeTest & StabilizeCodeTest & Stabilize Code Complete

27. Week 1Week 2Week 3 Sprint 69

28. Things we don’t watch Team burndown Team velocity Original estimate Completed hours Team capacity # of bugs found Things we watch # of bugs Unit test coverage Rolling build quality Dev cycle time Live site issues

30. Sprint 3-week sprints Season 6 month season Vision 18 month vision

31. SpringFallSpringFall

32. 3 weeks SpringFallSpringFall

33. 3 weeks SpringFallSpringFall

34. 3 sprints

35. 1. What’s next on your backlog? 2. What’s your debt situation? 3. Any issues?

38. Experience Review

39. Storyboard of what you’re going to build High level execution plan Talk about sprints, not hours Feedback, feedback, feedback

40. Monthly view of service availability Health check of operational metrics Talk about what happened, how, and what you’re doing about it

42. Sprint 3-week sprints Season 6 month season Vision 18 month vision

43. SpringFallSpringFall 6 month plan Experience Reviews 18 month vision Scenario Review

44. SpringFallSpringFall Done! What did we learn over the last 6 months? What did customers tells us? What did the telemetry tell us? What changed in the marketplace?

45. SpringFallSpringFall 6 month plan Experience Reviews 18 month vision Scenario Review Done!

47. 1. Less is more 2. Get out of your teams’ way 3. Autonomy, mastery, purpose 4. Plan & learn 5. Have fun

48. http://aka.ms/engineeringstories