<p><span style="font-size: 12pt;">Today, many customers expect to be met with fast releases, improvements and feedback response. Just as <a href="http://solidify.se/6-best-devops-companies/">Facebook and Amazon continuously roll out updates</a>, modern organizations need efficient release management to better meet expectations and demands. </span></p> <p><span style="font-size: 12pt;"><em>Release Management </em>is a discipline within software development that takes care of composition, packeting and installatio of software and makes it available for the product&#8217;s end users. A common misconcenption is that release management is something to look at in the end of the development cycle. It&#8217;s actually the opposite &#8211; release management should be well integrated in the entire development process in order for the project to work as well as it can.</span></p> <h2><strong>Release management and feedback response</strong></h2> <p><span style="font-size: 12pt;">As a result of an <a href="http://solidify.se/increase-release-frequency/">increased need for customer demand handling</a>, development tems need to organize suitably. The most common of these ways of organizing is agile and lean. A central part of lean and agile is iterative and incremental development of products, something that challenges traditional development in the sense that the product is being delivered considerably more often. Therefore, the product needs to be deployed, installed and tested more continuously and more often. In order to manage both more and faster deliveries, you need an efficient release management process.</span></p> <p><span style="font-size: 12pt;">The goal of better release management is to reduce the time from change decision to user availability. As a result, a well implemented release process can cut lead times from days to minutes using well defined actions and a big amount of automation.</span></p> <p><span style="font-size: 12pt;">A successful release management strategy includes:</span></p> <ul> <li><span style="font-size: 12pt;">Visibility, transparency and participation &#8211; the more every team member can see and understand, the better the process will work.</span></li> <li><span style="font-size: 12pt;">A repeatable process, a <em>pipeline</em>, that defines the different steps that needs to happen to go from checked-in code to released product.</span></li> <li><span style="font-size: 12pt;">Clear feedback for quick error measures in the process.</span></li> <li><span style="font-size: 12pt;">Tools enabling the team to release any version of the product to any environment at any time.</span></li> <li><span style="font-size: 12pt;">High amount of automation to cut time requirement and human error.</span></li> </ul> <h2><strong>Microsoft tools for release management</strong></h2> <p><span style="font-size: 12pt;">In order to practically implement a release management process you need a suitable tool. If you&#8217;re working with Microsoft tools today there are integrated solutions for release management included in both Team Foundation Server (TFS) 2013 and up as well as in Visual Studio Team Services (VSTS). In conclusion, these solutions include:</span></p> <ul> <li><span style="font-size: 12pt;">Integration with TFS and VSTS which enables various automation possibilities</span></li> <li><span style="font-size: 12pt;">Clear visual release flow definitions</span></li> <li><span style="font-size: 12pt;">Good access controls where you can control who is authorized to do what in the release process</span></li> <li><span style="font-size: 12pt;">Transparency &#8211; it&#8217;s easy to see what the process looks like and where a release is at each stage</span></li> <li><span style="font-size: 12pt;">Feedback, both directly in the tool or as mails directed to people in charge</span></li> </ul> <p><span style="font-size: 12pt;">All of these make TFS and VSTS great tools for release management.</span></p> <p><span style="font-size: 12pt;"><em>Have you an integrated RM strategy? Have you encountered any issues you want to discuss? Let us know below!</em></span></p>