Allow me to walk you through memory lane of Bing's agility transformation which started in 2012 and still continues to evolve on a daily basis.

Microsoft’s Bing is on a long-term journey to build the largest, most relevant, best performing search engine in the world. This one goal presents monumental software engineering challenges that demand the most from its development platform. So while Bing has been steadily climbing into the second largest search engine in the world, we have also been innovating in how we build, deploy, and manage our software platform. What we’ve discovered: rapid innovations in user-facing features and performance are only possible through innovation in the software platform and the developer experience. I hope to convey the challenges we faced trying to move over hundreds of engineers from doing something they were very comfortable with to a way that seemed not only infeasible but downright insane. The culmination of the platform and developer experiences is referred to as Continuous Delivery (or simply “Agility”), and when we began to make the leap to Continuous Delivery we not only changed the way our developers write code – we fundamentally altered the way our business operates. Regardless of organizational size, we believe this is a journey worth taking.


Outline/Structure of the Case Study

  • Introduction to Bing stack
  • Agility Philosophies at Bing
  • Agile Developer Support at Bing
  • Scaling up Agility
  • Beyond Agility and Key Learnings

Learning Outcome

A big monolith or a micro-service can both be agile and have continuous delivery.

Target Audience

Developers, DevOps tools owners, Management

Prerequisites for Attendees

Be open to change



schedule Submitted 2 years ago

Public Feedback