But we’re not done – we still have a lot to learn.” ![]() We’ve got to where we are now over a long time, and it’s been a very iterative process. DevOps brings Product First Mindset and Infrastructure as a Flexible Resource into play. Customer focussed, Team Autonomy and Shifting Left are basically second decade agile. But here are lessons that we’ve learned so far. We’re a long way on the journey, and still have a lot to learn. Here is Satya’s quote:”Īfter a three-hour-long conversation with executives, the engineering lead concluded, “Now Microsoft Windows, Office, Bing and many other Microsoft properties are built using a consistent set of tools that we call “One Engineering System” or 1ES. The engineering lead continued, “There was a strategic decision made by Satya and leadership that enabled aligned autonomy. Under Satya, we’ve acknowledged the need for modern DevOps practices and tools for all Microsoft products and services.” Those individual teams had large ongoing investments in these different tools and processes which was frankly costly and burdensome. ![]() Different teams used to have different tools and different processes. “The definition of Microsoft’s DevOps may seem obvious, but this journey actually includes many different products and teams at Microsoft with their own challenges, struggles and histories. We were sitting with a group of CxOs from Germany at the Redmond Executive Briefing Center in February 2019, an Azure engineering lead started to explain the history of our own DevOps transformation. To having deployment to production 82K times a day in 2019, ![]() “From taking once a year to release a packaged software in 2015,
0 Comments
Leave a Reply. |