<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Value Delivery on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-delivery/</link>
		<description>Recent content in Value Delivery 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/value-delivery/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stop Building Silos. Start Building Systems</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</link>
				<pubDate>Mon, 07 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Don’t Manage Dependencies, Remove Them</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</link>
				<pubDate>Mon, 29 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/</guid>
				<description>Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy.</description>
			</item>
			<item>
				<title>Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</link>
				<pubDate>Mon, 15 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/</guid>
				<description>The phrase “flow of value” is often misused in software development, as value is only confirmed when customers validate it, not just when work is completed. Teams should focus on validating outcomes quickly, breaking work into small, testable increments, and using data to cut features that do not deliver real value. To truly optimise value, ensure every item has a clear hypothesis, measure time to feedback, and prioritise learning over simply moving work through the system.</description>
			</item>
			<item>
				<title>Is Agile Really Just a Mindset?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</link>
				<pubDate>Mon, 11 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Rethinking Capacity Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/</link>
				<pubDate>Mon, 21 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/</guid>
				<description>Capacity planning should focus on optimising system flow and predictability, not tracking individual hours or task assignments. Shifting from micromanagement to managing work as a system at portfolio, category, and team levels helps prevent overload, improves value delivery, and enables reliable forecasting. Development managers should prioritise system-level metrics, enforce work-in-progress limits, and empower teams to pull well-prepared work, creating sustainable and predictable delivery.</description>
			</item>
			<item>
				<title>Why Topic Branches Drive High-Quality Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</link>
				<pubDate>Mon, 14 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</link>
				<pubDate>Wed, 14 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/</guid>
				<description>When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility.</description>
			</item>
			<item>
				<title>Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</link>
				<pubDate>Mon, 15 Sep 2025 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/</guid>
				<description>Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies.</description>
			</item>
			<item>
				<title>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</link>
				<pubDate>Mon, 22 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/</guid>
				<description>Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control.</description>
			</item>
			<item>
				<title>The Definition of Done is a Commitment to Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</link>
				<pubDate>Mon, 28 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/</guid>
				<description>A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk.</description>
			</item>
			<item>
				<title>Your Evolving Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/</link>
				<pubDate>Mon, 31 Mar 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.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>Velocity isn’t how many story points a team burns down</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</link>
				<pubDate>Mon, 10 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/</guid>
				<description>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.</description>
			</item>
			<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>Should You Use One Project to Rule Them All in Azure DevOps?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</link>
				<pubDate>Mon, 25 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/</guid>
				<description>Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and 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>Release planning and predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</link>
				<pubDate>Wed, 21 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</guid>
				<description>Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence.</description>
			</item>
			<item>
				<title>Engineering can fix technical debt, but leadership has to invest in it</title>
				<link>https://engineering-leadership-preview.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-preview.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>Great Scrum Masters Need Technical, Business, and Organisational Mastery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</link>
				<pubDate>Mon, 24 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/</guid>
				<description>Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team&amp;rsquo;s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery.</description>
			</item>
			<item>
				<title>Definition of Done - Objective vs Subjective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</link>
				<pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/</guid>
				<description>The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs.</description>
			</item>
			<item>
				<title>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Are We Still Pretending Coding Was the Bottleneck?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</link>
				<pubDate>Mon, 01 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</guid>
				<description>AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output.</description>
			</item>
			<item>
				<title>Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</link>
				<pubDate>Mon, 21 Jul 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</link>
				<pubDate>Wed, 16 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/</guid>
				<description>Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage.</description>
			</item>
			<item>
				<title>Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</link>
				<pubDate>Wed, 02 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/</guid>
				<description>Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality.</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>The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</link>
				<pubDate>Wed, 21 Aug 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</guid>
				<description>DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results.</description>
			</item>
			<item>
				<title>Stop Testing Quality In: How Shifting Left Builds Better Software, Faster</title>
				<link>https://engineering-leadership-preview.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-preview.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>Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</link>
				<pubDate>Wed, 18 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/</guid>
				<description>A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility.</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>The Power of Technical Excellence in Agile Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</link>
				<pubDate>Thu, 27 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</guid>
				<description>Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive.</description>
			</item>
			<item>
				<title>Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</link>
				<pubDate>Wed, 09 Jul 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/</guid>
				<description>Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success.</description>
			</item>
			<item>
				<title>Building a culture of Quality</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/</link>
				<pubDate>Fri, 22 Nov 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/</guid>
				<description>A culture of quality cannot be built by one person; it requires everyone in the organization to demonstrate and model technical excellence and leadership. Focusing only on revenue, as seen in Boeing&amp;rsquo;s decline, undermines quality and can lead to dangerous outcomes, while a strong culture of quality leads to better, safer products. Development managers should prioritize building and reinforcing engineering excellence and technical leadership across teams, using frameworks and tools as enablers rather than solutions.</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>How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</link>
				<pubDate>Wed, 25 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/</guid>
				<description>You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready.</description>
			</item>
			<item>
				<title>Scrum doesn’t stop you from optimising flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</link>
				<pubDate>Sun, 25 May 2025 15:30:23 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>A better way than staggered iterations for delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</link>
				<pubDate>Thu, 10 Dec 2020 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/</guid>
				<description>Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality.</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>Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation</title>
				<link>https://engineering-leadership-preview.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-preview.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>Mastering Sustainable Scaling: Overcoming Product Development Challenges with Naked Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</link>
				<pubDate>Fri, 28 Feb 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/</guid>
				<description>Scaling product development is complex and requires more than just adding people; it demands clear priorities, strong leadership, and systems designed for growth. Naked Agility helps organisations address common scaling challenges like alignment, technical debt, and slow feedback by eliminating bottlenecks, using data-driven decisions, and tailoring strategies to each team&amp;rsquo;s needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth.</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>The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</link>
				<pubDate>Tue, 19 Nov 2024 09:58:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</guid>
				<description>Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</link>
				<pubDate>Mon, 03 Mar 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/</guid>
				<description>Measuring individual cycle time in Kanban misleads teams by focusing on personal speed instead of system flow, which ignores real bottlenecks and encourages counterproductive behaviors. To improve delivery, track system-wide metrics like lead time, work in progress, process cycle efficiency, and blockers, then address constraints at the process level. Development managers should shift measurement and improvement efforts from individuals to the overall workflow to achieve better outcomes.</description>
			</item>
			<item>
				<title>Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</link>
				<pubDate>Wed, 11 Jun 2025 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/</guid>
				<description>Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn.</description>
			</item>
			<item>
				<title>Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</link>
				<pubDate>Wed, 28 May 2025 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Why Organisations Believe Their Software Is Too Complex for CD</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</link>
				<pubDate>Mon, 24 Feb 2025 10:51:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Rethinking Dev-Test-Staging-Production Pipelines for Safety</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</link>
				<pubDate>Fri, 21 Feb 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</guid>
				<description>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.</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>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</link>
				<pubDate>Sat, 15 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</guid>
				<description>Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals.</description>
			</item>
			<item>
				<title>Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</link>
				<pubDate>Mon, 25 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</guid>
				<description>Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible.</description>
			</item>
			<item>
				<title>Why Tracking Individual Cycle Time Distorts Team Behaviour</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</link>
				<pubDate>Wed, 12 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</guid>
				<description>Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead.</description>
			</item>
			<item>
				<title>The Scrum Master is accountable for Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</link>
				<pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/</guid>
				<description>The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success.</description>
			</item>
			<item>
				<title>Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</link>
				<pubDate>Tue, 27 Jun 2023 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/</guid>
				<description>In the first 90 days, a Scrum team can move from limited delivery to continuous delivery by focusing on frequent releases, clarifying business value, integrating user feedback, and empowering team members to take ownership. Success depends on organisational support and team readiness. Managers should prioritise building a delivery culture and enabling the team to sustain progress independently.</description>
			</item>
			<item>
				<title>I do continuous deliver, why should I Sprint?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/</guid>
				<description>Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible.</description>
			</item>
			<item>
				<title>Executives want predictability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</link>
				<pubDate>Mon, 31 Mar 2025 15:30:08 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/</guid>
				<description>If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating &amp;ldquo;Done&amp;rdquo; as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Estimating Better in an Overloaded System Is a Poor Man’s Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</link>
				<pubDate>Mon, 08 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/</guid>
				<description>Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning.</description>
			</item>
			<item>
				<title>Free Workshop 04: Introduction to Sprint Reviews [Review &amp; Retrospective]</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/</link>
				<pubDate>Sat, 18 Sep 2021 13:32:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</link>
				<pubDate>Mon, 08 Jan 2024 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</guid>
				<description>Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting.</description>
			</item>
			<item>
				<title>Deciphering the Enigma of Story Points Across Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</link>
				<pubDate>Thu, 21 Sep 2023 08:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</guid>
				<description>Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes.</description>
			</item>
			<item>
				<title>If every release feels high-risk, you lack a true Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</link>
				<pubDate>Sat, 05 Apr 2025 15:30:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/</guid>
				<description>If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team&amp;rsquo;s process to make releases predictable and low-stress.</description>
			</item>
			<item>
				<title>Special Sprints: Agile Banditry or Risk Management?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</link>
				<pubDate>Thu, 04 Jan 2024 11:09:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/</guid>
				<description>Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk.</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>Why Most Companies Operating Models Fail in Dynamic Markets</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-companies-operating-models-fail-in-dynamic-markets/</link>
				<pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/why-most-companies-operating-models-fail-in-dynamic-markets/</guid>
				<description>Most organisations still use a Predictive Operating Model built for stable, predictable markets, which now creates massive waste, slow decisions, and disengaged teams in today&amp;rsquo;s dynamic environment. An Adaptive Operating Model, built on empiricism, rapid learning, decentralised decision-making, and persistent cross-functional teams, is a better fit because it focuses on outcomes, adaptability, and continuous alignment with customers. The real work is redesigning structures, measures, and leadership, not just adopting new processes.</description>
			</item>
			<item>
				<title>Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/</link>
				<pubDate>Tue, 03 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/</guid>
				<description>To build a high-performing software delivery team, focus on developing both technical and business competence across all members, encouraging everyone to think like product developers rather than just coders. Embrace Agile, DevOps, Lean, and Scrum philosophies, adapt practices as needed, and ensure due diligence before making structural changes. Prioritise collaboration, open communication, and continuous improvement to maximise value delivery and drive business success.</description>
			</item>
			<item>
				<title>The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</link>
				<pubDate>Mon, 17 Feb 2025 16:30:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/</guid>
				<description>Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings.</description>
			</item>
			<item>
				<title>How important is DevOps in continuous delivery of value to customers?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</link>
				<pubDate>Mon, 20 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/</guid>
				<description>DevOps is essential for delivering value to customers because it enables teams to quickly and effectively turn ideas into working software, closely aligning with agile principles. Both DevOps and agile focus on rapid feedback, continuous improvement, and adapting to customer needs, making them deeply interconnected. Development managers should ensure their teams integrate DevOps practices to accelerate delivery, validate value, and reduce risk.</description>
			</item>
			<item>
				<title>Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</link>
				<pubDate>Fri, 17 Apr 2020 18:57:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-agile-transformation-empowering-teams-for-success-in-a-rapidly-changing-landscape/</guid>
				<description>To succeed with Agile transformation, focus on empowering teams through servant leadership, prioritising valuable product outcomes over feature lists, and fostering continuous improvement to manage technical debt. Enable product owners to drive value, build cross-functional teams, and measure results by customer impact rather than activity. Start with small changes to build momentum and consider expert support if needed.</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>Empowering Agile Teams: The Transformative Power of Teaching the &#34;Why&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</link>
				<pubDate>Thu, 27 Apr 2023 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-agile-teams-the-transformative-power-of-teaching-the-why/</guid>
				<description>Helping teams understand the reasons behind Agile practices is key to real engagement and lasting change. When team members grasp the value and purpose of what they do, they collaborate better, adapt more easily, and drive continuous improvement. Development managers should focus on explaining the &amp;ldquo;why&amp;rdquo; behind processes to empower teams and boost performance.</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>Story Points: A Ghost of Agile Past</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</link>
				<pubDate>Fri, 29 Dec 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</guid>
				<description>Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance.</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>The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</link>
				<pubDate>Tue, 22 Oct 2024 07:00:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/</guid>
				<description>Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress.</description>
			</item>
			<item>
				<title>Transforming Enterprises: How DevOps Drives Collaboration and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/</link>
				<pubDate>Tue, 16 Jun 2020 12:16:52 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/</guid>
				<description>DevOps can transform enterprise software teams by fostering collaboration, encouraging continuous improvement, and enabling automation, which together lead to faster delivery and higher quality. Focusing on a customer-centric approach helps teams respond quickly to feedback and market changes. Development managers should prioritize building a culture that supports these principles to drive meaningful organizational change.</description>
			</item>
			<item>
				<title>Too many teams overcomplicate their branching strategies</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</link>
				<pubDate>Thu, 06 Feb 2025 09:38:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Building the wrong thing is worse than fixing a bug</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</link>
				<pubDate>Mon, 14 Apr 2025 15:30:31 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/</guid>
				<description>Most features built by software teams do not deliver value, with 65 percent considered waste. Shortening feedback loops through frequent reviews and real user input helps teams focus on what matters and avoid building the wrong things. Act now to get faster, actionable feedback and prevent wasted time and resources.</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>From Chaos to Clarity: My Journey Through DevOps and the Three Key Challenges to Overcome</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</link>
				<pubDate>Thu, 04 Apr 2024 11:34:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/</guid>
				<description>The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster.</description>
			</item>
			<item>
				<title>The Pitfalls of Routine Agile Questions: Avoiding the Ghosts of Agile Past</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</link>
				<pubDate>Wed, 03 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/</guid>
				<description>Focusing daily meetings on routine status questions leads to disengagement and distracts from delivering real value. Instead, teams should use these meetings to track progress toward sprint goals, manage aging tasks before they become bottlenecks, and adapt ceremonies to support value delivery and continuous improvement. Review your Agile practices and shift the focus from individual updates to team outcomes for better results.</description>
			</item>
			<item>
				<title>Metrics that matter with evidence-based management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</link>
				<pubDate>Tue, 25 Feb 2014 13:29:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/</guid>
				<description>Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement.</description>
			</item>
			<item>
				<title>Quality enablement to achieve predictable delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</link>
				<pubDate>Wed, 24 Jul 2013 09:46:22 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/</guid>
				<description>Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance.</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>Transforming Waste into Value: How to Boost ROI with Agile Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</link>
				<pubDate>Tue, 17 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/</guid>
				<description>Most organisations lose significant value due to waste and lack of focus on engineering excellence, with metrics showing that only a small fraction of development investment results in features customers actually use. Key insights include low innovation rates, poor feature usage, and lagging version adoption, all of which drastically reduce ROI. Development managers should measure and act on innovation and usage metrics, close feedback loops, and focus on delivering value rather than just reducing costs.</description>
			</item>
			<item>
				<title>Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</link>
				<pubDate>Thu, 27 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/</guid>
				<description>If teams do not deliver a usable product at the end of each iteration, trust with stakeholders erodes, technical debt grows, adaptability slows, and expectations become misaligned. This also leads to lower team morale and a lack of feedback, making it hard to improve or stay on track. To avoid these issues, ensure every iteration results in a usable product so you maintain trust, alignment, and the ability to adapt quickly.</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>Maximising Product Value: The Power of Hypothesis-Driven Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</link>
				<pubDate>Wed, 11 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/</guid>
				<description>Focusing on hypothesis-driven engineering helps teams maximise product value by testing ideas with small experiments, measuring outcomes, and quickly adapting based on real customer feedback. The Azure DevOps team’s experience showed that even costly initiatives can provide critical learning, allowing resources to be redirected before larger losses occur. Development managers should encourage rapid experimentation and validation at all levels to ensure investments deliver real value and support agility.</description>
			</item>
			<item>
				<title>You can&#39;t stop the signal! But you can ignore it!</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</link>
				<pubDate>Wed, 17 Apr 2024 14:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/you-can&#39;t-stop-the-signal-but-you-can-ignore-it/</guid>
				<description>Agile and Scrum frameworks highlight problems in team processes, but many organizations ignore these signals due to cultural barriers like fear of repercussions and resistance to change. Simply adopting these frameworks is not enough; their effectiveness depends on a culture that encourages transparency, feedback, and continuous improvement. Development managers should focus on building an environment where raising and addressing issues is supported and valued to fully realize the benefits of Agile and Scrum.</description>
			</item>
			<item>
				<title>Unlocking Value in DevOps: My Role as a Consultant in Driving Change and Overcoming Bottlenecks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</link>
				<pubDate>Tue, 02 May 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/</guid>
				<description>As a DevOps consultant, my main focus is helping teams rethink how they deliver value by identifying and addressing both technical and process bottlenecks, such as slow builds or approval delays. I do this by asking targeted questions and encouraging teams to examine their workflows, which leads to continuous improvement and better customer outcomes. Development managers should regularly review their processes to spot and resolve the biggest sources of delay.</description>
			</item>
			<item>
				<title>Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</link>
				<pubDate>Fri, 28 Apr 2023 09:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-rituals-embracing-the-core-principles-of-scrum-for-true-agile-success/</guid>
				<description>Focusing on Scrum rituals instead of its core principles, empiricism, transparency, and delivering value, can hinder true agile success. Overemphasis on mechanics leads to misplaced priorities, reduced creativity, and lower team engagement. Development managers should encourage open dialogue, support experimentation, and regularly assess whether practices are truly delivering value, adapting or discarding those that do not.</description>
			</item>
			<item>
				<title>Embracing Process Improvement: How Understanding Scrum Transformed a Developer&#39;s Mindset</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</link>
				<pubDate>Thu, 27 Jul 2017 19:14:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/embracing-process-improvement-how-understanding-scrum-transformed-a-developer&#39;s-mindset/</guid>
				<description>Understanding and embracing Scrum processes can transform developer mindsets, leading to better collaboration, higher quality product delivery, and more empowered teams. Taking time to learn and refine processes is essential for sustainable success, not just individual productivity. Development managers should encourage their teams to invest in process improvement to drive long-term value and team growth.</description>
			</item>
			<item>
				<title>Agile Is Not Easier Than Traditional Methods: Common Misconceptions</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/</link>
				<pubDate>Sat, 08 Mar 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/</guid>
				<description>Agile is often harder than traditional methods because it requires frequent delivery, decision-making with limited information, and handling uncertainty. Success depends on disciplined teams, strong collaboration, and a focus on delivering value, not just following a framework. Development managers should assess whether their teams are truly embracing Agile principles or simply following routines.</description>
			</item>
			<item>
				<title>Transforming Agile: How to Shift from Blame to Systemic Solutions for Better Team Dynamics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agile-how-to-shift-from-blame-to-systemic-solutions-for-better-team-dynamics/</link>
				<pubDate>Fri, 29 Sep 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agile-how-to-shift-from-blame-to-systemic-solutions-for-better-team-dynamics/</guid>
				<description>Problems in agile teams are usually caused by flawed measurement systems and processes, not individual intent. Metrics drive behavior, so focusing on changing how people are evaluated and incentivized is more effective than trying to change culture directly. Review your team’s metrics and processes to remove barriers and foster adaptability, which will lead to better collaboration and innovation.</description>
			</item>
			<item>
				<title>let-us be blunt</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</link>
				<pubDate>Sat, 10 May 2025 15:30:22 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt/</guid>
				<description>Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability.</description>
			</item>
			<item>
				<title>Most teams don’t fail because they lack frameworks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</link>
				<pubDate>Mon, 05 May 2025 15:30:43 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/</guid>
				<description>Teams usually fail not because they lack frameworks like Agile or Scrum, but because they ignore the feedback these frameworks reveal. The real challenge is creating a culture where teams feel safe and empowered to act on what they learn. Development managers should focus on listening to feedback and enabling teams to address issues, which leads to better performance and competitive advantage.</description>
			</item>
			<item>
				<title>Empowering Teams to Maximize Value and Return on Investment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</link>
				<pubDate>Wed, 24 Jul 2024 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/</guid>
				<description>Empowering teams to adapt their own processes is essential for maximizing value and return on investment in Agile environments. Teams that have autonomy, leadership support, and a culture of continuous improvement consistently outperform those forced to follow rigid, standardized processes. Development managers should trust teams to tailor their workflows, provide the necessary tools and support, and focus on outcomes rather than strict process adherence.</description>
			</item>
			<item>
				<title>Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</link>
				<pubDate>Wed, 05 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/</guid>
				<description>Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</link>
				<pubDate>Fri, 13 Sep 2024 07:00:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/</guid>
				<description>Evidence-based management in Scrum focuses on four key value areas, current value, unrealized value, ability to innovate, and time to market, to guide data-driven decisions and balance innovation with stability. Tracking metrics in these areas helps teams improve customer satisfaction, identify growth opportunities, manage technical debt, and speed up delivery. Development managers should start measuring these areas to align teams with evidence-based management and drive sustainable product success.</description>
			</item>
			<item>
				<title>Unlocking Agile Success: How Empirical Models Transform Project Outcomes</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</link>
				<pubDate>Wed, 12 Oct 2022 17:08:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/</guid>
				<description>Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction.</description>
			</item>
			<item>
				<title>Cutting Through the Red Tape: How Eliminating Committees Can Boost Your Time to Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/cutting-through-the-red-tape-how-eliminating-committees-can-boost-your-time-to-market/</link>
				<pubDate>Mon, 02 Oct 2023 07:00:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/cutting-through-the-red-tape-how-eliminating-committees-can-boost-your-time-to-market/</guid>
				<description>Committees often slow down decision-making and stall teams, leading to missed business opportunities and delayed time to market. Empowering teams to make decisions and adopting modern collaboration tools can significantly improve speed, accountability, and innovation. Review your current processes and consider reducing committee involvement to stay competitive and agile.</description>
			</item>
			<item>
				<title>Everyone loves to shout give teams autonomy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</link>
				<pubDate>Thu, 08 May 2025 15:30:40 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/</guid>
				<description>Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives.</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>Security by Design Building Secure Software</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/</link>
				<pubDate>Tue, 26 Nov 2024 13:35:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Illuminate Your Workflow: Harnessing Candan Strategies for Continuous Improvement and Transparency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/</link>
				<pubDate>Fri, 08 Mar 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/</guid>
				<description>Adopting a Candan strategy helps teams achieve continuous improvement and greater transparency by using flow metrics to identify workflow issues and inefficiencies. Visualising these metrics enables more informed decisions and motivates action, especially for Scrum teams that lack built-in measurement tools. To maximise benefits, integrate flow metrics into your processes and seek expert support or training if needed.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/</link>
				<pubDate>Wed, 02 Oct 2024 13:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/</guid>
				<description>Evidence-Based Management helps Agile teams make better decisions by using data from four key areas: current value, unrealized value, ability to innovate, and time to market. By collecting and analyzing relevant metrics, teams can prioritize improvements, boost innovation, and deliver more value to customers. Start by tracking a few key metrics with simple tools, then use those insights to guide your team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Stop Starting and Start Finishing: The Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</link>
				<pubDate>Wed, 31 Jan 2024 14:26:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</guid>
				<description>Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact.</description>
			</item>
			<item>
				<title>Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</link>
				<pubDate>Fri, 20 Oct 2023 16:01:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/conquering-sloth-in-agile-6-signs-your-team-might-be-stalling/</guid>
				<description>Many teams claim to be Agile but stall due to issues like not delivering working software each Sprint, lacking clear goals, ignoring user feedback, slow deployments, rigid requirements, and resistance to process change. These signs indicate a lack of true agility and hinder progress. Development managers should honestly assess their teams for these problems and take action to empower teams, streamline feedback and deployment, and adapt processes as needed.</description>
			</item>
			<item>
				<title>7 harbingers of the Agile apocalypse - Judgement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</link>
				<pubDate>Fri, 20 Oct 2023 11:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-judgement/</guid>
				<description>Rigid, judgmental application of Agile frameworks stifles creativity and innovation, turning teams into rule-followers instead of problem-solvers. True agility comes from empowering teams with autonomy, transparency, and principles rather than enforcing one-size-fits-all rules. Development managers should focus on fostering a culture of openness and continuous learning, allowing teams to adapt practices to their unique needs.</description>
			</item>
			<item>
				<title>Quotes: Less is More. True or False?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</link>
				<pubDate>Sat, 14 Oct 2023 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/quotes-less-is-more-true-or-false/</guid>
				<description>Focusing on fewer, high-value tasks rather than trying to do everything leads to better productivity and higher quality in Agile teams. Regularly refining the backlog and planning sprints around essential work helps eliminate waste and ensures efforts align with project goals. Development managers should encourage teams to prioritize what matters most to maximize results.</description>
			</item>
			<item>
				<title>How Usable Working Products Are Your Ultimate Weapon Against Risks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</link>
				<pubDate>Thu, 20 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/</guid>
				<description>Continuously delivering a usable working product is the most effective way to reduce risk in Agile development. Focus on releasing functional increments, fixing bugs quickly, automating tests, and keeping documentation lean to stay responsive to market needs. Prioritise regular feedback from users and stakeholders to ensure you are building what truly adds value.</description>
			</item>
			<item>
				<title>Evidence-based Management: Gathering the metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</link>
				<pubDate>Wed, 30 Dec 2020 14:02:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</guid>
				<description>Evidence-based Management helps software organizations focus on delivering real value by tracking metrics in three areas: current value, time to market, and ability to innovate. Traditional measures like on-time and on-budget delivery miss customer value, so organizations should gather and regularly review these agile-focused metrics to guide improvement. Start collecting baseline data now and reassess quarterly to track progress and demonstrate the impact of agile investments.</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>Harnessing Your Entrepreneurial Spirit: Key Strategies for Product Owners to Drive Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/harnessing-your-entrepreneurial-spirit-key-strategies-for-product-owners-to-drive-team-success/</link>
				<pubDate>Wed, 20 Sep 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/harnessing-your-entrepreneurial-spirit-key-strategies-for-product-owners-to-drive-team-success/</guid>
				<description>Product owners should connect their teams to the value they create by clearly communicating vision and goals, and foster evidence-based decision-making using data and user feedback rather than intuition. Focusing on metrics like time to market and balancing innovation with maintenance helps teams deliver better results faster. Encourage regular dialogue and rapid prototyping to keep teams engaged and responsive to user needs.</description>
			</item>
			<item>
				<title>Beyond the Agile Illusion: Embracing True Agility in a World of Taylorism</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</link>
				<pubDate>Tue, 21 Jul 2020 18:00:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/beyond-the-agile-illusion-embracing-true-agility-in-a-world-of-taylorism/</guid>
				<description>Many teams claim to be agile but still operate with outdated management mindsets that stifle autonomy and engagement, leading to low adoption of core agile practices like short iterations and retrospectives. True agility requires transparency, regular feedback, and a focus on delivering value rather than just completing tasks. Development managers should assess whether their teams meet these criteria and actively foster a culture that supports genuine agile principles.</description>
			</item>
			<item>
				<title>The Scrum Guide (February 2010)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</link>
				<pubDate>Mon, 01 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/</guid>
				<description>A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems.</description>
			</item>
			<item>
				<title>The Importance of Delivering Working Software Every Iteration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</link>
				<pubDate>Wed, 26 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/</guid>
				<description>Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort.</description>
			</item>
			<item>
				<title>7 Harbingers of the Agile Apocalypse - Famine</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-famine/</link>
				<pubDate>Thu, 19 Oct 2023 15:00:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-famine/</guid>
				<description>Resource scarcity in Agile organizations, such as lack of trust, funding, training, and tools, often stems from rigid, top-down management and can severely limit team performance and growth. Empowering teams with decision-making authority, flexible budgets, and a culture of trust and continuous learning leads to better outcomes and avoids costly mistakes. Development managers should prioritize investing in people and resources to enable agility and long-term success.</description>
			</item>
			<item>
				<title>What Makes an Effective Scrum Master Beyond Meeting Facilitation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</link>
				<pubDate>Sun, 23 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/</guid>
				<description>An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach.</description>
			</item>
			<item>
				<title>Story Points &amp; Velocity are a sign of an unsuccessful team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</link>
				<pubDate>Mon, 04 Jan 2021 14:20:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/story-points-velocity-are-a-sign-of-an-unsuccessful-team/</guid>
				<description>Story points and velocity are not required by Scrum and relying on them long-term signals a team&amp;rsquo;s lack of maturity and adaptability. While they can help new teams start conversations and build shared understanding, they do not provide real predictability or confidence in delivery. Development managers should focus on transparency, concrete data, and metrics like cycle time to build true confidence and improve predictability for stakeholders.</description>
			</item>
			<item>
				<title>The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-management-guide/</link>
				<pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-management-guide/</guid>
				<description>Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and continuous experimentation.</description>
			</item>
			<item>
				<title>You want speed, adaptability, resilience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</link>
				<pubDate>Sun, 11 May 2025 15:30:29 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</guid>
				<description>Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks.</description>
			</item>
			<item>
				<title>let-us be blunt, if a Scrum Team isn’t delivering, is it effective</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</link>
				<pubDate>Fri, 07 Mar 2025 16:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/</guid>
				<description>A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness.</description>
			</item>
			<item>
				<title>Sprint Review #1</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/</guid>
				<description>Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders.</description>
			</item>
			<item>
				<title>The Importance of Validation in Product Development: A Strategic Approach</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/</link>
				<pubDate>Mon, 02 Sep 2024 15:30:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/</guid>
				<description>Prioritizing features to close sales can fragment your product and lead to long-term costs that outweigh short-term gains. Shifting to a hypothesis-driven approach, where you define, track, and validate the value of new features using data, helps ensure you invest in what truly benefits users and the business. Equip product managers with the right telemetry and authority to make evidence-based decisions, and avoid building features that do not deliver measurable value.</description>
			</item>
			<item>
				<title>You are doing it wrong if you are not using test first</title>
				<link>https://engineering-leadership-preview.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-preview.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>Agile without a usable working product is just expensive theatre</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/</link>
				<pubDate>Sun, 20 Apr 2025 15:30:27 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/</guid>
				<description>Agile only delivers value if each sprint results in a usable working product; focusing on rituals, documentation, or velocity without real output wastes time and resources. The key measure of success is having something shippable at the end of every sprint, which enables feedback and reduces risk. Development managers should ensure their teams are consistently delivering usable products rather than just going through the motions.</description>
			</item>
			<item>
				<title>Empowering Leadership: Driving Cultural Change for Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-leadership-driving-cultural-change-for-agile-success/</link>
				<pubDate>Fri, 07 Feb 2025 06:00:27 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-leadership-driving-cultural-change-for-agile-success/</guid>
				<description>Leadership is crucial for enabling agile success by setting a clear vision, investing in automation, supporting architectural improvements, fostering continuous learning, and breaking down silos. These actions help teams align with organisational goals, deliver more reliably, and adapt to change. Development managers should prioritise these areas to create a culture that supports frequent, high-quality delivery and ongoing improvement.</description>
			</item>
			<item>
				<title>Combatting the Agile Apocalypse: How to Overcome the Famine of Feedback and Engagement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</link>
				<pubDate>Wed, 08 Nov 2023 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/</guid>
				<description>A lack of feedback and engagement from stakeholders, especially the product owner, leads to disengaged teams, poor product alignment, and increased risk of failure. Regular feedback sessions, open communication, and early stakeholder involvement are essential to keep teams motivated and ensure products meet business needs. Development managers should prioritise active stakeholder participation to maintain team morale and deliver better outcomes.</description>
			</item>
			<item>
				<title>7 Deadly Sins of Agile: Greed</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</link>
				<pubDate>Wed, 11 Oct 2023 12:00:36 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/</guid>
				<description>Focusing on resource utilisation over value in Agile leads to busywork, burnout, and reduced innovation, undermining true productivity. Teams should prioritise delivering customer value, balance workloads, and foster open communication and trust to enable creativity and continuous improvement. Development managers should shift from maximising activity to nurturing a value-driven, healthy Agile culture that supports learning and adaptation.</description>
			</item>
			<item>
				<title>Why is Satya Nadella a better example of agile leadership than Steve Jobs?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</link>
				<pubDate>Wed, 01 Feb 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-is-satya-nadella-a-better-example-of-agile-leadership-than-steve-jobs/</guid>
				<description>Satya Nadella is a stronger example of agile leadership than Steve Jobs because he built a culture of innovation and empowered teams across Microsoft, rather than centralizing decision-making and innovation in one person. Nadella decentralized authority, focused on meaningful metrics that drive customer value, and fostered continuous improvement and collaboration throughout the organization. Development managers should consider enabling team autonomy and aligning incentives with customer outcomes to drive sustainable innovation.</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>Mastering Evidence-Based Management in Agile: Inform, Don’t Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</link>
				<pubDate>Wed, 11 Sep 2024 13:36:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/</guid>
				<description>Evidence-Based Management helps you use data to guide decisions and understand team behaviors, but it should inform rather than control actions. Define clear outcomes, choose metrics that align with those goals, and use data as a conversation starter to uncover challenges and drive improvement. Regularly review metrics with your teams to stay aligned and focus on delivering real value, not just hitting targets.</description>
			</item>
			<item>
				<title>Sprint Review Recipe</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/</guid>
				<description>Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions.</description>
			</item>
			<item>
				<title>Create your own path to Organisational Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/</link>
				<pubDate>Thu, 11 Jan 2018 13:28:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/</guid>
				<description>A one-size-fits-all agile framework rarely works because every organisation’s path to agility is unique; instead, you should define a clear vision, form a cross-functional change team, and use an incremental, evidence-based approach to improvement. Broad, consistent training across all levels ensures everyone understands and supports the change, while involving stakeholders in identifying and prioritising impediments helps create a relevant organisational change backlog. To succeed, secure executive buy-in, empower teams to drive change, and focus on continuous, measurable improvements tailored to your context.</description>
			</item>
			<item>
				<title>Everyone loves the idea of self-managing teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</link>
				<pubDate>Tue, 18 Mar 2025 09:51:08 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/</guid>
				<description>Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability.</description>
			</item>
			<item>
				<title>Why More Teams Won&#39;t Speed Up Delivery: The Truth About Scaling Effectively</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-more-teams-won&#39;t-speed-up-delivery-the-truth-about-scaling-effectively/</link>
				<pubDate>Fri, 21 Feb 2025 07:59:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-more-teams-won&#39;t-speed-up-delivery-the-truth-about-scaling-effectively/</guid>
				<description>Adding more teams does not automatically speed up software delivery; it often creates more dependencies, coordination overhead, and technical debt, which can slow progress. Effective scaling focuses on reducing friction, structuring teams to minimize dependencies, and prioritizing quality over quantity. Development managers should ensure teams are set up to work independently and efficiently rather than simply increasing headcount.</description>
			</item>
			<item>
				<title>Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/</link>
				<pubDate>Thu, 13 Jul 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/</guid>
				<description>Delivering working software in small increments helps teams identify and address risks early, adapt to changes quickly, and get real feedback from users, while relying mainly on documentation can slow response to shifting needs. Documentation is still important, but focusing on usable products provides more value in fast-changing environments. Development managers should prioritize building and validating working software while maintaining just enough documentation to support adaptation and clarity.</description>
			</item>
			<item>
				<title>DOD has made it illegal to do waterfall</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</link>
				<pubDate>Tue, 01 May 2018 01:02:03 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/</guid>
				<description>The US Department of Defense has updated its procurement rules to require agile, iterative development instead of traditional waterfall methods, following high-profile failures like the FBI’s Sentinel project. Agile approaches have proven to deliver higher success rates, lower costs, and reduced risk, and these changes are now influencing government and vendor practices across the US and UK. Development managers working with government clients should adopt agile methods to align with new regulations and improve project outcomes.</description>
			</item>
			<item>
				<title>Scrum is not a process it is a social technology designed to expose dysfunction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</link>
				<pubDate>Sat, 29 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/</guid>
				<description>Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions.</description>
			</item>
			<item>
				<title>Redefining Agile’s Core: Beyond Rituals and Procedures</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</link>
				<pubDate>Mon, 22 Jan 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/redefining-agile-s-core-beyond-rituals-and-procedures/</guid>
				<description>Agile is not about following rituals or procedures but about delivering value and adapting to change to maximize business outcomes. Teams that focus only on rituals risk losing sight of continuous improvement and ownership, while over-automation can miss the need for human judgment in complex situations. Development managers should prioritize outcomes, encourage critical thinking about processes, and adapt Agile practices to their unique context rather than just checking boxes.</description>
			</item>
			<item>
				<title>The Pitfalls of Agile Burndowns: Stop Being Agile Bandits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</link>
				<pubDate>Tue, 09 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-pitfalls-of-agile-burndowns-stop-being-agile-bandits/</guid>
				<description>Relying on burndown charts leads to excessive upfront planning, false confidence, and wasted effort, as most plans quickly become outdated and only a fraction of features are actually used. Instead, focus on minimal, just-in-time planning and continuous flow to adapt quickly, reduce overhead, and deliver real value. Encourage your teams to plan only what is needed for the next day, adjust daily, and prioritize delivering value over maintaining detailed charts.</description>
			</item>
			<item>
				<title>The Power of Metrics: Why PAL-EBM is Essential for Your Organization</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/</link>
				<pubDate>Sat, 27 Jan 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/</guid>
				<description>The PAL-EBM class helps leaders and teams understand how to use metrics effectively to drive organizational success by focusing on real data, transparency, and the human impact of measurement. Participants learn through real-world stories why some metrics fail, how to avoid negative behaviors like those seen with Microsoft&amp;rsquo;s stack ranking, and how to foster strategic conversations that lead to better outcomes. Leadership teams are encouraged to take the class together to align on measuring success, iteratively strategize, and make informed decisions that support long-term goals.</description>
			</item>
			<item>
				<title>Scrum isn’t limited to building features</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</link>
				<pubDate>Fri, 30 May 2025 15:30:41 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/</guid>
				<description>Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products.</description>
			</item>
			<item>
				<title>Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</link>
				<pubDate>Wed, 06 Sep 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/</guid>
				<description>The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team&amp;rsquo;s next steps.</description>
			</item>
			<item>
				<title>Mastering Market Leadership: The Power of Frequent Product Releases</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/</link>
				<pubDate>Thu, 06 Feb 2025 11:02:31 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-market-leadership-the-power-of-frequent-product-releases/</guid>
				<description>Frequent product releases help you lead the market by allowing rapid response to user feedback and emerging trends. Teams that adopt this approach see higher user engagement and improved morale, as they can quickly deliver value and adapt to change. To stay competitive, focus on releasing updates regularly and listening closely to your users.</description>
			</item>
			<item>
				<title>Unlocking the Power of Immersive Learning for Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-for-product-management/</link>
				<pubDate>Mon, 12 Aug 2024 10:03:43 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-immersive-learning-for-product-management/</guid>
				<description>Immersive learning helps product management teams move beyond traditional training by combining extended, practical assignments with real-world application and reflection, leading to deeper understanding and organizational change. Focusing on outcome-based tasks and evidence-based metrics, rather than vanity measures, sparks valuable conversations and continuous improvement within teams. Development managers should consider adopting immersive learning approaches to drive lasting value and empower teams to deliver better results.</description>
			</item>
			<item>
				<title>Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</link>
				<pubDate>Wed, 17 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/</guid>
				<description>Empowering teams to update or delete requirements based on user feedback is essential for true agility and delivering maximum value. Regularly engaging with the product team, keeping the backlog dynamic, and being willing to pivot or remove features ensures your product stays relevant and user-focused. Review your processes to make sure your teams have the authority and support to make these changes.</description>
			</item>
			<item>
				<title>How to Discover Unrealized Value in Your Product</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-discover-unrealized-value-in-your-product/</link>
				<pubDate>Wed, 24 Jan 2024 11:00:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-to-discover-unrealized-value-in-your-product/</guid>
				<description>Evidence-Based Management helps you find hidden opportunities to improve your product by using metrics like customer satisfaction, market share, and innovation to identify gaps between current performance and potential value. By adding these insights to your product backlog and prioritizing improvements, you can boost user satisfaction, reduce churn, and stay competitive. Regularly review feedback and involve stakeholders to ensure continuous improvement and maximize your product’s value.</description>
			</item>
			<item>
				<title>Transforming Sprint Reviews: How to Engage Stakeholders and Secure Meaningful Feedback</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</link>
				<pubDate>Fri, 15 Dec 2023 11:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-sprint-reviews-how-to-engage-stakeholders-and-secure-meaningful-feedback/</guid>
				<description>Sprint reviews often fail to engage stakeholders or generate useful feedback because stakeholders do not see the value or feel emotionally connected to the work. To address this, communicate the benefits of participation early, use visuals, create a safe space for feedback, engage stakeholders before reviews, and tailor your approach to their interests. Development managers should focus on making Sprint reviews relevant and personal to stakeholders to drive better engagement and product outcomes.</description>
			</item>
			<item>
				<title>Sprint Goal is an Immediate Tactical Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</link>
				<pubDate>Mon, 11 Jan 2021 14:36:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/</guid>
				<description>The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.</description>
			</item>
			<item>
				<title>What my father taught me about Evidence-based Management (34 years before it was invented!)</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</link>
				<pubDate>Mon, 13 Jul 2020 18:42:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/</guid>
				<description>Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in both business and software contexts.</description>
			</item>
			<item>
				<title>Empowering Product Owners as Strategic Leaders in Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</link>
				<pubDate>Wed, 26 Mar 2025 16:30:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/</guid>
				<description>Product Owners should be empowered as strategic leaders who drive product vision and business value, not just manage backlogs. Scrum Masters play a key role in coaching Product Owners to use customer insights and data for better decisions. Development managers should ensure Product Owners have the authority and support to lead effectively, rather than treating them as task managers.</description>
			</item>
			<item>
				<title>There is no place like production</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-place-like-production/</link>
				<pubDate>Mon, 28 Dec 2020 14:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-place-like-production/</guid>
				<description>To deliver real value and reduce risk, teams must release features to production quickly so real users can provide feedback, since assumptions and testing environments cannot replace actual usage. Key measures like customer satisfaction, product usage, and employee satisfaction help validate value, and releasing early also offers financial benefits through capital expenditure write-downs. Prioritize getting small increments into production to maximize learning, value, and organizational savings.</description>
			</item>
			<item>
				<title>What is DevOps and how is it different to Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-devops-and-how-is-it-different-to-agile/</link>
				<pubDate>Thu, 23 Feb 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-devops-and-how-is-it-different-to-agile/</guid>
				<description>DevOps and Agile are fundamentally the same, both aiming to deliver value to customers and organizations by focusing on rapid feedback, continuous improvement, and systems thinking. The main difference is perspective, with each emphasizing different aspects of the delivery process, but both require the right tools and practices to optimize the whole system. Development managers should ensure Agile and DevOps work together to maximize value and improve outcomes across the organization.</description>
			</item>
			<item>
				<title>How Do You Know the Value Currently Delivered in Your Organization?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/</link>
				<pubDate>Tue, 23 Jan 2024 11:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/</guid>
				<description>Evidence-Based Management helps organizations measure and improve the value they deliver by using key metrics like customer satisfaction, employee engagement, revenue per employee, product cost ratio, and customer usage. This approach enables clearer goals, better decisions, and ongoing improvement by relying on data instead of assumptions. Start small with relevant metrics, involve your team, and regularly review results to drive meaningful change.</description>
			</item>
			<item>
				<title>How would you help organizations pitch the opportunity of agile internally?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</link>
				<pubDate>Wed, 08 Feb 2023 07:15:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-would-you-help-organizations-pitch-the-opportunity-of-agile-internally/</guid>
				<description>To successfully pitch agile internally, tailor your message to leadership by focusing on business outcomes they care about, such as reduced costs, faster time to market, and improved customer satisfaction, using clear metrics and financial examples. When engaging teams, use a consultative approach that involves them in problem-solving and framework selection to build buy-in and reduce resistance. The key action is to align agile benefits with stakeholder priorities and measure progress with relevant data to make a compelling, evidence-based case.</description>
			</item>
			<item>
				<title>Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</link>
				<pubDate>Mon, 13 Mar 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-greatness-how-the-right-scrum-master-transforms-teams-and-organisations/</guid>
				<description>A great Scrum Master is defined by their fit with the team and their ability to build trust, which is best achieved when teams help select their own Scrum Master. Beyond supporting the team, the most effective Scrum Masters build relationships across the organisation to identify and address broader obstacles, empowering others to drive change. Development managers should involve teams in Scrum Master selection and support their efforts to connect with stakeholders for greater organisational impact.</description>
			</item>
			<item>
				<title>Nexus Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/</guid>
				<description>Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies.</description>
			</item>
			<item>
				<title>Mastering Product Development Costs: Empower Your Team for Financial Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-development-costs-empower-your-team-for-financial-success/</link>
				<pubDate>Fri, 20 Dec 2024 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-development-costs-empower-your-team-for-financial-success/</guid>
				<description>Understanding and managing product development costs, especially people and infrastructure, is essential for financial success. Empowering teams with financial awareness helps them make better decisions, align work with value, and focus on profitable outcomes. Development managers should foster a culture where teams track costs, measure value delivered, and continuously improve processes to drive profitability and innovation.</description>
			</item>
			<item>
				<title>The Synergy Between Product Management and Product Development in Agile Environments</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</link>
				<pubDate>Thu, 25 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/</guid>
				<description>Product Management and Product Development must work closely together in agile environments to deliver products that meet current and future market needs. Product Management sets the vision and strategy, while Product Development brings these ideas to life through innovation, quality, and fast delivery, with both functions relying on continuous feedback and improvement. Development managers should ensure strong collaboration and feedback loops between these teams to maximize product value and long-term success.</description>
			</item>
			<item>
				<title>How Immersive Learning Transforms Aspiring Agile Leaders</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/how-immersive-learning-transforms-aspiring-agile-leaders/</link>
				<pubDate>Fri, 24 Nov 2023 07:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/how-immersive-learning-transforms-aspiring-agile-leaders/</guid>
				<description>Immersive learning experiences like the PAL-E class help aspiring agile leaders overcome common barriers by providing time, practical assignments, and peer feedback to apply and reflect on agile practices in real-world settings. Leaders gain actionable tools to empower teams, foster collaboration, and focus on value delivery rather than just process. Consider enrolling your leadership team in such a program to drive sustainable agile transformation and maximize organizational impact.</description>
			</item>
			<item>
				<title>Detecting agile theatre with real delivery signals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/</link>
				<pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/</guid>
				<description>Agile is measured by delivery, feedback, and decision-making authority in the hands of teams, not by visible ceremonies or tooling.</description>
			</item>
			<item>
				<title>Mastering Product Backlog Management: Essential Skills for Product Owners</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</link>
				<pubDate>Mon, 18 Dec 2023 07:00:15 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/</guid>
				<description>Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently.</description>
			</item>
			<item>
				<title>Say-Do Metrics: Avoiding Agile Banditry in Your Organization</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</link>
				<pubDate>Fri, 05 Jan 2024 07:00:28 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/</guid>
				<description>Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change.</description>
			</item>
			<item>
				<title>Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</link>
				<pubDate>Fri, 07 Oct 2022 10:41:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/</guid>
				<description>Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs.</description>
			</item>
			<item>
				<title>Unlocking Agility: How Decentralisation Empowers Teams to Maximise Value in Any Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agility-how-decentralisation-empowers-teams-to-maximise-value-in-any-organisation/</link>
				<pubDate>Thu, 28 Sep 2023 11:09:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agility-how-decentralisation-empowers-teams-to-maximise-value-in-any-organisation/</guid>
				<description>Decentralising decision-making empowers teams to respond faster, innovate more, and feel greater ownership, which leads to higher value delivery. Involving team members in shaping the organisation’s goals and connecting their skills to outcomes boosts engagement and collaboration. Development managers should focus on pushing responsibility to teams and fostering a shared sense of purpose to maximise results.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</link>
				<pubDate>Mon, 29 Jan 2024 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/</guid>
				<description>Evidence-Based Management (EBM) helps product owners make better decisions by tracking key metrics like current value, unrealized value, ability to innovate, and time to market, ensuring teams focus on delivering the right value efficiently. Using EBM enables you to identify when to pivot, align stakeholders, and engage your team in the product’s success. Consider adopting EBM practices or training, such as the PAL-EBM course, to maximize value delivery and team effectiveness.</description>
			</item>
			<item>
				<title>Kanban Guide for Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</guid>
				<description>Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery.</description>
			</item>
			<item>
				<title>Empowering Teams with Financial Insights: The Key to Maximising ROI and Fostering Ownership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-with-financial-insights-the-key-to-maximising-roi-and-fostering-ownership/</link>
				<pubDate>Thu, 12 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-with-financial-insights-the-key-to-maximising-roi-and-fostering-ownership/</guid>
				<description>Giving your teams clear financial insights and ownership over their work leads to better decision-making and higher returns. When teams understand both the value they create and the costs involved, they align their efforts with business goals and are more motivated to improve. Start sharing financial context and encourage team-level profit and loss analysis to drive accountability and smarter product decisions.</description>
			</item>
			<item>
				<title>Manifesto for Agile Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/</guid>
				<description>Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement.</description>
			</item>
			<item>
				<title>Transform Your Product Development: Unleash the Power of Experimentation and Collaboration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/</link>
				<pubDate>Sun, 11 Aug 2024 22:00:33 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/</guid>
				<description>This course teaches development managers how to boost user value and ROI by using experimentation, agile practices, and better collaboration with stakeholders. Key outcomes include reducing waste, speeding up time-to-market, and unlocking creative solutions by focusing on real problems. Consider applying these methods to streamline your process, make data-driven decisions, and deliver higher-impact products.</description>
			</item>
			<item>
				<title>The Myth of Knowing Everything Upfront in Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</link>
				<pubDate>Mon, 16 Jun 2025 15:30:47 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/</guid>
				<description>You cannot know everything upfront in software development, so focus on continuous discovery and adapt as you learn. Scrum supports this by encouraging just enough planning and design to move forward, then delivering and learning from real use. Prioritise delivery and feedback over excessive upfront design to create more value.</description>
			</item>
			<item>
				<title>Evidence-Based Portfolio Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-portfolio-management/</link>
				<pubDate>Wed, 16 Dec 2020 13:11:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/evidence-based-portfolio-management/</guid>
				<description>Explains how evidence-based portfolio management helps organisations extend agile practices beyond teams, enabling greater responsiveness and improved business outcomes.</description>
			</item>
			<item>
				<title>Why Copying Scaled Agile Frameworks Fails in Your Business</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</link>
				<pubDate>Tue, 10 Jun 2025 15:30:38 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/</guid>
				<description>Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint.</description>
			</item>
			<item>
				<title>Transforming Scope Creep into Success: Embrace Agility and Deliver Value in a Changing Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</link>
				<pubDate>Wed, 04 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/</guid>
				<description>Scope creep is often a sign that traditional fixed-scope approaches are failing in today’s fast-changing market. Focusing on delivering customer value, embracing flexible planning, and actively seeking feedback helps teams adapt and succeed. Development managers should shift from rigid scope management to Agile practices that prioritize value and responsiveness to change.</description>
			</item>
			<item>
				<title>The Fallacy of Equating Agility with Speed: What Agile Really Means</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</link>
				<pubDate>Thu, 11 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-fallacy-of-equating-agility-with-speed-what-agile-really-means/</guid>
				<description>Agile is not about working faster but about focusing on delivering the most valuable outcomes by prioritizing, experimenting, and adapting based on real customer needs. Speed alone can lead to building the wrong product, while Agile helps teams avoid wasted effort by eliminating unnecessary work and bureaucracy. Development managers should ensure their teams use Agile to maximize value, not just to increase velocity.</description>
			</item>
			<item>
				<title>Unlocking Success: The Essential Role of Product Ownership in Lean Product Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-the-essential-role-of-product-ownership-in-lean-product-delivery/</link>
				<pubDate>Thu, 28 Sep 2023 09:01:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-the-essential-role-of-product-ownership-in-lean-product-delivery/</guid>
				<description>Strong product ownership is essential for aligning product vision with business goals, fostering team collaboration, and enabling quick adaptation to change. Lean product delivery helps teams focus on delivering customer value, encourages continuous improvement, and empowers teams to take ownership of their work. Development managers should invest in training, promote experimentation, and establish feedback loops to enhance product ownership and stay competitive.</description>
			</item>
			<item>
				<title>Getting Started with Objectives &amp; Key Results</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-objectives-key-results/</link>
				<pubDate>Mon, 18 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-objectives-key-results/</guid>
				<description>OKRs only work when there is a clear strategy, a culture of transparency and adaptation, empowered teams, and a focus on outcomes over output. They help connect strategy to execution but require ongoing review, learning, and refinement to be effective. Before adopting OKRs, ensure your leadership, culture, and processes support these foundations or the framework will not deliver real value.</description>
			</item>
			<item>
				<title>Kanban Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</link>
				<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</guid>
				<description>Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work.</description>
			</item>
			<item>
				<title>Scrum is built on empiricism, transparency, inspection, and adaptation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</link>
				<pubDate>Mon, 24 Feb 2025 16:30:29 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/</guid>
				<description>Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint.</description>
			</item>
			<item>
				<title>Unlocking Organisational Agility: How to Empower Your Team for Rapid Market Response</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-organisational-agility-how-to-empower-your-team-for-rapid-market-response/</link>
				<pubDate>Fri, 01 Sep 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-organisational-agility-how-to-empower-your-team-for-rapid-market-response/</guid>
				<description>Organisational agility is about enabling your teams to respond quickly to market changes by empowering those closest to the customer to make decisions and reducing communication bottlenecks. Focusing on speed, clear context, and ownership helps capture opportunities faster than competitors. Review your decision-making processes and give teams the information and authority they need to act swiftly.</description>
			</item>
			<item>
				<title>In high competition markets, how does scrum product development help acquire and retain customers?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</link>
				<pubDate>Mon, 13 Feb 2023 07:00:21 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-high-competition-markets-how-does-scrum-product-development-help-acquire-and-retain-customers/</guid>
				<description>Scrum does not directly acquire or retain customers, but it helps teams deliver value quickly and adapt based on customer feedback, which can lead to competitive advantage. Its main strengths are making problems and opportunities visible, enabling rapid execution, and supporting a culture of innovation, but leaders and teams must still identify what customers need and how to deliver it. To succeed, focus on building strong teams, understanding market value, and using Scrum to consistently deliver and validate valuable features.</description>
			</item>
			<item>
				<title>Why are recessions a great time for organizations to evaluate the opportunity of agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</link>
				<pubDate>Thu, 09 Feb 2023 07:15:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-are-recessions-a-great-time-for-organizations-to-evaluate-the-opportunity-of-agile/</guid>
				<description>Recessions are an ideal time for organizations to consider agile because uncertainty highlights the need to adapt quickly, focus on customer value, and empower teams to make decisions. Agile enables rapid learning, continuous improvement, and faster response to market changes compared to traditional management. Development managers should pilot agile practices in small, iterative cycles to test their impact and build on what works.</description>
			</item>
			<item>
				<title>Quality enablement with Visual Studio 2012</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/</link>
				<pubDate>Wed, 15 May 2013 03:13:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>The Evolution of Product Management in the Agile Era</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</link>
				<pubDate>Thu, 18 Jul 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/</guid>
				<description>Agile product management replaces long release cycles with short, frequent delivery, enabling faster feedback, reduced risk, and more responsive adaptation to customer needs. Building quality in from the start and using practices like continuous integration and a clear definition of done minimizes defects and waste. Development managers should focus on shorter cycles, continuous feedback, and embedding quality throughout the process to stay competitive and maximize business value.</description>
			</item>
			<item>
				<title>OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/okr-guide/</link>
				<pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/okr-guide/</guid>
				<description>Comprehensive guide to using OKRs for shared focus, measurable outcomes, and strategic learning, including roles, events, best practices, and common pitfalls.</description>
			</item>
			<item>
				<title>In WIP, less is more.  Why?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-wip-less-is-more-why/</link>
				<pubDate>Tue, 09 May 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-wip-less-is-more-why/</guid>
				<description>Limiting work in progress leads to higher productivity because multitasking and context switching reduce efficiency and slow down progress. Keeping tasks small and focusing on finishing before starting new work helps teams deliver more in less time. Development managers should encourage teams to reduce simultaneous tasks and prioritize completing work to improve outcomes.</description>
			</item>
			<item>
				<title>Product Goal is an Intermediate Strategic Goal</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/product-goal-is-an-intermediate-strategic-goal/</link>
				<pubDate>Mon, 21 Dec 2020 14:27:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/product-goal-is-an-intermediate-strategic-goal/</guid>
				<description>Product Goals serve as intermediate steps that help teams evaluate and adapt progress toward broader strategic objectives, especially in uncertain environments. Focusing on outcomes over outputs, investing in discovery through flexible team allocation, and running hypothesis-driven experiments are key to delivering real value. Development managers should shift away from traditional project management and factory-style practices, adopting a data-driven, experimental approach to stay competitive and responsive.</description>
			</item>
			<item>
				<title>Hiring a Professional Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</link>
				<pubDate>Mon, 17 May 2021 14:17:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/</guid>
				<description>Hiring a professional Product Owner is increasingly valued, with companies seeking external candidates who bring fresh perspectives and strong business understanding. The Product Owner is accountable for maximizing product value by setting vision, managing stakeholders, collaborating with teams, making key decisions, and using evidence-based approaches to drive outcomes. Ensure candidates have both certification and practical experience, but remember that while responsibilities can be delegated, ultimate accountability always remains with the Product Owner.</description>
			</item>
			<item>
				<title>Transform Your Product Development: Unlock User Value, Reduce Waste, and Enhance Collaboration with Structured Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unlock-user-value-reduce-waste-and-enhance-collaboration-with-structured-learning/</link>
				<pubDate>Tue, 27 Aug 2024 07:07:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unlock-user-value-reduce-waste-and-enhance-collaboration-with-structured-learning/</guid>
				<description>A structured learning course in product development can help your teams better understand user needs through experimentation, reduce waste by making evidence-based decisions, and improve collaboration with stakeholders using data-driven discussions. The course also encourages creative problem-solving and provides practical tools you can apply immediately. Consider investing in this training to boost user value, efficiency, and team alignment.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Sweep problems under the rug</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/</link>
				<pubDate>Mon, 04 Mar 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/</guid>
				<description>Ignoring problems in your Kanban process leads to bigger issues, workflow blockages, and potential crises like project delays or cost overruns. Teams should regularly identify, visualize, and address problems, foster transparency, and take prompt action to prevent issues from escalating. Make it a priority to surface and resolve problems early to keep your workflow effective and avoid costly setbacks.</description>
			</item>
			<item>
				<title>The Importance of Batch to Optimise Flow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/</guid>
				<description>Explains how breaking large tasks into smaller batches improves workflow, predictability, and delivery speed, using hands-on exercises based on queuing theory principles.</description>
			</item>
			<item>
				<title>Navigating the Future with a Fine-Tuned Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</link>
				<pubDate>Thu, 10 Aug 2023 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/</guid>
				<description>A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery.</description>
			</item>
			<item>
				<title>Transforming Training: The Power of Immersive Learning in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</link>
				<pubDate>Wed, 08 May 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/transforming-training-the-power-of-immersive-learning-in-scrum/</guid>
				<description>Traditional two-day Scrum training is ineffective for lasting change because participants retain little and struggle to apply what they learn. Immersive learning, with shorter sessions spread over time, hands-on assignments, and ongoing feedback, leads to better retention, practical application, and continuous improvement. Development managers should consider adopting immersive training formats to drive real, sustainable transformation in their teams and organizations.</description>
			</item>
			<item>
				<title>Bridging the Gap: How to Align Your Organisation for Successful Agile Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</link>
				<pubDate>Mon, 06 May 2024 13:29:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/</guid>
				<description>Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</link>
				<pubDate>Wed, 30 Aug 2023 07:00:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/</guid>
				<description>Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs.</description>
			</item>
			<item>
				<title>Can organisations run an Applying Professional Scrum workshop? How would that help them?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</link>
				<pubDate>Wed, 29 Mar 2023 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/</guid>
				<description>Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Key to Agile Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-key-to-agile-success/</link>
				<pubDate>Fri, 26 Jan 2024 07:00:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/evidence-based-management-the-key-to-agile-success/</guid>
				<description>Focusing only on agile frameworks does not guarantee business success; organizations need to use evidence-based management to track real business outcomes and adapt based on data. Successful companies transform their leadership, processes, and decision-making using key metrics like current value, unrealized value, ability to innovate, and time to market. Development managers should prioritize data-driven decisions and organizational adaptability over simply following agile practices.</description>
			</item>
			<item>
				<title>Vision, Value, and Validation: The Keys to Successful Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</link>
				<pubDate>Thu, 14 Dec 2023 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/vision-value-and-validation-the-keys-to-successful-product-management/</guid>
				<description>When moving from project management to product management, it is essential for Product Owners to fill the gap left by traditional planning tools by focusing on vision, value, and validation. Clearly define and communicate the product vision, ensure all work aligns with delivering real value, and continuously validate progress through feedback and measurement. Prioritize these pillars to keep teams aligned and maximize product impact; consider seeking support if challenges arise.</description>
			</item>
			<item>
				<title>The Definition of Done: Ensuring Quality without Compromising Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</link>
				<pubDate>Wed, 27 Sep 2023 09:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/</guid>
				<description>The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team&amp;rsquo;s delivery.</description>
			</item>
			<item>
				<title>Product Ownership vs. Product Management: Busting the Myth That They&#39;re Separate Roles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</link>
				<pubDate>Thu, 01 Aug 2024 06:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they&#39;re-separate-roles/</guid>
				<description>Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive.</description>
			</item>
			<item>
				<title>Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</link>
				<pubDate>Tue, 26 Mar 2024 10:56:26 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/</guid>
				<description>Using a flat backlog instead of a hierarchical one makes it easier to prioritise work, adapt to changing needs, and focus on delivering value rather than just managing tasks. Flat structures avoid the inflexibility and complexity of parent-child relationships, allowing teams to use tags and flexible visualisations for context. Development managers should consider shifting to a flat backlog to improve agility and value delivery.</description>
			</item>
			<item>
				<title>Mastering Prioritisation: How Product Owners Can Drive Value and Accountability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</link>
				<pubDate>Mon, 27 Nov 2023 11:00:56 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/</guid>
				<description>Product Owners play a crucial role in ensuring resources are spent wisely by prioritising the most valuable work, aligning development with business goals, and maintaining stakeholder trust through clear communication. Effective prioritisation maximises value delivery, keeps teams focused, and adapts to changing needs. Development managers should support Product Owners in understanding users, collaborating closely, and staying flexible to drive successful outcomes.</description>
			</item>
			<item>
				<title>Temperance in Agile: Why Less is More</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</link>
				<pubDate>Tue, 05 Dec 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/</guid>
				<description>Focusing on just enough work and keeping your backlog, planning, and team size lean helps your team deliver more value and avoid waste or burnout. Prioritize only high-impact tasks, limit work in progress, and avoid over-refining or over-planning. Say no to non-essential work, balance short-term wins with long-term goals, and seek coaching if you struggle to maintain this balance.</description>
			</item>
			<item>
				<title>The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</link>
				<pubDate>Thu, 03 Jul 2025 05:22:41 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/</guid>
				<description>The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together.</description>
			</item>
			<item>
				<title>Too many organisations hide behind excuses:&#34;</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/</link>
				<pubDate>Sat, 07 Jun 2025 15:30:25 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/</guid>
				<description>Even large, regulated, and traditionally slow organizations like the DOD and FBI have successfully adopted iterative delivery, showing that excuses for not embracing agile are unfounded. Agile helps reduce risk, increase flexibility, and deliver value incrementally, which is especially important in regulated industries. Development managers should challenge resistance and prioritize agile practices to improve outcomes regardless of organizational constraints.</description>
			</item>
			<item>
				<title>Unlocking Product Value: Why Real User Feedback is Your Best Asset</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-product-value-why-real-user-feedback-is-your-best-asset/</link>
				<pubDate>Fri, 07 Feb 2025 07:52:12 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-product-value-why-real-user-feedback-is-your-best-asset/</guid>
				<description>Product value is only proven when real users interact with your product, so early and ongoing user feedback is essential to validate assumptions and guide development. Engaging users early, testing with prototypes or MVPs, and iterating based on feedback help ensure your product meets real needs and delivers genuine value. Prioritise getting your product in front of users quickly to maximise impact and avoid wasted effort.</description>
			</item>
			<item>
				<title>Unpacking Assumptions: How to Elevate Your Product Development Beyond the Feature Factory</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-assumptions-how-to-elevate-your-product-development-beyond-the-feature-factory/</link>
				<pubDate>Tue, 13 Aug 2024 07:14:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unpacking-assumptions-how-to-elevate-your-product-development-beyond-the-feature-factory/</guid>
				<description>Many teams focus on delivering features quickly but often overlook the assumptions behind what users truly need, leading to wasted effort and misaligned products. The PPD V course helps product teams identify and challenge these assumptions through structured discovery, experimentation, and validation, fostering better collaboration and evidence-based decisions. Consider investing in approaches that prioritise learning and user value over simply shipping features.</description>
			</item>
			<item>
				<title>Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</link>
				<pubDate>Wed, 23 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</guid>
				<description>Kanban can be applied to any workflow to provide visibility into how work moves through your system, enabling teams to optimise delivery speed and manage capacity effectively. By using data analysis and probabilistic forecasting, such as Monte Carlo simulations, you can set realistic expectations with stakeholders and make more informed decisions. Consider adopting Kanban to improve transparency, predictability, and continuous improvement in your development processes.</description>
			</item>
			<item>
				<title>Rethinking Budgeting: How to Break Free from Traditional Constraints and Maximise Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-budgeting-how-to-break-free-from-traditional-constraints-and-maximise-value/</link>
				<pubDate>Mon, 09 Dec 2024 06:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-budgeting-how-to-break-free-from-traditional-constraints-and-maximise-value/</guid>
				<description>Traditional annual budgeting creates rigidity, discourages innovation, and often leads to missed opportunities and wasted resources. Adopting a more flexible, value-driven approach like Beyond Budgeting allows teams to allocate funds dynamically, respond quickly to changing needs, and focus on delivering real value. Development managers should consider shifting to iterative funding models to maximise impact and avoid costly missed opportunities.</description>
			</item>
			<item>
				<title>Mastering Kanban: A Simple Guide to Its Core Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</link>
				<pubDate>Mon, 01 Jul 2024 07:00:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/</guid>
				<description>Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency.</description>
			</item>
			<item>
				<title>Understanding the Power of Kanban in Scrum</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</link>
				<pubDate>Mon, 05 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/</guid>
				<description>Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery.</description>
			</item>
			<item>
				<title>Understanding Kanban: A Tool for Transparency and Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</link>
				<pubDate>Mon, 24 Jun 2024 06:48:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/</guid>
				<description>Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements.</description>
			</item>
			<item>
				<title>Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</link>
				<pubDate>Thu, 25 Jan 2024 07:00:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-business-value-the-power-of-evidence-based-management-for-effective-leadership/</guid>
				<description>Evidence-based management helps leaders make better decisions by focusing on meaningful metrics that drive real business value, such as current and unrealised value, time to market, and ability to innovate. Regularly reviewing and tailoring these metrics to your organisation enables data-driven strategies and a clear competitive advantage. Consider adopting this approach to move beyond gut feelings and ensure your team delivers measurable results.</description>
			</item>
			<item>
				<title>How to Set and Achieve Effective Sprint Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</link>
				<pubDate>Fri, 29 Sep 2023 12:12:59 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/</guid>
				<description>Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed.</description>
			</item>
			<item>
				<title>Unlocking Startup Success: Why Every Entrepreneur Needs to Master Product Management Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-startup-success-why-every-entrepreneur-needs-to-master-product-management-value/</link>
				<pubDate>Tue, 16 May 2023 14:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-startup-success-why-every-entrepreneur-needs-to-master-product-management-value/</guid>
				<description>Mastering product management value is critical for startup success, as it helps ensure you deliver what customers truly need and avoid common causes of failure. Key actions include focusing on value, communicating a clear vision, using practical tools, and regularly engaging with your team and customers to adapt based on feedback. Investing in product management training like the PSPO course can strengthen your foundation and support long-term growth.</description>
			</item>
			<item>
				<title>The Strategic Imperative: Empowering Teams with Vision, Goals, and Direction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</link>
				<pubDate>Thu, 08 Aug 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-strategic-imperative-empowering-teams-with-vision-goals-and-direction/</guid>
				<description>Many teams lack clarity on their organization’s vision, goals, and value, leading to inefficiency and misaligned efforts. To address this, leaders should clearly communicate strategic direction, empower teams with autonomy through intent-based leadership, and move beyond rigid procedures to foster engagement and continuous improvement. Ensure everyone understands how their work contributes to broader objectives so teams can make informed decisions and drive meaningful results.</description>
			</item>
			<item>
				<title>Understanding Product Discovery: Why It Matters More Than Ever</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-product-discovery-why-it-matters-more-than-ever/</link>
				<pubDate>Mon, 26 Aug 2024 07:44:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/understanding-product-discovery-why-it-matters-more-than-ever/</guid>
				<description>Product Discovery is a proactive process that helps teams identify what to build and why, ensuring alignment with business goals and user needs. It goes beyond backlog refinement by uncovering new opportunities, involving diverse perspectives, and driving strategic direction at both portfolio and team levels. To maximize product value and ROI, development managers should invest in deliberate discovery practices, involve their teams early, and continuously gather feedback to guide decisions.</description>
			</item>
			<item>
				<title>Unlocking Success: How Lean Product Development Transforms Decision-Making and Value Creation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-lean-product-development-transforms-decision-making-and-value-creation/</link>
				<pubDate>Thu, 28 Sep 2023 08:29:48 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-lean-product-development-transforms-decision-making-and-value-creation/</guid>
				<description>Lean product development is gaining traction because it helps teams make better decisions, reduce risk, and create more value with fewer resources. Adopting this mindset enables organisations to focus on building products that truly meet customer needs and avoid wasted effort. Development managers should consider exploring lean practices to improve product outcomes and maximise return on investment.</description>
			</item>
			<item>
				<title>Unlocking Effective Product Development: How a Hypothesis-Driven Approach Transforms User Experience</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</link>
				<pubDate>Mon, 10 Apr 2023 07:00:18 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-effective-product-development-how-a-hypothesis-driven-approach-transforms-user-experience/</guid>
				<description>A hypothesis-driven approach to product development helps teams make better decisions by focusing on user needs, testing ideas with small experiments, and measuring outcomes before committing to full features. Collaboration between design and engineering is essential to align daily decisions with long-term goals, and integrating these practices into continuous delivery ensures ongoing improvement. Development managers should encourage experimentation, cross-team collaboration, and data-driven feedback loops to build products that truly meet user needs.</description>
			</item>
			<item>
				<title>The Art of Negotiation for Product Owners: Essential Skills to Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-art-of-negotiation-for-product-owners-essential-skills-to-master/</link>
				<pubDate>Wed, 13 Dec 2023 07:00:07 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-art-of-negotiation-for-product-owners-essential-skills-to-master/</guid>
				<description>Strong negotiation skills are essential for Product Owners to balance stakeholder demands, technical realities, and leadership requests, ensuring the product delivers maximum value. Key techniques include active listening, asking probing questions, and guiding others to see the bigger picture, which helps avoid unnecessary features and maintain focus. Development managers should encourage Product Owners to build these skills through training, reflection, and coaching to improve outcomes and stakeholder relationships.</description>
			</item>
			<item>
				<title>Adaptive Operating Model</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/adaptive-operating-model/</link>
				<pubDate>Fri, 16 Jan 2026 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/adaptive-operating-model/</guid>
				<description>An adaptive operating model is an organisational structure designed to enable value delivery in environments characterised by uncertainty, complexity, and ongoing change. Unlike traditional models that rely on prediction, control, and centralised authority, the adaptive operating model is built around principles of learning, rapid feedback, and decentralised decision-making. Its core features include organising work around outcomes rather than tasks or projects, distributing decision rights to those closest to emerging information, embedding explicit learning loops for continuous adjustment, maintaining stable teams and roles while allowing flexible execution, and implementing governance that supports flow and transparency rather than rigid compliance. This model serves as the foundational structure for product-centric organisations and underpins specialised approaches such as product operating models and agile product operating models, which apply adaptive principles specifically to product delivery. The adaptive operating model is not a set of delivery practices, a process framework, or a superficial change initiative; rather, it fundamentally redefines how work is coordinated, how decisions are made, and how value is discovered within an organisation. Organisations adopt this model when they face rapidly evolving customer needs, technological uncertainty, high coordination costs, bottlenecks from centralised control, and when the speed of learning is more critical than adherence to plans. In such contexts, adaptability becomes essential for survival, making the adaptive operating model particularly valuable in agile, DevOps, product development, and modern organisational design, where empiricism, accountability, and the ability to respond to change are paramount.</description>
			</item>
			<item>
				<title>Agentic Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-engineering/</link>
				<pubDate>Tue, 22 Jul 2025 15:58:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-engineering/</guid>
				<description>Agentic Engineering is the deliberate design and practice of software development that maximises the agency of both humans and intelligent systems. It integrates engineering excellence, DevOps ethos, and ethical autonomy to create environments where decisions are decentralised, feedback is fast, and value delivery is continuous. It&amp;rsquo;s characterised by Developer Agency, Systemic Observability, DevOps-Infused Craft, Ethical AI Integration, and Feedback-Driven Adaptation. Agentic Engineering is not a job title, role, or method, it&amp;rsquo;s a philosophy of engineering in which the ability to act with clarity, intent, and impact is engineered into the way we build, learn, and evolve.</description>
			</item>
			<item>
				<title>Ethos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/ethos/</link>
				<pubDate>Tue, 13 May 2025 10:30:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/ethos/</guid>
				<description>Ethos is the foundation beneath principles, practices, and strategies. It informs how we lead, how we coach, and how we build systems that endure. Without a clearly defined ethos, teams drift into rituals without results, Scrum becomes status theatre, DevOps becomes tool automation, and transformation stalls. Ethos brings coherence and conviction to how we work. It’s not a mindset. It’s a disciplined stance.</description>
			</item>
			<item>
				<title>Customer Focus</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/customer-focus/</link>
				<pubDate>Tue, 13 May 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/customer-focus/</guid>
				<description>Customer Focus is not a platitude. It&amp;rsquo;s the first principle of agile delivery and product development. It defines value, directs investment, and constrains decisions. If you&amp;rsquo;re not anchored in real customer outcomes, you&amp;rsquo;re optimising the wrong system. This principle demands more than empathy. It demands feedback, evidence, and relentless alignment to customer need.</description>
			</item>
			<item>
				<title>Increment</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/increment/</guid>
				<description>Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices.</description>
			</item>
			<item>
				<title>Product Backlog</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/</guid>
				<description>The Product Backlog is a dynamic and prioritised list of work items that acts as the definitive source for what needs to be accomplished in order to deliver a product. It includes features, enhancements, bug fixes, and technical tasks, providing teams with a clear understanding of their objectives. This concept is vital as it allows teams to deliver value in a predictable and sustainable manner by offering transparency regarding priorities and progress. Effective management of the backlog encourages collaboration among stakeholders and enables continuous refinement based on feedback and shifting market conditions. It empowers teams to make informed decisions about their next steps, aligning their work with strategic goals and customer needs. The Product Backlog is more than just a to-do list; it is a living artefact that captures the evolving understanding of the product and its context, promoting a culture of continuous improvement and adaptability. By maintaining a well-structured backlog, organisations can enhance agility, minimise waste, and optimise resource allocation, leading to more successful product outcomes. This systematic approach to backlog management supports long-term planning while remaining flexible enough to address new insights and challenges as they emerge. Ultimately, the Product Backlog is foundational to effective Agile practices, ensuring that teams focus on delivering high-quality, valuable products that meet user expectations and contribute to business success.</description>
			</item>
			<item>
				<title>Site Reliability Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/</guid>
				<description>Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks.</description>
			</item>
			<item>
				<title>Definition of Done</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/</guid>
				<description>The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.</description>
			</item>
			<item>
				<title>Definition of Workflow</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</link>
				<pubDate>Mon, 05 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-workflow/</guid>
				<description>The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability.</description>
			</item>
			<item>
				<title>Lead Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/</guid>
				<description>Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments.</description>
			</item>
			<item>
				<title>Agnostic Agile</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</link>
				<pubDate>Thu, 10 Apr 2025 14:49:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agnostic-agile/</guid>
				<description>Agnostic Agile is a movement that advocates for a flexible and context-driven approach to agility, emphasising the importance of principles over rigid frameworks. Originating from the need for adaptability in various methodologies, it encourages teams to tailor their practices based on specific requirements rather than conforming to a single ideology. This pragmatic approach allows practitioners to integrate diverse methodologies such as Scrum, Kanban, Lean, and Extreme Programming, fostering an environment that values critical thinking and professionalism. By prioritising value delivery, Agnostic Agile equips teams to respond effectively to evolving circumstances, ensuring predictable and sustainable value generation. This adaptability is essential in today&amp;rsquo;s dynamic environments, where the capacity to pivot and innovate can significantly influence an organisation&amp;rsquo;s success. Furthermore, Agnostic Agile promotes ethical practices by avoiding brand loyalty to specific frameworks, thereby nurturing a culture of continuous improvement and learning. This mindset empowers teams to experiment and refine their processes, ultimately supporting a long-term, systemic approach to agility that enhances organisational resilience and effectiveness. As such, Agnostic Agile is a crucial concept in contemporary product development and delivery, providing valuable insights for teams striving to thrive in an ever-changing landscape.</description>
			</item>
			<item>
				<title>Cell Structure Design</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cell-structure-design/</link>
				<pubDate>Thu, 10 Apr 2025 14:48:25 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cell-structure-design/</guid>
				<description>Cell Structure Design is an organisational model that redefines traditional hierarchies by establishing a decentralised network of autonomous units, referred to as cells. Each cell is granted end-to-end responsibility, enabling rapid responses to customer needs and market fluctuations. This model aligns with the principles of the Beta Codex, promoting accountability and continuous adaptation through dynamic coordination rather than a command-and-control approach. Grounded in complexity theory, Cell Structure Design acknowledges the unpredictable nature of modern business environments, where adaptability is essential. By fostering transparency and collaboration both within and between cells, this structure enhances communication and accelerates decision-making, allowing teams to deliver value in a predictable and sustainable manner. The independent yet cohesive operation of cells facilitates ongoing innovation and process improvement, contributing to long-term organisational success. This systemic design not only boosts operational efficiency but also nurtures a culture of empowerment and engagement, which is vital for thriving in today’s fast-paced business landscape. Ultimately, the focus on value creation and responsiveness equips organisations to effectively navigate complexity, ensuring their competitiveness and relevance in the market.</description>
			</item>
			<item>
				<title>Company as a Product</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/company-as-a-product/</link>
				<pubDate>Thu, 10 Apr 2025 14:47:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/company-as-a-product/</guid>
				<description>Company as a Product (CaaP) is an organisational strategy that conceptualises the entire company as a dynamic product, evolving continuously based on customer feedback and measurable outcomes. Originating from the principles of agile and product development, this approach emphasises the alignment of all organisational components, people, processes, and systems, towards delivering customer value. CaaP fosters a culture of cross-functional collaboration and experimentation, enabling teams to respond swiftly to market changes and customer needs. This strategy represents a significant shift from traditional hierarchical structures to a more fluid and responsive organisational model, encouraging leaders to view their company&amp;rsquo;s capabilities as adaptable. By promoting a mindset of continuous improvement, CaaP ensures that every aspect of the organisation is open to refinement and innovation, which is crucial for maintaining competitiveness and relevance in a rapidly changing environment. Ultimately, by treating the organisation as a product, CaaP facilitates predictable and sustainable value delivery, establishing a resilient framework that supports long-term success and adaptability.</description>
			</item>
			<item>
				<title>Ability to Innovate</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/ability-to-innovate/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:20 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/ability-to-innovate/</guid>
				<description>Ability to Innovate refers to an organisation&amp;rsquo;s capacity to generate, implement, and sustain innovative solutions effectively, which is essential for delivering value in a predictable and sustainable manner. This concept is rooted in the need for organisations to adapt to changing market demands and customer needs, thereby maintaining competitiveness. It encompasses various measures, such as the frequency of experiments, innovation throughput, and learning cycles, which collectively provide insight into an organisation&amp;rsquo;s innovation capabilities. By focusing on systemic growth and adaptability rather than specific methodologies, the Ability to Innovate fosters a culture that views failure as a learning opportunity, promoting psychological safety and collaboration among teams. This cultural embedding of innovation empowers teams to explore new ideas and solutions, leading to enhanced customer satisfaction and increased business agility. The emphasis on continuous improvement and experimentation ensures that innovation becomes a sustained effort rather than a sporadic occurrence, positioning it as a fundamental aspect of modern product development and organisational design.</description>
			</item>
			<item>
				<title>Current Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/current-value/</guid>
				<description>Current Value is a vital metric within Evidence-Based Management that quantifies the real-time value a product or service provides to its users. It includes various indicators such as customer satisfaction, revenue impact, and performance feedback, which together offer insights into the value being realised at any moment. This concept is crucial for teams striving to deliver value in a predictable and sustainable manner, as it facilitates continuous assessment and adjustment based on actual performance rather than assumptions. By tracking Current Value, organisations can make data-driven decisions that improve their offerings and better align them with customer needs. This ongoing evaluation promotes a culture of responsiveness and adaptability, allowing teams to swiftly adjust to feedback and shifting market conditions. Unlike static measures, Current Value is dynamic and systemic, reflecting the changing landscape of customer expectations and business environments. It empowers teams to concentrate on delivering meaningful outcomes, ensuring that their efforts lead to long-term success and customer loyalty. This emphasis on real-time value delivery distinguishes Current Value from other concepts such as Value Stream Management or Customer Satisfaction, which may not fully capture the immediacy and comprehensive nature of the value being generated.</description>
			</item>
			<item>
				<title>Time to Market</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/time-to-market/</link>
				<pubDate>Thu, 10 Apr 2025 14:20:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/time-to-market/</guid>
				<description>Time to Market is a critical metric that evaluates how quickly an organisation can transform ideas into market-ready products or features, incorporating various measures such as lead time and cycle time to provide a comprehensive understanding of product development efficiency. This concept is essential for organisations striving to deliver value in a predictable and sustainable manner, as a shorter Time to Market allows teams to swiftly address customer needs and adapt to market fluctuations. By prioritising Time to Market, organisations can gain a competitive advantage, ensuring that their innovations reach customers ahead of competitors. This focus on agility promotes a culture of continuous improvement, encouraging teams to refine processes and eliminate inefficiencies. The systemic nature of Time to Market impacts not only individual projects but also the overall organisational capacity for innovation and adaptability. It aligns with Lean and Agile methodologies, fostering a mindset that prioritises speed while maintaining quality. Ultimately, a strong commitment to Time to Market nurtures an environment where delivering value becomes a core organisational principle, contributing to long-term success and resilience in an ever-evolving marketplace.</description>
			</item>
			<item>
				<title>Unrealised Value</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/unrealised-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:19:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/unrealised-value/</guid>
				<description>Unrealised Value refers to the potential value that an organisation has yet to capture, highlighting opportunities for improvement and innovation. It encompasses various indicators that assess untapped possibilities, such as latent market demand or areas ripe for enhancement. By focusing on Unrealised Value, teams can identify opportunities to optimise processes, innovate products, or better meet customer needs, ultimately leading to increased competitiveness and sustainability. This concept is crucial for enabling teams to deliver value predictably and sustainably, as it promotes a proactive approach to recognising and addressing gaps in performance and capability. Systematically measuring and analysing Unrealised Value fosters a culture of continuous improvement, motivating teams to explore new ideas and solutions. This long-term focus not only enhances current operations but also positions organisations to adapt to changing market conditions and customer expectations. Understanding Unrealised Value empowers teams to make informed decisions about resource allocation, ensuring they are strategically planning for future growth and success rather than merely reacting to immediate challenges. This perspective shifts the focus from delivering current value to actively seeking and realising potential value, which is essential for thriving in today’s dynamic business landscape.</description>
			</item>
			<item>
				<title>Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/product-development/</link>
				<pubDate>Wed, 09 Apr 2025 14:47:40 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/product-development/</guid>
				<description>Product Development is a structured approach to creating valuable and usable products through iterative learning, customer feedback, and continuous improvement. Originating from methodologies such as Agile, Lean, and DevOps, it aligns strategy, discovery, and delivery to enhance outcomes while reducing risks. This process is vital as it enables teams to swiftly adapt to shifting market demands and customer preferences, fostering an innovative environment. By promoting collaboration and transparency among cross-functional teams, Product Development ensures that customer feedback informs product iterations, leading to enhancements that not only meet but exceed user expectations. Its systemic nature underscores that Product Development is not just about launching a product but establishing a sustainable framework for ongoing value delivery. This approach encourages experimentation and learning, resulting in greater efficiency and effectiveness in product delivery. By prioritising continuous improvement and adaptability, organisations can build resilience and maintain a competitive advantage in a dynamic landscape. Ultimately, the focus on value delivery ensures that all efforts align with the organisation&amp;rsquo;s strategic objectives, highlighting the critical role of a well-defined Product Development process in achieving long-term success.</description>
			</item>
			<item>
				<title>Scaling</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scaling/</link>
				<pubDate>Wed, 09 Apr 2025 13:53:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scaling/</guid>
				<description>Scaling refers to the capacity of an organisation to effectively coordinate multiple teams in the delivery of complex products while maintaining agility. This concept originates from the need to align efforts, optimise workflow, and enhance value delivery across the enterprise. It is particularly important in the contexts of agile methodologies and DevOps, as it allows organisations to respond swiftly to market changes without compromising on quality or speed. By implementing lean principles and adaptive product structures, scaling promotes a cohesive approach to product development, enabling teams to operate autonomously while remaining aligned with broader business objectives. This alignment is crucial for maximising efficiency and minimising waste, thereby leveraging the organisation&amp;rsquo;s collective capabilities. Furthermore, scaling fosters a culture of continuous improvement, where feedback loops and collaboration are integral to the development process. By prioritising these aspects, organisations can achieve sustainable growth and deliver value consistently, enhancing their competitive advantage in a rapidly changing environment. Ultimately, scaling is not just about increasing size but about establishing a robust framework that supports innovation and responsiveness throughout the organisation.</description>
			</item>
			<item>
				<title>Capability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/capability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/capability/</guid>
				<description>Capability refers to a persistent competence that enables teams or organisations to deliver value in a predictable, sustainable, and adaptive manner. Unlike transient tools or one-off techniques, capabilities are cultivated over time and become embedded in organisational culture and processes. They are crucial for fostering an environment where teams can effectively respond to changing demands, leveraging collective skills and knowledge to ensure value delivery aligns with strategic objectives. The development of capabilities involves a commitment to learning and collaboration, enhancing individual competencies while building cohesive team dynamics essential for high performance. As teams grow in their capabilities, they become adept at proactively identifying and addressing issues, leading to improved outcomes and reduced risk. Capabilities also facilitate alignment across various functions within an organisation, serving as a common language that bridges gaps between teams, which is particularly important in agile and DevOps environments. They are dynamic, evolving through feedback loops that inform future practices, and are actionable and measurable, allowing organisations to track progress and make informed development decisions. Ultimately, investing in capabilities enhances agility, resilience, and the ability to deliver consistent value, positioning organisations to thrive in an ever-changing landscape and enabling teams to navigate complexity and uncertainty with confidence.</description>
			</item>
			<item>
				<title>Observability</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/observability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/observability/</guid>
				<description>Observability is the practice of gaining comprehensive insights into systems and processes, enabling teams to understand work flows and value delivery. It transcends traditional monitoring by offering a holistic view of system behaviour, which allows teams to identify patterns, diagnose issues, and make informed decisions based on real-time data. This capability is essential for fostering transparency and collaboration within teams and across organisational silos. By implementing observability, organisations can improve their ability to deliver value predictably and sustainably, supporting continuous improvement through learning and adaptation. It encompasses not only technical telemetry but also signals reflecting team dynamics, product experiences, and alignment with strategic goals, thus providing a complete view of performance that includes both human and technical factors. When integrated into daily practices, observability cultivates a feedback-rich environment that enhances decision-making and strengthens delivery capabilities. It represents a cultural shift that empowers teams to take ownership of their processes and outcomes, aligning with Lean and Agile principles focused on understanding flow and eliminating waste. By embedding observability into the organisational framework, teams can create a resilient environment that leverages data-driven insights, ultimately leading to improved products, stronger teams, and more strategic business outcomes.</description>
			</item>
			<item>
				<title>Practice</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/practice/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/practice/</guid>
				<description>Practice refers to the consistent and repeatable techniques or habits that teams employ to improve their effectiveness, collaboration, and value delivery. Originating from Agile, Lean, and DevOps methodologies, practices such as Pair Programming, Continuous Deployment, and Retrospectives are integral to fostering ongoing, systematic routines that enhance team dynamics and performance. Unlike structured methods, which provide defined steps, practices focus on the habitual actions that teams incorporate into their workflows. For instance, Pair Programming not only boosts code quality but also promotes knowledge sharing, while Retrospectives allow teams to reflect on their processes and identify areas for improvement, thus supporting continuous enhancement. Although tools like Kanban boards can facilitate these practices, the essence lies in how teams manage their workflows and adapt their routines to evolving challenges. The long-term value of practices is evident in their ability to embed behaviours that lead to predictable and sustainable outcomes, such as the frequent and reliable software releases enabled by Continuous Deployment. Ultimately, practices are crucial for effective teamwork, as they shape collaboration, drive continuous improvement, and ensure responsiveness to both internal and external demands, making them essential in the fast-paced environments characteristic of modern product development and organisational design.</description>
			</item>
			<item>
				<title>Scrum Master</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</link>
				<pubDate>Tue, 25 Mar 2025 07:35:53 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/scrum-master/</guid>
				<description>The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint.</description>
			</item>
			<item>
				<title>Common Goals</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</link>
				<pubDate>Fri, 21 Mar 2025 14:45:01 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/common-goals/</guid>
				<description>Common Goals are a foundational principle for effective delivery within organisations, serving to align strategy with execution and ensuring that every decision, Sprint, and line of code contributes to a shared purpose. These goals are not mere aspirational statements; they represent the strategic objectives that unify efforts and connect individual contributions to meaningful outcomes. In the context of agile, DevOps, and product development, understanding and committing to common goals fosters ownership, clarity, and accountability among team members, enabling distributed decision-making and reducing friction in prioritisation. This alignment is crucial for creating adaptive and high-performing systems, as it allows teams to surface misalignments early and make informed trade-offs without waiting for permission. Furthermore, the integration of tactical commitments, such as Product Goals and Sprint Goals, ensures that strategic intent is operationalised at every level of delivery. By maintaining a focus on measurable outcomes and desired impacts, organisations can avoid the pitfalls of busywork and ensure that their efforts are directed towards achieving significant results. Ultimately, common goals provide the necessary framework for teams to understand their role in the larger organisational context, making it imperative for leaders to establish and communicate these objectives clearly.</description>
			</item>
			<item>
				<title>Evidence Based Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-management/</link>
				<pubDate>Fri, 21 Mar 2025 14:44:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/evidence-based-management/</guid>
				<description>Evidence-Based Management (EBM) is a strategic approach designed to enhance organisational agility by providing a framework for assessing and improving value delivery. Unlike traditional frameworks or methodologies, EBM focuses on empirical data to inform decision-making, enabling organisations to move beyond superficial metrics and truly understand their performance. It centres on four critical areas: Current Value, which evaluates immediate value delivery; Time to Market, which measures responsiveness and speed; Ability to Innovate, which assesses the capacity for creating new value amidst existing challenges; and Unrealised Value, which identifies potential opportunities for growth. By utilising these metrics, leaders can make informed decisions about resource allocation and prioritisation, ultimately fostering a culture of continuous improvement. EBM is particularly valuable in the contexts of agile, DevOps, and product development, as it encourages a shift from output-focused practices to outcome-driven strategies. This empirical approach not only clarifies organisational goals but also provides the necessary feedback to adapt and evolve, ensuring that efforts are aligned with delivering real value rather than merely maintaining the status quo. In a landscape where many organisations struggle with agility, EBM offers a practical solution for those seeking to enhance their effectiveness and responsiveness in a complex and dynamic environment.</description>
			</item>
			<item>
				<title>Artifact</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</link>
				<pubDate>Fri, 21 Mar 2025 13:59:46 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/concepts/artifact/</guid>
				<description>An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change.</description>
			</item>
			<item>
				<title>Continuous Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/</link>
				<pubDate>Fri, 21 Mar 2025 13:37:32 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Continuous Improvement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-improvement/</guid>
				<description>Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation&amp;rsquo;s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation&amp;rsquo;s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of &amp;ldquo;Kaizen,&amp;rdquo; which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value.</description>
			</item>
			<item>
				<title>Agile Product Operating Model</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-operating-model/</link>
				<pubDate>Fri, 21 Mar 2025 09:30:34 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-operating-model/</guid>
				<description>The Agile Product Operating Model (APOM) is an operating model that integrates agile methodologies with contemporary product management principles, enabling organisations to consistently deliver value through a product-centric approach. As a specialization of the Adaptive Operating Model, APOM addresses the specific need to shift away from traditional project-based approaches, which often emphasise rigid timelines and budgets, toward continuous value delivery and responsiveness to customer feedback. This model is crucial in the context of agile, DevOps, and product development as it aligns organisational efforts around well-defined outcomes, ensuring that every product has clear boundaries, stakeholders, and measurable value. By integrating elements such as business and technology roadmaps, operational stability, and governance, APOM allows organisations to adapt swiftly to market changes while maintaining a clear connection to their strategic goals. Furthermore, it emphasises evidence-based decision-making, fostering transparency and collaboration across teams, which enhances the ability to manage and optimise product value effectively. While non-agile product operating models are possible, APOM provides the recommended approach that empowers organisations to shape their unique operating models, driving sustainable value creation in a dynamic environment.</description>
			</item>
			<item>
				<title>DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/devops/</link>
				<pubDate>Thu, 20 Mar 2025 11:04:38 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/devops/</guid>
				<description>DevOps is a philosophy that integrates people, processes, and technology to facilitate continuous value delivery in software development. Originating from the need to bridge the gap between development and operations, it emphasises collaboration and automation to enhance the quality and speed of software delivery. The core principles of DevOps prioritise flow efficiency over mere resource utilisation, advocate for rapid feedback loops to align with customer needs, and promote automation to minimise errors and delays. Additionally, it fosters shared accountability among developers, operations, and security teams, ensuring collective responsibility for product quality. DevOps encourages a culture of continuous improvement, where teams are committed to experimentation and adaptation. In practice, organisations embracing DevOps focus on eliminating silos, integrating quality and security measures early in the development process, leveraging data for informed decision-making, and automating as many processes as possible. This approach is crucial in agile and DevOps environments as it enables organisations to deliver software more reliably and efficiently, ultimately enhancing their ability to respond to market demands and customer expectations. DevOps is viewed not as a final goal but as an ongoing journey towards improved software delivery.</description>
			</item>
			<item>
				<title>Shift Left Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/</link>
				<pubDate>Mon, 17 Mar 2025 14:46:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Internal Developer Platform</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/</link>
				<pubDate>Mon, 24 Feb 2025 13:04:45 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/</guid>
				<description>An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery.</description>
			</item>
			<item>
				<title>Acceptance Test Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/</guid>
				<description>Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users.</description>
			</item>
			<item>
				<title>Agile Frameworks</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/</guid>
				<description>Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape.</description>
			</item>
			<item>
				<title>Agile Philosophy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-philosophy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-philosophy/</guid>
				<description>Agile philosophy is a mindset that emphasises flexibility, collaboration, and a focus on customer needs in the realm of product development. Originating from the desire to improve traditional project management approaches, it serves as a foundational ethos that guides teams beyond specific methodologies like Scrum or Kanban. This philosophy is vital as it promotes incremental and iterative value delivery, enabling organisations to swiftly adapt to evolving market conditions and customer feedback. By fostering a culture of continuous improvement and learning, Agile philosophy allows teams to refine their processes over time, ensuring ongoing effectiveness and relevance. It encourages cross-functional collaboration, dismantling silos and fostering shared ownership of outcomes, which enhances team dynamics and aligns organisational objectives with customer expectations. Furthermore, Agile philosophy nurtures an environment conducive to experimentation and innovation, empowering teams to make data-driven decisions that lead to superior products and services. Its emphasis on adaptability and responsiveness distinguishes Agile philosophy from other frameworks, making it an essential component in achieving organisational excellence and resilience.</description>
			</item>
			<item>
				<title>Agile Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning/</guid>
				<description>Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development.</description>
			</item>
			<item>
				<title>Agile Planning Tools</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-planning-tools/</guid>
				<description>Agile Planning Tools are vital resources that support effective backlog management, forecasting, and collaboration within Agile teams. Originating from the principles of Agile methodology, these tools enable teams to visualise their work, prioritise tasks, and monitor progress in real-time, ensuring alignment and focus on delivering value. Their importance lies in enhancing predictability and sustainability in value delivery, allowing teams to make informed decisions based on empirical data, which fosters a culture of continuous improvement and adaptability in dynamic environments. By providing a structured approach to planning, Agile Planning Tools help teams anticipate challenges and respond to changing requirements, streamlining workflows and promoting a collaborative atmosphere. Unlike Agile Project Management or Agile Product Management, which target specific project execution or product lifecycle aspects, these tools form the foundational layer that underpins all Agile practices. They facilitate not just task management but also the creation of an environment conducive to team innovation and customer satisfaction through effective planning and execution. Integrating Agile Planning Tools into daily operations enhances organisational agility and resilience, ultimately leading to improved outcomes and sustained success.</description>
			</item>
			<item>
				<title>Agile Strategy</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-strategy/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-strategy/</guid>
				<description>Agile Strategy is a holistic framework that aligns an organisation&amp;rsquo;s vision with its operational execution and adaptability, enabling teams to consistently and sustainably deliver value. Originating from the principles of agile methodologies, this approach transcends individual practices by promoting the systemic integration of agile values throughout the organisation. It is essential for fostering an environment that encourages responsiveness to change, continuous innovation, and a strong focus on customer needs. By cultivating a culture of collaboration and transparency, Agile Strategy helps dismantle silos and enhances cross-functional teamwork. It advocates for the use of metrics and feedback loops to guide decision-making, allowing teams to adapt their strategies based on real-time insights. This level of adaptability is vital in today&amp;rsquo;s rapidly evolving market, where the capacity to pivot swiftly can significantly influence success. Furthermore, Agile Strategy is about embedding agility into the organisational culture, ensuring that it becomes a sustained capability rather than a temporary initiative. This long-term focus on aligning strategic objectives with operational execution equips organisations to navigate complexity and uncertainty more effectively, ultimately leading to improved customer satisfaction and enhanced business resilience.</description>
			</item>
			<item>
				<title>Agile Values and Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-values-and-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-values-and-principles/</guid>
				<description>Agile Values and Principles are fundamental guidelines that underpin effective Agile practices, serving as a framework for teams to consistently and sustainably deliver value. Originating from the Agile Manifesto, these values prioritise human interactions and collaboration over rigid processes and tools, fostering an environment where customer feedback and adaptability are central. Their importance lies in their ability to enable organisations to respond swiftly to change, ensuring that products remain relevant and aligned with customer needs. By promoting a culture of continuous improvement, Agile encourages teams to regularly assess their processes and outcomes, which enhances efficiency and drives innovation. This systemic approach builds organisational resilience, equipping teams to navigate the complexities and uncertainties of modern product development. By embedding these values into the organisational culture, teams gain the autonomy to self-organise and make informed decisions, maintaining a focus on high-quality outcomes. Ultimately, embracing Agile Values and Principles transcends a mere tactical adjustment; it acts as a strategic enabler that transforms operational dynamics, fostering a mindset oriented towards long-term success and value creation, thereby driving meaningful change and sustainable growth across the organisation.</description>
			</item>
			<item>
				<title>Asynchronous Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/asynchronous-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/asynchronous-development/</guid>
				<description>Asynchronous Development is a collaborative approach that enables team members to work independently and at different times, rather than depending on real-time interactions. This method is particularly advantageous for distributed teams, as it accommodates diverse time zones and personal schedules, facilitating continuous progress without the limitations of synchronous communication. By utilising tools and practices that support asynchronous workflows, teams can improve their efficiency and flexibility, leading to more predictable and sustainable value delivery. This concept is vital in contemporary product development, where rapid adaptation and responsiveness are essential. Asynchronous Development creates an environment where team members can contribute insights and work at their own pace, minimising bottlenecks caused by waiting for others. It fosters a culture of ownership and accountability, encouraging individuals to take responsibility for their tasks while remaining aligned with team objectives. Additionally, this approach aligns with Lean and Agile principles, promoting continuous improvement and learning. By allowing teams to operate asynchronously, organisations can better manage complexity and enhance collaboration, ensuring consistent value delivery to customers without the friction of traditional synchronous methods. This systemic shift not only boosts productivity but also nurtures a more engaged and motivated workforce, ultimately driving long-term success and innovation.</description>
			</item>
			<item>
				<title>Automated Testing</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/automated-testing/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>
			<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>Backlog Refinement</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/backlog-refinement/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/backlog-refinement/</guid>
				<description>Backlog Refinement is a fundamental practice within Agile methodologies that focuses on ensuring the product backlog is clearly defined, prioritised, and prepared for execution. Originating from the need for effective collaboration between product owners and development teams, this ongoing process involves clarifying requirements, estimating effort, and adjusting priorities based on evolving insights and stakeholder feedback. The importance of Backlog Refinement lies in its ability to enhance focus and alignment on delivering value, thereby enabling teams to deliver outcomes predictably and sustainably. By regularly refining the backlog, teams can reduce risks associated with ambiguity and miscommunication, facilitating smoother sprint planning and execution. This practice promotes a culture of continuous improvement, allowing teams to adapt to changing circumstances and customer needs while maintaining momentum. Additionally, it supports long-term planning by prioritising the most valuable items, optimising resource allocation, and enhancing overall productivity. By integrating Backlog Refinement into their workflows, organisations can foster a more responsive and agile environment, leading to improved product outcomes and greater stakeholder satisfaction. This systemic approach not only streamlines the development process but also encourages a proactive mindset among team members, empowering them to take ownership of their work and align with the organisation&amp;rsquo;s strategic objectives.</description>
			</item>
			<item>
				<title>Behaviour Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/behaviour-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/behaviour-driven-development/</guid>
				<description>Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality.</description>
			</item>
			<item>
				<title>Collaboration Tools</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/collaboration-tools/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/collaboration-tools/</guid>
				<description>Collaboration tools are vital platforms that enhance communication and coordination among Agile teams, enabling improved effectiveness and efficiency in their workflows. Originating from the need to streamline processes in product development, these tools facilitate real-time information sharing, progress tracking, and task management, thereby reducing friction and fostering transparency. Their importance is underscored by their role in promoting a culture of continuous improvement and learning, as they provide a shared space for feedback and discussion essential for iterative development and innovation. Regular engagement through these tools strengthens team relationships and cultivates a sense of shared purpose, which in turn boosts overall performance. Furthermore, collaboration tools are integral to the systemic nature of Agile practices, aligning with Lean and DevOps principles by minimising waste and allowing teams to concentrate on delivering high-quality products. By embedding these tools into their workflows, organisations can foster an environment that supports agility and responsiveness, ensuring that teams are well-prepared to adapt to changing customer needs and market dynamics, ultimately driving sustained value creation.</description>
			</item>
			<item>
				<title>Continuous Integration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/</guid>
				<description>Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development.</description>
			</item>
			<item>
				<title>Continuous Learning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/continuous-learning/</guid>
				<description>Continuous Learning is the practice of nurturing a growth mindset and facilitating knowledge sharing within teams to achieve ongoing improvement. Originating from the need to adapt to rapidly changing environments, this concept underscores the significance of learning from both successes and failures to enhance skills, processes, and products. It is crucial in agile and DevOps contexts, as it enables teams to respond swiftly to challenges, ensuring consistent and sustainable value delivery. By embedding continuous learning into an organisation&amp;rsquo;s culture, teams become more resilient and innovative, fostering an environment that encourages experimentation and reflection. This approach not only refines practices and boosts performance but also integrates insights from diverse sources to inform strategic decision-making. Unlike Continuous Improvement, which focuses on incremental changes, Continuous Learning adopts a broader perspective, enhancing individual competencies and strengthening team dynamics. It promotes active knowledge sharing, leading to collective intelligence that drives superior outcomes. Continuous Learning is a long-term commitment rather than a one-off initiative, essential for organisations to remain competitive and relevant in a fast-evolving landscape. By prioritising this practice, organisations can cultivate a culture of excellence that enhances value delivery and customer satisfaction across all operations.</description>
			</item>
			<item>
				<title>Cross Functional Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/</guid>
				<description>Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise.</description>
			</item>
			<item>
				<title>Customer Feedback Loops</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/customer-feedback-loops/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/customer-feedback-loops/</guid>
				<description>Customer feedback loops are critical processes that enable the integration of user insights into product development, ensuring that offerings are closely aligned with actual user needs and preferences. Originating from agile methodologies, these loops involve the systematic collection and analysis of customer feedback, fostering a culture of responsiveness and adaptability within teams. Their importance lies in the ability to drive predictable and sustainable value delivery, allowing teams to make informed decisions based on real user experiences rather than assumptions. This reduces the risk of misalignment between product features and market demands, supporting a long-term vision where learning from customer interactions is central to the development cycle. Additionally, customer feedback loops enhance the understanding of user behaviour, informing strategic planning and prioritisation. By embedding these mechanisms into the organisational structure, teams promote continuous learning and improvement, leading to increased customer satisfaction and loyalty. This proactive approach not only mitigates potential failures but also positions organisations to capitalise on new opportunities, ensuring competitiveness in a rapidly changing market environment.</description>
			</item>
			<item>
				<title>Customer Retention</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/customer-retention/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/customer-retention/</guid>
				<description>Customer retention encompasses the strategies and practices that organisations implement to maintain user engagement with their products or services over time, thereby minimising customer churn. This concept is vital as it significantly influences an organisation&amp;rsquo;s sustainability and profitability. By prioritising customer retention, teams can consistently deliver value, fostering loyalty and encouraging repeat business. Effective retention strategies often incorporate continuous feedback loops, enabling teams to adapt and enhance their offerings based on user needs and preferences, which aligns with Agile principles that emphasise responsiveness to change and customer collaboration. Retaining customers not only stabilises revenue but also lowers the costs associated with acquiring new customers, making it a more efficient growth strategy. Furthermore, a strong focus on customer retention promotes a culture of long-term thinking within teams, encouraging the development of relationships over mere transactional interactions. This systemic emphasis on value delivery allows organisations to thrive in competitive markets, ensuring they remain relevant and responsive to changing customer expectations. By prioritising retention, teams can establish a sustainable business model that supports ongoing innovation and improvement, ultimately leading to increased customer satisfaction and loyalty.</description>
			</item>
			<item>
				<title>Customer Satisfaction</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/customer-satisfaction/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/customer-satisfaction/</guid>
				<description>Customer satisfaction is the assessment of how effectively a product or service meets or surpasses user expectations, serving as a crucial indicator of product-market fit and a key feedback mechanism for teams aiming to deliver value. This concept originates from the need to understand user experiences and is integral to fostering a customer-centric culture within organisations. By prioritising customer satisfaction, teams can adapt and innovate based on genuine user feedback, which helps identify pain points and opportunities for enhancement, leading to iterative improvements that align with user needs. In the context of agile, DevOps, and product development, customer satisfaction is vital for long-term success, promoting a proactive approach to quality and responsiveness in a rapidly evolving market. Emphasising this principle enables organisations to establish a resilient framework that supports continuous improvement and value delivery, ensuring that customer satisfaction transcends being merely a metric and becomes a foundational element that influences all aspects of product development and delivery.</description>
			</item>
			<item>
				<title>Cycle Time</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/</guid>
				<description>Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success.</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>Deployment Strategies</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Empirical Process Control</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/empirical-process-control/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/empirical-process-control/</guid>
				<description>Empirical Process Control is a key principle that focuses on making decisions grounded in observation and experimentation rather than assumptions. Originating from methodologies such as Agile, Lean, and DevOps, it empowers teams to refine their processes and outputs through ongoing inspection and transparency. This reliance on real data and feedback enables organisations to discern effective practices from ineffective ones, fostering a culture of continuous learning and improvement. By adopting this approach, teams can deliver value in a predictable and sustainable manner, adjusting their strategies based on actual performance rather than theoretical frameworks. It promotes a mindset of experimentation, where hypotheses are tested in real-world scenarios, leading to informed decisions that enhance product quality and customer satisfaction. Beyond being a tactical tool, Empirical Process Control serves as a long-term enabler of organisational agility, creating an environment where teams can swiftly adapt to changing conditions and remain aligned with customer needs and market dynamics. In today&amp;rsquo;s fast-paced development landscape, the ability to pivot based on evidence is crucial for success. By integrating empirical practices into their workflows, organisations can cultivate a more resilient and responsive operational model that prioritises value delivery and continuous improvement.</description>
			</item>
			<item>
				<title>Engineering Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/engineering-practices/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/engineering-practices/</guid>
				<description>Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software&amp;rsquo;s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance.</description>
			</item>
			<item>
				<title>Experimentation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/experimentation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/experimentation/</guid>
				<description>Experimentation is a fundamental practice within agile workflows that utilises hypothesis-driven methods to test ideas and validate assumptions. Originating from the need to systematically address uncertainties, this approach enables teams to make informed decisions based on empirical evidence rather than relying solely on intuition. The importance of experimentation is underscored by its ability to facilitate predictable and sustainable value delivery, fostering a culture where failure is perceived as a learning opportunity that drives continuous improvement and resilience. Through iterative testing and feedback loops, teams can refine their products and processes, ensuring they align with customer needs and organisational objectives. Furthermore, experimentation promotes long-term systemic change by integrating a scientific mindset into the organisational culture, enhancing collaboration among cross-functional teams and boosting engagement as team members witness the direct impact of their efforts. By prioritising experimentation, organisations can create an environment that values learning and adaptability, which is essential for effective and innovative product development in today&amp;rsquo;s complex and rapidly changing landscape. This practice serves not just as a tactic but as a foundational element that influences how teams operate and evolve.</description>
			</item>
			<item>
				<title>Forecasting</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/forecasting/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/forecasting/</guid>
				<description>Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation.</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>
			<item>
				<title>Hypothesis Driven Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/hypothesis-driven-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/hypothesis-driven-development/</guid>
				<description>Hypothesis Driven Development is a structured methodology that utilises experimentation and validated learning to guide product decisions. Originating from the need to make informed choices based on user needs and behaviours, this approach enables teams to formulate hypotheses and design experiments that test these assumptions in real-world contexts. Its importance lies in enhancing predictability and sustainability in delivering value, as it allows organisations to gather actionable data and insights that inform product development, thereby reducing reliance on intuition. By continuously testing and iterating on ideas, teams can swiftly adapt to evolving market conditions and user feedback, minimising the risk of developing products that fail to meet customer expectations. This methodology fosters a culture of learning and experimentation, encouraging teams to embrace uncertainty and view setbacks as opportunities for growth. In contrast to traditional development methods that often depend on extensive upfront planning, Hypothesis Driven Development promotes an agile mindset where learning and adaptation are central to the process. This long-term, systemic approach not only leads to improved product outcomes but also empowers teams to innovate and effectively tackle emerging challenges, ultimately contributing to organisational success through a more profound understanding of customer value and market dynamics.</description>
			</item>
			<item>
				<title>Lean Principles</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lean-principles/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/lean-principles/</guid>
				<description>Lean Principles are a methodology aimed at minimising waste and maximising value through iterative learning and continuous improvement, primarily used in product development processes. Originating from manufacturing practices, these principles are now widely adopted across various sectors to enhance organisational efficiency and responsiveness. The importance of Lean Principles lies in their ability to foster a culture of experimentation and feedback, enabling teams to identify and eliminate non-value-adding activities, streamline workflows, and optimise resource utilisation. By focusing on value delivery, Lean ensures that all actions align with customer needs, promoting sustainable product development. Techniques such as value stream mapping are employed to visualise the flow of information and materials, helping to identify bottlenecks and areas for improvement. This comprehensive approach not only enhances current processes but also establishes a foundation for long-term agility and adaptability. Unlike Agile frameworks that may concentrate on iterative cycles, Lean Principles advocate for a holistic perspective, integrating insights from various methodologies to create a cohesive strategy for continuous improvement. This enables organisations to effectively respond to changing market demands while maintaining a commitment to delivering high-quality products that meet customer expectations. By embedding Lean thinking into the organisational culture, teams can foster an environment of ongoing learning and innovation, ultimately driving sustained success and resilience in a competitive landscape.</description>
			</item>
			<item>
				<title>Lean Product Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lean-product-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/lean-product-development/</guid>
				<description>Lean Product Development is a methodology that centres on minimising waste and maximising learning throughout the product creation process, drawing from Lean principles that prioritise efficiency and value delivery by eliminating non-value-adding activities. This approach is utilised to foster a culture of continuous improvement, enabling teams to swiftly adapt to changing market demands and customer feedback, thereby ensuring the development of relevant and high-quality products. By empowering cross-functional teams to collaborate effectively and employing tools like Kanban to visualise workflows and identify bottlenecks, Lean Product Development promotes iterative cycles of experimentation that allow for the validation of assumptions and necessary pivots. This is particularly vital in today’s fast-paced environment, where responsiveness is key. The focus on systemic thinking aligns all aspects of product development with organisational goals, encouraging a sustainable approach to innovation. By integrating Lean practices, organisations can enhance their capacity to deliver value predictably, cultivating a culture that values learning and adaptability over rigid processes. This long-term emphasis on efficiency and responsiveness equips teams to excel in a competitive landscape, ultimately leading to improved outcomes for both the organisation and its customers.</description>
			</item>
			<item>
				<title>Lean Thinking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/lean-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/lean-thinking/</guid>
				<description>Lean Thinking is a methodology aimed at maximising value by minimising waste within organisational processes, originating from manufacturing practices and now widely applied across various sectors. It focuses on understanding customer needs and aligning workflows to efficiently deliver products and services that meet those needs. The importance of Lean Thinking lies in its ability to foster a culture of continuous improvement, where teams are encouraged to identify non-value-adding activities, streamline operations, and enhance productivity. This approach is not solely about cost reduction; rather, it aims to create sustainable systems that support long-term value delivery. By adopting Lean principles, organisations can respond more swiftly to changing market demands while ensuring high quality and customer satisfaction. Furthermore, integrating Lean practices leads to greater predictability in delivery cycles, reduced lead times, and improved collaboration among cross-functional teams. This systemic approach empowers individuals at all levels to engage in process enhancements, cultivating a sense of ownership that drives innovation and resilience. Ultimately, Lean Thinking transforms organisational operations, enabling them to remain competitive and responsive in a rapidly evolving landscape.</description>
			</item>
			<item>
				<title>Minimum Viable Product</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/minimum-viable-product/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/minimum-viable-product/</guid>
				<description>Minimum Viable Product (MVP) is a fundamental concept in product development that emphasises the creation of a product version with just enough features to meet the needs of early adopters and facilitate feedback for subsequent iterations. Originating from lean startup methodologies, the MVP approach enables teams to quickly test hypotheses and validate market assumptions, thereby minimising the risk associated with investing substantial resources in untested ideas. This strategy not only accelerates product launches but also fosters a culture of experimentation and learning, which is essential for organisations seeking sustainable innovation. By promoting cross-functional collaboration, teams can collectively determine the essential features of the product, enhancing its relevance and aligning team members around common objectives. The MVP framework is not solely focused on speed; it establishes a basis for continuous improvement and value delivery, allowing organisations to remain responsive to evolving market conditions and customer preferences. Ultimately, this approach supports long-term success and resilience in a competitive environment by ensuring that products are developed in a manner that maximises value over time.</description>
			</item>
			<item>
				<title>Operational Practices</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/operational-practices/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/operational-practices/</guid>
				<description>Operational Practices refer to the techniques and strategies that organisations implement to improve their operational efficiency and delivery capabilities. Originating from methodologies such as Lean, Agile, and DevOps, these practices are utilised to streamline workflows, minimise waste, and optimise resource allocation. Their importance lies in fostering a culture of continuous improvement, enabling teams to swiftly adapt to changing demands while ensuring high-quality outputs. By establishing clear processes and enhancing collaboration, Operational Practices empower teams to make data-driven decisions, which collectively enhance performance and customer satisfaction. This systemic approach ensures that operational improvements are ingrained within the organisational culture, promoting resilience and adaptability rather than being merely reactive. Furthermore, Operational Practices align team efforts with strategic goals, ensuring that every action contributes to the organisation&amp;rsquo;s overarching mission. By prioritising these practices, organisations can create an environment conducive to innovation and consistent value delivery, ultimately leading to a more agile and responsive structure capable of navigating the complexities of modern product development and market dynamics.</description>
			</item>
			<item>
				<title>Portfolio Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/portfolio-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/portfolio-management/</guid>
				<description>Portfolio Management is a strategic methodology that aligns an organisation&amp;rsquo;s investments with its overarching objectives, ensuring effective resource allocation to maximise value delivery. Originating from the need to continuously assess and prioritise projects and initiatives, this approach enables teams to concentrate on the most impactful work. Its importance lies in fostering a culture of transparency and accountability, as it provides a data-driven framework for decision-making that empowers teams to deliver value predictably and sustainably, while also reducing waste and enhancing overall efficiency. Unlike Agile Project Management, which focuses on individual projects, Portfolio Management adopts a holistic perspective, considering the interdependencies and potential synergies among multiple initiatives. By embedding Portfolio Management within the organisational structure, companies can develop a long-term vision that promotes innovation and adaptability. This systemic approach not only drives performance but also cultivates a resilient organisational culture, equipping teams to effectively navigate complexity and uncertainty. The emphasis on continuous improvement and learning ensures that organisations remain competitive and responsive in a rapidly changing environment, ultimately enhancing their ability to deliver consistent value.</description>
			</item>
			<item>
				<title>Product Discovery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-discovery/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-discovery/</guid>
				<description>Product Discovery is a vital process in product development that focuses on identifying customer needs and defining valuable product features that align with those needs. Originating from the necessity to ensure that teams deliver solutions that resonate with users, this phase allows organisations to validate assumptions, explore market opportunities, and refine their product vision. The importance of Product Discovery lies in its ability to enable teams to deliver value predictably and sustainably. By employing techniques such as user interviews, prototyping, and iterative testing, teams can gather insights that inform decision-making and mitigate the risk of developing products that fail to meet market demands. This process fosters a culture of experimentation and learning, empowering organisations to adapt swiftly to evolving customer preferences and technological changes. Unlike Agile Planning or Product Management, which concentrate on execution and delivery, Product Discovery is exploratory and systemic, emphasising the understanding of the underlying reasons for product features. This long-term approach not only enhances customer satisfaction but also drives innovation and competitive advantage, making Product Discovery an essential practice for organisations dedicated to creating meaningful products that endure over time.</description>
			</item>
			<item>
				<title>Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/product-management/</guid>
				<description>Product Management is a strategic discipline focused on aligning customer needs, business objectives, and technical feasibility to maximise value delivery in product development. Originating from Agile methodologies, particularly within the Scrum framework, the role of the Product Owner is central to this discipline, emphasising accountability for value rather than mere output. This approach is crucial in ensuring that product teams prioritise impactful features over an extensive list of functionalities, thereby avoiding the pitfalls of feature bloat. Effective Product Management operates within a social system, requiring collaboration with stakeholders, executives, and developers while continuously engaging with users to maintain a compelling product vision. The use of evidence-based management is vital, as it allows Product Managers to make informed decisions based on measurable metrics rather than vanity metrics. Customer feedback is treated as a strategic asset, necessitating discernment in its application to avoid misalignment with product goals. Additionally, technical empathy is essential for understanding the feasibility and risks associated with product strategies, ensuring that desirability, viability, and feasibility are balanced. Clear boundaries of authority and accountability are necessary for effective collaboration, with Product Managers defining the &amp;lsquo;what&amp;rsquo; and &amp;lsquo;why&amp;rsquo;, while developers focus on the &amp;lsquo;how&amp;rsquo;. Ultimately, Product Management is about optimising value through informed decision-making, fostering a culture of learning, and prioritising outcomes over outputs, making it a critical function in Agile and DevOps environments.</description>
			</item>
			<item>
				<title>Product Owner</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/</guid>
				<description>The Product Owner is a key accountability within the Scrum framework, tasked with maximising the value of the product produced by the Scrum Team. This role encompasses more than just managing the product backlog; it involves making strategic decisions that align the product vision with customer needs and business objectives. The importance of the Product Owner lies in their responsibility for outcomes rather than merely tasks, as they prioritise features that balance immediate requirements with long-term goals. By optimising the product backlog and adapting to stakeholder feedback and market changes, the Product Owner significantly influences the product&amp;rsquo;s success and the team&amp;rsquo;s effectiveness. They foster collaboration between stakeholders and the development team, ensuring transparency and alignment across the organisation, which enhances decision-making and workflow efficiency. This accountability is crucial for a value-driven approach to product development, as the Product Owner must navigate competing priorities and ensure the product delivers measurable business value. Their strategic decision-making role is distinct from that of the Scrum Master or Development Team, as they continuously assess the product&amp;rsquo;s value and make evidence-based decisions to guide its evolution. By embedding this accountability within the organisational culture, the Product Owner helps maintain alignment with broader strategic goals, ultimately contributing to the consistency of value delivery and the successful completion of product iterations.</description>
			</item>
			<item>
				<title>Product Validation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-validation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-validation/</guid>
				<description>Product validation is the process of testing product ideas with actual users to confirm that they meet market demands and provide real customer value. This practice is essential for organisations seeking to develop products that connect with their target audience, as it reduces the risk of investing in features or solutions that do not meet user expectations. By involving users early and frequently, teams can collect feedback that informs design and functionality, facilitating iterative enhancements that improve product-market fit. The importance of product validation lies in its capacity to enable teams to deliver value in a predictable and sustainable manner, fostering a culture of experimentation and learning where assumptions are validated through real-world data rather than theoretical models. This not only speeds up the development process but also increases the likelihood of product success in a competitive environment. Additionally, product validation is a long-term, systemic practice that aligns well with agile methodologies, lean principles, and DevOps practices. It promotes cross-functional collaboration and empowers teams to make informed decisions based on user insights, ultimately driving continuous improvement and innovation. By prioritising validation, organisations can establish a strong feedback loop that enhances their adaptability and resilience in a constantly changing market.</description>
			</item>
			<item>
				<title>Release Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/release-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/release-management/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Remote Working</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/remote-working/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/remote-working/</guid>
				<description>Remote working is a practice that enables teams to collaborate and deliver value from various locations, moving beyond the constraints of a physical office. This approach has gained prominence in today&amp;rsquo;s technology-driven landscape, allowing organisations to access a wider talent pool, improve employee satisfaction, and sustain productivity irrespective of geographical limitations. By utilising digital collaboration tools and nurturing a culture of trust and accountability, remote working empowers teams to function effectively, adapting quickly to market changes and customer demands. Its systemic nature fosters sustainable practices through continuous communication and feedback loops, which are crucial for iterative development. This flexibility supports agile methodologies and aligns with lean principles by reducing waste and optimising resource use. Additionally, remote working enhances team members&amp;rsquo; sense of ownership, boosting engagement and motivation. As teams embrace this model, they cultivate resilience and agility, equipping them to tackle challenges and seize opportunities in a dynamic environment. Ultimately, the emphasis on delivering value ensures that organisations can thrive in a competitive landscape while promoting innovation and collaboration among dispersed teams.</description>
			</item>
			<item>
				<title>Self Organisation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/self-organisation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/self-organisation/</guid>
				<description>Self-organisation is the capacity of teams to independently manage their work, make decisions, and adapt to evolving circumstances without external oversight. Originating from principles in Agile, Lean, and DevOps methodologies, this concept is vital for fostering a culture of ownership and accountability within teams. By empowering individuals to take initiative, self-organisation enhances collaboration and innovation, leading to improved problem-solving and value delivery. In such environments, teams leverage their collective skills and insights, which boosts engagement and drives continuous improvement through experimentation and learning from failures. This autonomy not only enhances productivity but also contributes to long-term organisational resilience, enabling teams to thrive in dynamic contexts. Unlike traditional hierarchical structures, self-organisation aligns with the need for adaptability and responsiveness, creating a framework that optimises workflows and ensures that organisations remain competitive and responsive to market demands. Ultimately, this approach cultivates an environment where innovation can flourish, equipping teams to navigate complexity with confidence and agility.</description>
			</item>
			<item>
				<title>Software Development</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/software-development/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/software-development/</guid>
				<description>Software Development refers to the systematic techniques and methodologies used to create high-quality software solutions that align with user needs and business objectives. Originating from various practices such as Agile, Lean, and DevOps, it aims to improve collaboration, efficiency, and adaptability within development teams. This approach is vital as it allows organisations to deliver value in a predictable and sustainable manner, fostering a culture of continuous improvement and responsiveness to change. By emphasising iterative development, teams can swiftly adapt to feedback and changing requirements, ensuring the software remains relevant and effective. Additionally, the focus on automation, testing, and integration mitigates the risk of defects and accelerates delivery cycles, leading to more frequent releases and increased customer satisfaction. Software Development also encourages a comprehensive view of the software lifecycle, promoting cross-functional collaboration and knowledge sharing among team members. This long-term, systemic approach not only enhances software quality but also nurtures an innovative environment, enabling organisations to stay competitive in a fast-evolving market. The incorporation of evidence-based management principles further aids informed decision-making, equipping teams to effectively navigate complexity and uncertainty. By prioritising these practices, organisations can secure a sustainable competitive advantage through improved software development capabilities that align with their strategic goals and customer expectations.</description>
			</item>
			<item>
				<title>Team Collaboration</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/team-collaboration/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/team-collaboration/</guid>
				<description>Team collaboration is the practice of enhancing teamwork, communication, and shared ownership among team members to achieve high performance. Originating from the need for effective interaction within teams, it is crucial for enabling organisations to deliver value in a predictable and sustainable manner. By fostering a culture of openness and trust, team collaboration empowers individuals to contribute their ideas and skills, thereby enhancing problem-solving capabilities and accelerating decision-making. This collaborative approach helps break down silos, facilitating the free flow of knowledge and expertise across functions, which in turn improves efficiency and adaptability in response to changing requirements and customer feedback. The long-term advantages of strong collaboration include increased innovation, higher employee engagement, and improved overall performance, aligning teams more closely with organisational goals and customer needs. Furthermore, the use of effective collaboration tools and practices is essential in agile, lean, and DevOps environments, supporting seamless communication and coordination. Ultimately, team collaboration serves as a foundational element that drives continuous improvement and value delivery, making it vital for modern product development and organisational success.</description>
			</item>
			<item>
				<title>Test Automation</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/</guid>
				<description>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.</description>
			</item>
			<item>
				<title>Value Stream Mapping</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-mapping/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-mapping/</guid>
				<description>Value Stream Mapping is a visual tool designed to analyse and optimise workflows within an organisation by focusing on the flow of materials and information necessary for delivering a product or service. This method involves mapping each step of the process to identify inefficiencies, bottlenecks, and areas of waste, thereby enabling teams to streamline operations and enhance value delivery. Its importance lies in facilitating predictable and sustainable value delivery, empowering teams to make informed decisions based on empirical data, and allowing for adjustments that improve overall performance. By aligning processes with customer needs, Value Stream Mapping ensures that every step adds value towards the end goal. It is not a one-time exercise but a long-term, systemic practice that promotes ongoing reflection and adaptation, helping teams remain agile in response to changing demands and market conditions. This ultimately leads to improved customer satisfaction and organisational resilience. The insights gained from Value Stream Mapping can drive strategic initiatives and foster a culture of collaboration and shared understanding across cross-functional teams, which is essential for achieving sustained success in modern product development.</description>
			</item>
			<item>
				<title>Working Software</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/working-software/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/working-software/</guid>
				<description>Working Software is a fundamental artifact in Agile, Scrum, and Lean frameworks, serving as the tangible output of a team&amp;rsquo;s efforts throughout the development process. It emerges from iterative development cycles and acts as a demonstration of progress and value delivery. In Scrum, working software is the primary success metric for each Sprint, encapsulated in the Increment artifact, which is subject to inspection and adaptation based on stakeholder feedback. The Definition of Done ensures that the software meets established quality criteria, making it valuable and ready for release. The importance of working software lies in its ability to provide a concrete measure of progress, aligning teams and stakeholders around completed work and remaining tasks. It transcends mere code, representing deliverables that address real-world needs and customer expectations, thereby maintaining a focus on value delivery. In agile methodologies, the emphasis on working software fosters continuous feedback and improvement, enabling teams to release increments iteratively and adapt to evolving requirements. This focus enhances collaboration, increases transparency, and drives ongoing improvement within organisations. Ultimately, working software is not solely about technical execution; it is about consistently delivering value, responding to customer needs, and ensuring long-term sustainability, thereby contributing to customer satisfaction, innovation, and overall business success.</description>
			</item>
			<item>
				<title>Agile Product Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-management/</guid>
				<description>Agile Product Management is a methodology that prioritises maximising product value by aligning organisational strategy with customer needs through iterative and incremental delivery processes. Originating from Agile principles, this approach allows teams to swiftly adapt to changing market demands while ensuring that product development is informed by real user feedback. Unlike Agile Project Management, which focuses on project execution within Agile frameworks, Agile Product Management encompasses the entire product lifecycle, from discovery to delivery, fostering a culture of collaboration among cross-functional teams. This systemic approach to value delivery emphasises not only immediate outputs but also the long-term evolution of products to meet shifting user requirements. By enabling organisations to maintain a competitive edge and adapt to disruptions, Agile Product Management is essential for driving sustained growth and innovation. It enhances organisational agility and resilience, empowering teams to thrive in dynamic environments and ultimately leading to improved customer satisfaction and retention.</description>
			</item>
			<item>
				<title>Application Lifecycle Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/</guid>
				<description>Application Lifecycle Management (ALM) is the systematic approach to managing software applications throughout their entire lifecycle, from initial development to eventual retirement. Originating from the need for structured processes in software development, ALM integrates various practices, tools, and team collaboration to streamline workflows and enhance communication. Its importance lies in its ability to provide organisations with a comprehensive view of application development, aligning technical efforts with business goals while remaining adaptable to evolving requirements. By implementing methodologies such as continuous integration and continuous delivery, ALM fosters rapid feedback and iterative enhancements, which are critical in dynamic environments. This approach not only reduces deployment risks but also cultivates a culture of accountability and transparency within teams. Furthermore, ALM aids organisations in effectively managing their application portfolios, ensuring optimal resource allocation and proactive technical debt management. This long-term focus is essential for driving innovation and maintaining a competitive edge, as it allows teams to concentrate on delivering high-quality software that satisfies user demands and contributes to overall business success. The synergy between ALM and frameworks like Agile and DevOps amplifies its impact, establishing a solid foundation for ongoing improvement and value creation.</description>
			</item>
			<item>
				<title>Azure DevOps</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/</guid>
				<description>Azure DevOps is a comprehensive suite of tools developed by Microsoft that supports continuous integration and continuous delivery (CI/CD), enhances collaboration, and streamlines agile project management. It encompasses various functionalities, including Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for automating builds and deployments, and Azure Test Plans for managing testing efforts. This platform is crucial for organisations seeking to deliver value in a predictable and sustainable manner, as it promotes a culture of collaboration and transparency among teams. By providing a unified environment for development and operations, Azure DevOps facilitates the adoption of best practices in agile methodologies and DevOps principles, ensuring efficient software delivery that is responsive to evolving business needs. Its systemic approach encourages continuous improvement and learning, enabling organisations to swiftly adapt to market demands while upholding high-quality standards. The integration of tools within Azure DevOps mitigates silos, enhances communication, and fosters a shared understanding of project objectives, ultimately leading to improved outcomes and a culture of innovation. This capability is vital for organisations aiming to achieve operational excellence and maintain a competitive advantage in a fast-changing landscape.</description>
			</item>
			<item>
				<title>Business Agility</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/business-agility/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/business-agility/</guid>
				<description>Business Agility is the capacity of an organisation to swiftly adapt to market fluctuations, customer needs, and new opportunities while prioritising value delivery. Originating from the need for organisations to remain competitive in a fast-paced environment, this concept is vital as it enables teams to foster continuous innovation, streamline processes, and improve cross-functional collaboration. Business Agility extends beyond merely implementing Agile methodologies; it involves a comprehensive approach that incorporates principles from Lean, DevOps, and continuous improvement. This integrated perspective allows organisations to optimise workflows, shorten lead times, and boost customer satisfaction. By cultivating a culture that values flexibility, experimentation, and learning, organisations can quickly adjust their strategies based on feedback and data insights. The long-term advantages of embracing Business Agility include enhanced resilience, sustained competitive edge, and consistent delivery of high-quality products and services. By embedding agility into their core operations, organisations can proactively navigate change, drive innovation, and achieve strategic objectives, ultimately leading to greater value creation and organisational success.</description>
			</item>
			<item>
				<title>Complexity Thinking</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/complexity-thinking/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/complexity-thinking/</guid>
				<description>Complexity Thinking is an approach that utilises principles from complexity science to address the intricate dynamics present within organisations and systems. It acknowledges that many challenges faced by organisations are complex rather than merely complicated, characterised by unpredictable interactions and emergent behaviours. This perspective is vital for teams striving to deliver value in a predictable and sustainable manner, as it promotes a deeper understanding of the interdependencies within systems. By employing Complexity Thinking, teams can better foresee how changes in one area may have cascading effects throughout the organisation, leading to unintended consequences. This understanding nurtures a culture of adaptability, enabling teams to respond effectively to changing circumstances rather than relying on linear planning. It empowers organisations to embrace uncertainty, fostering experimentation and learning, which are critical for innovation. Furthermore, Complexity Thinking aligns with Agile and Lean principles by advocating for iterative processes and continuous feedback loops, shifting the focus from isolated tasks to the overall health and performance of the system. This systemic approach not only improves decision-making but also builds resilience, ensuring organisations can thrive in the face of change and complexity. By integrating Complexity Thinking into their practices, teams can discover new avenues for growth and improvement, ultimately enhancing their ability to deliver value consistently and effectively.</description>
			</item>
			<item>
				<title>Flow Efficiency</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/flow-efficiency/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/flow-efficiency/</guid>
				<description>Flow efficiency is the optimisation of work throughput within a value stream, aimed at minimising waste and reducing bottlenecks. This concept is essential for organisations seeking to deliver value in a predictable and sustainable manner, as it significantly influences the speed at which teams can respond to customer demands and market fluctuations. By examining and enhancing flow efficiency, teams can pinpoint delays and implement targeted improvements that boost overall performance. This methodology is closely aligned with Lean principles, which emphasise the removal of non-value-adding activities. Unlike metrics such as cycle time or lead time that focus on specific durations, flow efficiency offers a comprehensive view of how effectively work progresses through the system, promoting collaboration across various teams and disciplines to ensure seamless operation throughout the value stream. By emphasising flow efficiency, organisations foster a culture of continuous improvement, empowering teams to innovate and experiment. This not only increases productivity but also enhances resilience, allowing teams to adapt to evolving circumstances while consistently delivering value. Ultimately, the focus on flow efficiency nurtures an environment conducive to sustainable practices, leading to long-term success and heightened customer satisfaction.</description>
			</item>
			<item>
				<title>Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/kanban/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/kanban/</guid>
				<description>Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments.</description>
			</item>
			<item>
				<title>Lean</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/categories/lean/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/categories/lean/</guid>
				<description>Lean is a strategic methodology focused on maximising value while minimising waste, originating from the principles of the Toyota Production System. It is utilised to enhance organisational efficiency by delivering customer value through streamlined processes and fostering a culture of continuous improvement and respect for individuals. By systematically identifying and eliminating non-value-adding activities, Lean enables teams to optimise workflows, boost productivity, and swiftly adapt to changing market conditions. This approach transcends mere tools, embodying a mindset that prioritises long-term sustainability and systemic transformation. Techniques such as value stream mapping and flow efficiency allow teams to visualise their processes, pinpoint bottlenecks, and improve resource allocation, leading to the reliable delivery of high-quality products and services, which in turn enhances customer satisfaction and loyalty. Lean&amp;rsquo;s focus on empirical decision-making and iterative learning aligns seamlessly with Agile and DevOps principles, creating a collaborative environment that fosters rapid innovation while maintaining a commitment to value delivery. By promoting a culture of experimentation and feedback, Lean equips organisations to navigate and thrive in a dynamic landscape, ensuring their competitiveness and relevance in the market.</description>
			</item>
			<item>
				<title>Platform Engineering</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/</guid>
				<description>Platform Engineering is the discipline focused on the design, construction, and maintenance of internal platforms that empower developers to deliver value independently, reliably, and swiftly. Originating from the need to streamline software development processes, it aims to alleviate cognitive load by abstracting the complexities of infrastructure and operations through well-crafted interfaces, tools, and APIs. This approach treats platforms as products, ensuring clear ownership, regular feedback, and ongoing enhancements based on developer requirements. A robust platform engineering capability fosters paved paths and self-service tools that facilitate secure, observable, and resilient software delivery while avoiding constraints that stifle innovation. By creating an environment conducive to rapid feedback, safe experimentation, and autonomous delivery across teams, Platform Engineering not only provides essential tools but also cultivates a cohesive developer experience that aligns with organisational strategy, ultimately enabling continuous value delivery at scale.</description>
			</item>
			<item>
				<title>Product Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/</guid>
				<description>Product Delivery refers to the comprehensive process of delivering functional software products to customers, integrating various stages such as planning, development, testing, and deployment into a unified workflow. Originating from methodologies like Agile, Lean, and DevOps, this approach is essential for organisations aiming to deliver consistent value in a predictable and sustainable manner, ensuring that products align with customer needs and expectations. By emphasising an end-to-end delivery process, Product Delivery enhances collaboration among cross-functional teams, streamlines workflows, and reduces cycle times. It fosters a culture of continuous improvement and adaptability, driven by feedback loops that allow teams to respond swiftly to customer insights and market changes. This systemic approach not only improves product quality but also establishes a resilient organisational framework conducive to long-term success. Prioritising Product Delivery cultivates an environment where innovation flourishes and team ownership is encouraged, leading to increased employee engagement and satisfaction. Ultimately, this focus on delivering value through a structured process is vital for maintaining competitiveness and responsiveness in a rapidly changing landscape, positioning Product Delivery as a cornerstone of contemporary product development.</description>
			</item>
			<item>
				<title>Value Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-delivery/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/value-delivery/</guid>
				<description>Value Delivery is a systematic approach aimed at providing consistent and meaningful outcomes to customers through iterative and incremental processes. Originating from methodologies such as Lean and Agile, it is used in product development to ensure that efforts are aligned with customer needs, allowing for every release to contribute tangible benefits. This concept is vital as it enables teams to deliver value predictably and sustainably, fostering a culture of continuous improvement and responsiveness to change. By prioritising value delivery, organisations can significantly enhance customer satisfaction and loyalty, as products are more likely to meet expectations. It promotes cross-functional collaboration, encouraging teams to work together to identify and eliminate waste, optimise workflows, and streamline processes. Value Delivery encompasses the entire lifecycle of product development, from initial discovery to delivery and beyond, ensuring that teams can adapt to evolving market demands and customer feedback. This long-term focus ultimately leads to sustained organisational success and resilience in a competitive landscape, as embedding value delivery into the organisational culture creates a robust framework that supports innovation and drives continuous value creation for customers and stakeholders alike.</description>
			</item>
			<item>
				<title>Value Stream Management</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-management/</guid>
				<description>Value Stream Management is a strategic methodology aimed at improving the flow of value within an organisation by optimising processes, reducing waste, and aligning efforts with customer outcomes. Originating from the need to enhance operational efficiency, it involves mapping the entire value stream from ideation to delivery, enabling teams to identify and address bottlenecks and inefficiencies that impede performance. This approach is vital in the context of agile, DevOps, and product development, as it fosters a culture of continuous improvement and responsiveness to market changes. By promoting collaboration across departments and breaking down silos, Value Stream Management ensures a shared understanding of how work contributes to overarching business goals. It empowers teams to focus on delivering high-quality products that satisfy customer needs while balancing speed and efficiency. Unlike specific Agile frameworks or Lean principles that concentrate on particular practices, Value Stream Management offers a comprehensive perspective on the entire process, ensuring that each step adds value. This long-term, systemic approach not only enhances operational performance but also nurtures an environment conducive to innovation, ultimately leading to greater organisational resilience and adaptability in a fast-changing landscape.</description>
			</item>
			<item>
				<title>Agentic Software Delivery</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/</link>
				<pubDate>Tue, 21 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/</guid>
				<description>Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation&amp;rsquo;s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term &amp;lsquo;agentic&amp;rsquo; implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.</description>
			</item>
			<item>
				<title>Product Developer</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</link>
				<pubDate>Mon, 20 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/</guid>
				<description>Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.</description>
			</item>
	</channel>
</rss>
