<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Deployment Frequency on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/</link>
		<description>Recent content in Deployment Frequency on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stop Hiding Behind Complexity and Start Delivering Continuously</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</link>
				<pubDate>Mon, 24 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery</title>
				<link>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/</link>
				<pubDate>Wed, 07 May 2025 11:46:58 +0000</pubDate>
				<guid>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/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Testing in Production Maximises Quality and Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</link>
				<pubDate>Thu, 13 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Delivery is the only Measure of Progress in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</link>
				<pubDate>Mon, 03 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Do More Staging Environments Really Reduce Deployment Risk</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</link>
				<pubDate>Wed, 26 Feb 2025 16:30:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Every delay increases the risk of failure</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</link>
				<pubDate>Mon, 10 Feb 2025 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Stop Promoting Branches</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/</link>
				<pubDate>Thu, 06 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Mastering Site Reliability: Insights from Azure DevOps on Building a Resilient Live Site Culture</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</link>
				<pubDate>Thu, 04 Jun 2020 02:05:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/</guid>
				<description>The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust.</description>
			</item>
			<item>
				<title>Without Delivery, There Is No Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/</link>
				<pubDate>Mon, 10 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</link>
				<pubDate>Mon, 11 Aug 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/</link>
				<pubDate>Thu, 06 Feb 2025 10:20:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</link>
				<pubDate>Wed, 22 Jan 2025 14:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>The Sprint is a container for Planning and not necessarily for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</link>
				<pubDate>Tue, 29 Nov 2011 04:36:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/</guid>
				<description>Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality.</description>
			</item>
			<item>
				<title>Unlocking Rapid Delivery: Overcoming Common DevOps Challenges for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</link>
				<pubDate>Fri, 21 Apr 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/</guid>
				<description>Many teams struggle to deliver products quickly due to slow feedback loops, limited automation, and resistance to change. Key improvements include automating processes, engaging compliance teams early to challenge assumptions, and fostering a culture open to experimentation. Development managers should review their delivery pipelines for bottlenecks and actively involve stakeholders to enable faster, more agile releases.</description>
			</item>
			<item>
				<title>let-us do the maths</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/</link>
				<pubDate>Wed, 30 Apr 2025 15:30:52 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</link>
				<pubDate>Mon, 16 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</guid>
				<description>DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues.</description>
			</item>
			<item>
				<title>Deploying Windows OS Directly to Production: Then vs Now</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</link>
				<pubDate>Sat, 22 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Branch promotion is a relic of slow, manual software delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</link>
				<pubDate>Sat, 08 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Frequent releases are not just a technical strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</link>
				<pubDate>Fri, 07 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</guid>
				<description>Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback.</description>
			</item>
			<item>
				<title>Is Your Project Ecosystem Truly Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</link>
				<pubDate>Wed, 31 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</link>
				<pubDate>Tue, 14 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Unlocking Code Quality: The Transformative Power of Frequent Deployments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</link>
				<pubDate>Mon, 13 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Building a release pipeline with Release Management with Visual Studio 2013</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</link>
				<pubDate>Tue, 18 Feb 2014 16:30:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</guid>
				<description>Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices.</description>
			</item>
			<item>
				<title>If software is not delivered, it is not valuable</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</link>
				<pubDate>Sat, 01 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Staging Environments Do Not Prevent Production Failures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</link>
				<pubDate>Fri, 28 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Every unreleased feature is a cost</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</link>
				<pubDate>Wed, 05 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/</guid>
				<description>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&amp;rsquo;s efforts translate into actual value.</description>
			</item>
			<item>
				<title>Live Site Culture &amp; Site Reliability Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</link>
				<pubDate>Wed, 17 Jun 2020 13:23:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/</guid>
				<description>To stay competitive in a fast-changing market, teams must adopt DevOps and continuous delivery, shifting from infrequent releases to deploying updates daily. This requires faster feedback, shared responsibility for quality and operations, and new ways of working, as shown by Microsoft&amp;rsquo;s Azure DevOps team. Development managers should consider evolving their team structures and practices to support rapid, customer-focused delivery.</description>
			</item>
			<item>
				<title>Release Management with Team Foundation Server 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</link>
				<pubDate>Wed, 24 Apr 2013 17:38:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/</guid>
				<description>Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality.</description>
			</item>
			<item>
				<title>Unlocking the True Power of Continuous Delivery: How Automation Transforms Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</link>
				<pubDate>Fri, 06 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Continuous value delivery with modern business applications</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</link>
				<pubDate>Tue, 27 Nov 2012 23:00:35 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/</guid>
				<description>Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates.</description>
			</item>
			<item>
				<title>Unlocking Continuous Delivery: How Feature Flags Transform Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</link>
				<pubDate>Thu, 16 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Unlocking the Future of Software Development: Why Automation is Your Key to Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</link>
				<pubDate>Wed, 15 Jan 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/</guid>
				<description>Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability.</description>
			</item>
			<item>
				<title>Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 06:00:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-unrealised-value-the-key-to-elevating-your-product-development-strategy/</guid>
				<description>Unrealised value, or the features your users need but you have not built or identified yet, is often overlooked but crucial for product success. To unlock this value, focus on understanding your users, validate assumptions with small experiments before full development, and increase deployment frequency to speed up feedback and learning. Make it a priority to continuously learn from your market and adapt your product strategy to stay relevant and maximise impact.</description>
			</item>
			<item>
				<title>Git Flow should have died years ago</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/</link>
				<pubDate>Sun, 09 Feb 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Azure Pipelines</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-pipelines/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-pipelines/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Deployment Frequency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Frequent Releases</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/</guid>
				<description>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.</description>
			</item>
	</channel>
</rss>
