https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/ Recent content in Continuous Delivery on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system. https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change. https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery. https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Wed, 07 May 2025 11:46:58 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact. https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements. https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Mon, 04 Aug 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization. https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Mon, 21 Jul 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success. https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Mon, 03 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration. https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates. https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Mon, 10 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Value in software is only realised when products are delivered to users, so frequent releases are essential to validate assumptions, gather feedback, and adapt quickly. Delaying delivery increases costs, risks, and missed opportunities, while research shows that teams releasing often are more successful and resilient. Development managers should prioritise short feedback loops and empower teams to release working software regularly to maximise value and minimise waste. https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Fri, 02 Aug 2024 06:45:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Adopting Agile development practices is not enough if the rest of your organization remains slow and bureaucratic; true agility requires continuous delivery, high product quality, and minimal manual or bureaucratic steps across the entire process. Use the Department of Defense’s six-question test to assess your real agility, and focus on automating testing, streamlining deployment, and building quality in from the start. Regularly review and improve your processes to eliminate bottlenecks and ensure your whole ecosystem supports rapid, reliable delivery. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Thu, 06 Feb 2025 10:20:34 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Azure DevOps transformed from two-year release cycles to 880,000 deployments per year by adopting continuous delivery, shortening feedback loops, and using real-time data to guide decisions. This shift enabled rapid response to customer needs and market changes, helping them stay ahead of competitors. Development managers should focus on frequent, small releases and data-driven improvements to maximise value and agility. https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Wed, 28 May 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline. https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity. https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time. https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Tue, 29 Nov 2011 04:36:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality. https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success. https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ Thu, 23 Jan 2025 06:30:03 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ There are no universal best practices for continuous delivery in complex environments; instead, teams should adopt flexible, situation-specific approaches. Key strategies include audience-based delivery for rapid feedback, testing in production to validate real-world performance, and a commitment to quickly finding and fixing issues. Development managers should focus on continuous improvement and adaptability rather than rigid processes. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability. https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Tue, 14 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Wed, 24 Jul 2013 09:46:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance. https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently. https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Tue, 27 Nov 2012 23:00:35 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Sun, 09 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Git Flow is outdated and causes unnecessary delays and complications for modern software teams. Long-lived branches and complex merges slow down delivery and increase risk. Switch to simpler workflows like GitHub Flow or Release Flow to speed up development and focus on delivering value. https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/ Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements.