<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Shift Left Strategy on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/</link>
		<description>Recent content in Shift Left Strategy 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.hinshelwood.com/tags/shift-left-strategy/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/</guid>
				<description>The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives.</description>
			</item>
			<item>
				<title>Engineering can fix technical debt, but leadership has to invest in it</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</link>
				<pubDate>Mon, 03 Mar 2025 16:30:35 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Stop Testing Quality In: How Shifting Left Builds Better Software, Faster</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</link>
				<pubDate>Mon, 18 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</link>
				<pubDate>Wed, 04 Jun 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/</guid>
				<description>Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software.</description>
			</item>
			<item>
				<title>NKD Agility: Your partner in developing engineering excellence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/</link>
				<pubDate>Sat, 23 Nov 2024 07:00:12 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/</guid>
				<description>NKD Agility helps organizations build engineering excellence and technical leadership by shifting key practices like testing, security, and architecture closer to development teams and actively addressing technical debt. This approach reduces the high costs of poor-quality products and supports a culture of quality and value creation. Development managers looking to improve software quality and team capability can partner with NKD Agility for modern engineering practices and support.</description>
			</item>
			<item>
				<title>Code Reviews for Quality Assurance</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/code-reviews-for-quality-assurance/</link>
				<pubDate>Wed, 27 Nov 2024 06:00:25 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/code-reviews-for-quality-assurance/</guid>
				<description>Automating code validation before pull requests speeds up delivery, catches defects earlier, and ensures consistent quality, allowing manual reviews to focus on architecture and business alignment instead of minor issues. Development managers should invest in automated testing, static analysis, and security checks, making pull requests mandatory and using manual reviews strategically. This approach reduces bottlenecks and helps teams deliver high-quality software faster.</description>
			</item>
			<item>
				<title>Security by Design Building Secure Software</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/security-by-design-building-secure-software/</link>
				<pubDate>Tue, 26 Nov 2024 13:35:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/security-by-design-building-secure-software/</guid>
				<description>Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation.</description>
			</item>
			<item>
				<title>You are doing it wrong if you are not using test first</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</link>
				<pubDate>Mon, 07 Dec 2020 12:00:58 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/</guid>
				<description>Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices.</description>
			</item>
			<item>
				<title>Quality enablement with Visual Studio 2012</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</link>
				<pubDate>Wed, 15 May 2013 03:13:20 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</guid>
				<description>Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction.</description>
			</item>
			<item>
				<title>Unlocking the Superpower of Software Development: How Shifting Left Transforms Quality Assurance</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</link>
				<pubDate>Fri, 22 Nov 2024 14:04:14 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/</guid>
				<description>Shifting quality assurance to the start of the development process leads to higher product quality, faster delivery, and lower costs by catching issues early and fostering better collaboration. Teams that adopt this approach see improved morale and stakeholder confidence. To get started, educate your team, involve QA early, encourage collaboration, use automation, and focus on continuous improvement.</description>
			</item>
			<item>
				<title>Test First Development</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/test-first-development/</link>
				<pubDate>Tue, 25 Mar 2025 07:40:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/test-first-development/</guid>
				<description>Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts.</description>
			</item>
			<item>
				<title>Shift Left Strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/</link>
				<pubDate>Mon, 17 Mar 2025 14:46:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/</guid>
				<description>The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development.</description>
			</item>
			<item>
				<title>Automated Testing</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/automated-testing/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/automated-testing/</guid>
				<description>Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment.</description>
			</item>
	</channel>
</rss>
