Microsoft Global Development Platform Team’s Journey from Agile to DevOps

On November 13, 2013 Microsoft announced Visual Studio 2013 and the commercial launch of Visual Studio Online (VSO). The release triggered a seven‑hour service outage affecting roughly one million users across Europe and the US due to missing telemetry on a critical IP port.

In response, the team shifted focus from feature work to backend reliability, introducing a multi‑scale unit architecture (SU0 and SU1) and adopting canary deployments across Chicago, Amsterdam, and later additional Azure data centers, which reduced online incidents from 43 in November 2013 to just 7 by April 2014.

To support continuous delivery, the team embraced DevOps practices, replacing the traditional Scrum model with feature‑crew teams, implementing feature‑flag controls for gradual exposure, and standardizing three‑week sprint cycles. They also flattened their branching strategy, moving to Git for lightweight feature branches, and integrated pull‑request workflows with quality gates.

Experiments were run to improve the project‑creation experience in both the IDE and web portals. By exposing new users to streamlined registration flows, the proportion of users creating a team project rose from 3% to 20% in the IDE and from 18% to 30% on the web, with further refinements eventually reaching a 50% conversion rate.

Throughout the transformation, the team emphasized measurement and learning: they tracked service health metrics, performed controlled A/B experiments, and iterated on both process and tooling to achieve a more reliable, scalable, and user‑centric development platform.