Agile Evolution - An Enterprise Transformation That Shows That You Can Too

This talk examines how Microsoft's Azure DevOps Services moved from three-year waterfall delivery to three-week iterations and continuous delivery. It draws lessons from the team's successes and failures, including customer feedback, automation, technical-debt repayment, and production practices.

Syllabus

Introduction
DevOps
What is DevOps
Epic failures
Poor quality products
How Microsoft became agile
Microsofts journey into DevOps
Trade off features for productivity
Azure stats
Change the story
Key habits
Listening to customers
Customer feedback
Visual Studio
Measure important KPIs
Iterating over pain
Twoyear cycles
Safety net
Stabilization phase
Technical debt
Threeweek sprints
Paying back technical debt
Technical debt is risk
Release vs Sprint
Feature Flags
What could go wrong
Microsofts policy
Production mindset
Live site mindset
Transparency
Automation
Automate everything
Traditional model
Azure Devops
Big environments
Speed vs control
Alignment vs autonomy
Autonomy mastery and purpose
Team structure
Team size
Team forming exercises
Proportional representation
consort cadence
focus
alignment
stay in sync
Questions
Quality
Test plans
Test matrix
Cloud first
Incremental rollout
Learn from failure
One sprint a time
Progress always follows the J curve
What changed for the Azure DevOps team
One step at a time