{"id":1034,"date":"2016-04-04T00:00:51","date_gmt":"2016-04-04T00:00:51","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=1034"},"modified":"2020-02-14T07:47:18","modified_gmt":"2020-02-14T14:47:18","slug":"how-microsoft-does-devops","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/how-microsoft-does-devops\/","title":{"rendered":"How Microsoft does DevOps"},"content":{"rendered":"

In this blog post, Application Development Manager, Justin Wendlandt<\/strong>, shares a bit about DevOps strategy, why it\u2019s important, and common areas Premier Developer can help your teams.<\/p>\n

\n

 <\/p>\n

One of the core focuses at every enterprise or technology organization is how to deliver more business value to their sponsors. It may be phrased differently depending on who you ask. Some statements I hear are, \u201cwe need to do more with less\u201d, \u201crelease features more often\u201d or my favorite, \u201cbuild software faster\u201d.<\/p>\n

In today\u2019s cloud-first, mobile-first world technology companies are stuck between features that their business sponsors or customers want and staying current on the new technologies that are changing to support those features. In order to accommodate those moving targets on both sides, your team needs to move faster and be more agile to the changes. So what changes does your organization need to make in terms of People, Processes and Technology in order to build software faster?<\/p>\n

At Microsoft, we are heavily focused on the topic of DevOps. It\u2019s that grey area between what a developer does day-to-day and what happens inside an operations organization on a daily basis. Our internal product groups at Microsoft are sharing our story in terms of this transformation to adopt a strong relationship between developers and operations, find out more here – http:\/\/stories.visualstudio.com\/devops\/<\/a>.<\/p>\n

The reason why DevOps is a focus for most companies today is because of the complexity in orchestrating tasks between developers, infrastructure engineers and operations teams. That pain used to be absorbed by organizations \u201cthrowing it over the wall\u201d and making it someone else\u2019s problem. In a healthy DevOps organization, it becomes everyone\u2019s problem.<\/p>\n

\"DevOps<\/a><\/p>\n

@DonovanBrown<\/a>\u2019s view of why DevOps is popular right now: http:\/\/bit.ly\/DevOpsHurts<\/a><\/p>\n

DevOps should be viewed in terms of closing the feedback loop between product owners and technology rather than doing more with less, or building software faster. Shortening the time it takes to go from a user story, to a release to production. By doing this effectively, your team can inherently gain in terms of quality of delivery, speed to market and hopefully return on investment. Below we can see how complex this all is by the complexity by People, Process and Technology.<\/p>\n

\"\"<\/p>\n

Another good perspective on DevOps comes from @jezhumble<\/a> from Chef during this last year\u2019s ChefConf<\/a>. Jez Humble touches on changes needed to implement enterprise developer and operations relationships. The keynote touched on several aspects of DevOps such as \u201cThe Alignment Trap\u201d, \u201cWater-Scrum-Fall\u201d and \u201cEmergency Change Process vs. Normal Change Process\u201d.<\/p>\n