https://engineering-leadership.hinshelwood.com/tags/release-management/ Recent content in Release Management on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness. https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release. https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/ Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster. https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Mon, 11 Aug 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible. https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability. https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency. https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead. https://engineering-leadership.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/ Sat, 18 Sep 2021 13:32:34 +0000 https://engineering-leadership.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/ The workshop introduced key concepts of Sprint Reviews using interactive tools and received very positive participant feedback, despite technical audio issues during the live stream. The main learning was to check both music and voice before sessions to avoid similar problems, and future events will use a new community platform for easier access. Development managers should ensure thorough technical checks before virtual workshops and consider leveraging interactive formats for better engagement. https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Using separate branches for each environment increases complexity and slows feedback, making it harder to deliver value quickly. Teams should use branches to manage work in progress and rely on feature flags and progressive rollouts to control what users see. Review your current branching approach and consider simplifying it to speed up delivery and reduce risk. https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/ Slow release cycles mean customer needs go unmet and competitors gain an edge. Microsoft’s shift from a two-year delivery cycle to three-week sprints allowed them to deliver features in days, improving customer satisfaction and competitiveness. Accelerate your delivery process to stay relevant and meet customer demands faster. https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes. https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness. https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery. https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile. https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Tue, 18 Feb 2014 16:30:59 +0000 https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices. https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Sat, 01 Mar 2025 16:30:03 +0000 https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Undelivered software provides no value, and long development cycles increase risk, cost, and missed opportunities. Research shows that teams releasing software frequently are more successful and efficient. To maximize value and learning, prioritize frequent delivery to users. https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems. https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team’s efforts translate into actual value. https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality. https://engineering-leadership.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Tue, 27 Nov 2012 23:00:35 +0000 https://engineering-leadership.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates. https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs. https://engineering-leadership.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ Wed, 15 Oct 2014 14:49:05 +0000 https://engineering-leadership.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ The speaker will present a demo-heavy session at NDC London to showcase major improvements in Team Foundation Server and Visual Studio Online since 2012, targeting developers who previously found TFS lacking. Key insights include end-to-end demonstrations of new features for agile project management, coding, testing, release, and monitoring, with scenarios covering both new features and bug fixes. Development managers should consider revisiting TFS/VSO for .NET projects and can provide feedback on which features or scenarios they want prioritized in the session. https://engineering-leadership.hinshelwood.com/articles/the-high-of-release/ Sat, 05 Dec 2015 14:49:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-high-of-release/ Microsoft’s new web-based Release Management tools let teams build flexible, integrated release pipelines in VSTS or TFS without being locked into specific deployment tools. The focus is on orchestration and integration, allowing you to use your preferred technologies like Chef, Puppet, Docker, or PowerShell. These tools are now in public preview, so consider evaluating them to streamline your release process and support cloud or on-premises deployments. https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles. https://engineering-leadership.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/ Wed, 14 Apr 2010 20:11:36 +0000 https://engineering-leadership.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/ Explains an effective branching strategy for Scrum teams, covering best practices, common pitfalls, and step-by-step guidance for managing code, releases, and bug fixes. https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction. https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines. https://engineering-leadership.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/ Thu, 04 Dec 2014 11:30:00 +0000 https://engineering-leadership.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/ Setting up a standard release management environment in Azure is straightforward, cost-effective, and closely mirrors on-premises setups by using VMs, resource groups, and Application Insights for analytics. Using the old Azure portal gives better control over naming and resource organization, while Azure’s flexibility allows quick scaling and isolation for multiple environments. Development managers should consider scripting environment setup for repeatability and use Application Insights to track application usage and feedback. https://engineering-leadership.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Mon, 27 Jan 2014 11:29:14 +0000 https://engineering-leadership.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Learn how to automate test execution during deployments using Release Management for Visual Studio 2013, including setup steps, environment tips, and common issues. https://engineering-leadership.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/ Tue, 19 Apr 2011 17:57:41 +0000 https://engineering-leadership.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/ Step-by-step guide to upgrading Team Foundation Server 2008 to 2010, including in-place upgrade, build server update, and migrating to a new domain with key troubleshooting tips. https://engineering-leadership.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/ Mon, 26 Jan 2015 14:13:11 +0000 https://engineering-leadership.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/ Visual Studio Online offers enterprises always up-to-date tools, integrated build and release management, global access, and reduced infrastructure overhead, enabling greater agility and faster feature delivery. While some customisation and reporting features from TFS are still missing, Microsoft is actively addressing these gaps, and most teams can work around them using tags and new reporting options. Development managers should consider VSO to streamline operations, lower support costs, and keep pace with evolving business needs, provided they are ready for the cultural shift to cloud-based development. https://engineering-leadership.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/ Sat, 30 Jun 2012 02:38:01 +0000 https://engineering-leadership.hinshelwood.com/articles/upgrading-tfs-2010-to-tfs-2012-with-vss-migration-and-process-template-consolidation/ Step-by-step guide to upgrading TFS 2010 to TFS 2012, migrating VSS data, consolidating process templates, and resolving common issues during team project integration. https://engineering-leadership.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/ Thu, 03 Apr 2014 19:26:22 +0000 https://engineering-leadership.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/ Covers new features and upgrade steps for Team Foundation Server 2013 Update 2, including improvements in backlog, test, release, and version management. https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements. https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/ Deployment Frequency is a key metric that measures the rate at which software is released into production, playing a vital role in contemporary product development. It originates from the need for organisations to enhance their responsiveness to customer needs by facilitating quicker feedback loops and adjustments. By optimising deployment frequency, teams can not only release features and fixes more frequently but also validate their assumptions and learn from real-world usage promptly. This concept is crucial for cultivating a culture of continuous improvement and innovation, allowing teams to experiment, iterate, and adapt to market changes effectively. A high deployment frequency reflects a mature DevOps practice characterised by automation, collaboration, and efficient processes that enable rapid delivery without sacrificing quality. Additionally, it fosters a sense of accountability and ownership among team members, as they can directly observe the impact of their contributions on end-users. By prioritising deployment frequency, organisations can establish a sustainable delivery rhythm that enhances customer satisfaction and drives long-term business success through consistent value delivery and adaptability. This systemic approach not only promotes resilience and agility but also ensures that teams remain competitive in an ever-evolving digital landscape. https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering-leadership.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/frequent-releases/ Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape. https://engineering-leadership.hinshelwood.com/tags/release-management/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/release-management/ Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty.