<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Metrics and Learning on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/</link>
		<description>Recent content in Metrics and Learning on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?</title>
				<link>https://engineering-leadership.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.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>The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery</title>
				<link>https://engineering-leadership.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.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>Velocity isn’t how many story points a team burns down</title>
				<link>https://engineering-leadership.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.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.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.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>Stop Testing Quality In: How Shifting Left Builds Better Software, Faster</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</link>
				<pubDate>Mon, 18 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/</guid>
				<description>Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases.</description>
			</item>
			<item>
				<title>Every delay increases the risk of failure</title>
				<link>https://engineering-leadership.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.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>How to Build for Business Resilience and Continuity</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</link>
				<pubDate>Mon, 26 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/</guid>
				<description>Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement.</description>
			</item>
			<item>
				<title>Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments</title>
				<link>https://engineering-leadership.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.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>Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)</title>
				<link>https://engineering-leadership.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.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.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.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>Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success</title>
				<link>https://engineering-leadership.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.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.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.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.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.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.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.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>Estimating Better in an Overloaded System Is a Poor Man’s Strategy</title>
				<link>https://engineering-leadership.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.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>Deciphering the Enigma of Story Points Across Teams</title>
				<link>https://engineering-leadership.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.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>Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/</link>
				<pubDate>Thu, 15 Aug 2024 07:04:39 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/</guid>
				<description>Using clear metrics and visual tools helps teams identify improvement areas, increase transparency, and make better decisions. Regularly reviewing processes, experimenting with small changes, and focusing on relevant, actionable data are key to ongoing improvement. Development managers should ensure their teams use these practices to drive meaningful and continuous workflow enhancements.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership.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.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</guid>
				<description>DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues.</description>
			</item>
			<item>
				<title>Deploying Windows OS Directly to Production: Then vs Now</title>
				<link>https://engineering-leadership.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.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.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.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>Frequent releases are not just a technical strategy</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</link>
				<pubDate>Fri, 07 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/</guid>
				<description>Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback.</description>
			</item>
			<item>
				<title>The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI</title>
				<link>https://engineering-leadership.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.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>The Common Challenges of Adopting DevOps Practices</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</link>
				<pubDate>Tue, 20 Aug 2024 08:04:38 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-common-challenges-of-adopting-devops-practices/</guid>
				<description>Adopting DevOps brings challenges like managing new types of risk and avoiding setbacks, especially as teams shift from long, structured cycles to rapid, continuous delivery. Success depends on quickly closing feedback loops, acting on real-world data from production, and adapting processes to maintain quality and flexibility. Development managers should focus on integrating feedback into daily workflows and using modern tools to manage risk without slowing down delivery.</description>
			</item>
			<item>
				<title>Unlocking Continuous Improvement: How Metrics and Visualisation Drive Workflow Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/</link>
				<pubDate>Mon, 19 Aug 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/</guid>
				<description>Continuous improvement relies on using the right metrics and clear visual tools to identify patterns, increase transparency, and drive meaningful workflow changes. Teams should focus on measuring what truly matters and ensure their visualisations support understanding and collaboration. Regularly reviewing and adjusting processes based on these insights is essential for ongoing success.</description>
			</item>
			<item>
				<title>Metrics that matter with evidence-based management</title>
				<link>https://engineering-leadership.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.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>Building a release pipeline with Release Management with Visual Studio 2013</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</link>
				<pubDate>Tue, 18 Feb 2014 16:30:59 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/</guid>
				<description>Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices.</description>
			</item>
			<item>
				<title>If software is not delivered, it is not valuable</title>
				<link>https://engineering-leadership.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.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.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.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>Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</link>
				<pubDate>Wed, 20 Nov 2024 08:02:36 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/</guid>
				<description>A team increased their annual feature delivery from 25 to 150 by breaking down work into smaller experiments, enabling faster feedback, reduced risk, and continuous learning without increasing headcount. This approach allowed them to quickly identify and focus on features that mattered most to customers, leading to better products. Development managers should consider adopting small, frequent experiments to drive both speed and quality in feature delivery.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Four Key Value Areas in Scrum</title>
				<link>https://engineering-leadership.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.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>Illuminate Your Workflow: Harnessing Candan Strategies for Continuous Improvement and Transparency</title>
				<link>https://engineering-leadership.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.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>How long does it take to transition from project management to Kanban?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</link>
				<pubDate>Fri, 16 Feb 2024 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/</guid>
				<description>Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams.</description>
			</item>
			<item>
				<title>How to Measure Your Organization&#39;s Ability to Improve Value Through Innovation</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-measure-your-organization&#39;s-ability-to-improve-value-through-innovation/</link>
				<pubDate>Thu, 25 Jan 2024 11:00:18 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-measure-your-organization&#39;s-ability-to-improve-value-through-innovation/</guid>
				<description>To improve your organization&amp;rsquo;s ability to deliver value, focus on measuring and enhancing your capacity for innovation using evidence-based management and key metrics like active branches, technical debt, innovation rate, and complexity overhead. Regularly monitor these metrics, set clear innovation goals, and foster a culture of continuous improvement to identify bottlenecks and drive better outcomes. Take action by simplifying processes, managing technical debt, and increasing time spent on new features to boost your team&amp;rsquo;s innovation and long-term success.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management for Agile Success</title>
				<link>https://engineering-leadership.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.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>Evidence-based Management: Gathering the metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/</link>
				<pubDate>Wed, 30 Dec 2020 14:02:07 +0000</pubDate>
				<guid>https://engineering-leadership.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>Mastering Outcomes: How Evidence-Based Management Transforms Your Project Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-outcomes-how-evidence-based-management-transforms-your-project-success/</link>
				<pubDate>Thu, 12 Sep 2024 13:46:15 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-outcomes-how-evidence-based-management-transforms-your-project-success/</guid>
				<description>Defining clear, measurable outcomes and using both leading and lagging metrics are essential for project success. Evidence-based management helps teams make informed decisions by consistently collecting and analyzing data, then iterating based on insights. Development managers should focus on setting SMART goals, tracking the right metrics, and using data to guide continuous improvement.</description>
			</item>
			<item>
				<title>Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-chasing-tech-hype-how-evidence-based-decisions-empower-real-leadership/</link>
				<pubDate>Fri, 04 Jul 2025 06:00:44 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-chasing-tech-hype-how-evidence-based-decisions-empower-real-leadership/</guid>
				<description>Chasing technology trends because competitors do is not a real strategy; instead, focus on making your systems visible, use evidence to guide decisions, and choose tools that fit your actual needs. This approach helps you defend your roadmap with confidence and creates sustainable results for your teams and business. Prioritise clarity and alignment over hype to lead effectively and avoid unnecessary complexity.</description>
			</item>
			<item>
				<title>The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/evidence-based-management-guide/</link>
				<pubDate>Wed, 01 Jan 2020 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>The Importance of Validation in Product Development: A Strategic Approach</title>
				<link>https://engineering-leadership.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.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>Harnessing Evidence-Based Management: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/</link>
				<pubDate>Wed, 14 Aug 2024 07:12:45 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/</guid>
				<description>Evidence-based management helps you make better decisions by using data to inform, not control, your actions and team behaviours. Focus on choosing the right metrics that align with your business goals, understand the context behind the numbers, and engage with teams to uncover root causes. Use data as a guide for continuous improvement and be ready to adapt your strategies as new insights emerge.</description>
			</item>
			<item>
				<title>Mastering Evidence-Based Management in Agile: Inform, Don’t Control</title>
				<link>https://engineering-leadership.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.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>Harnessing the Power of Empiricism: Transform Your Decision-Making with Data-Driven Insights</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/harnessing-the-power-of-empiricism-transform-your-decision-making-with-data-driven-insights/</link>
				<pubDate>Thu, 17 Aug 2023 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/harnessing-the-power-of-empiricism-transform-your-decision-making-with-data-driven-insights/</guid>
				<description>Using data to guide decisions helps teams make better choices, improve continuously, and build trust with stakeholders. The key is to ensure access to relevant data, act deliberately, and monitor results in a cycle of experimentation and learning. Development managers should foster a culture where decisions are based on evidence, not assumptions, and regularly review outcomes to adapt and improve.</description>
			</item>
			<item>
				<title>The Importance of Evidence-Based Management in Agile Environments</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</link>
				<pubDate>Mon, 22 Jan 2024 11:00:07 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/</guid>
				<description>Evidence-based management helps Agile teams make smarter decisions by tracking key metrics like value delivered, time to market, and ability to innovate, ensuring changes actually lead to improvement. Without data, teams risk wasting time and resources on ineffective changes, but with regular measurement and analysis, they can adapt quickly and foster continuous improvement. Start by identifying and tracking a few important metrics, involve your team, and use the insights to guide your next steps.</description>
			</item>
			<item>
				<title>The Power of Metrics: Why PAL-EBM is Essential for Your Organization</title>
				<link>https://engineering-leadership.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.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>Unlocking the Power of Immersive Learning for Product Management</title>
				<link>https://engineering-leadership.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.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>What my father taught me about Evidence-based Management (34 years before it was invented!)</title>
				<link>https://engineering-leadership.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.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>How Do You Know the Value Currently Delivered in Your Organization?</title>
				<link>https://engineering-leadership.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.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>Navigating the Judgment Trap: How to Foster a Healthy Agile Environment</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/</link>
				<pubDate>Thu, 09 Nov 2023 06:45:04 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/</guid>
				<description>Judgment in Agile teams, such as rigid rules and unhealthy metric comparisons, can lower morale, stifle innovation, and create a culture of blame. To avoid this, set meaningful goals, use adaptive metrics that encourage improvement, and foster open dialogue focused on learning. Development managers should prioritize creating a safe, collaborative environment where teams feel empowered to innovate and grow.</description>
			</item>
			<item>
				<title>Mastering Product Development Costs: Empower Your Team for Financial Success</title>
				<link>https://engineering-leadership.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.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>How Do You Know How Long It Takes to Deliver Value?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</link>
				<pubDate>Fri, 26 Jan 2024 11:00:51 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/</guid>
				<description>Measuring and improving Time to Market is essential for delivering value quickly and staying competitive. Key metrics like lead time, cycle time, time to pivot, time to learn, and time to fix help teams identify bottlenecks and make better decisions. Focus on streamlining processes, automating tasks, gathering fast feedback, and building cross-functional teams to reduce delivery times and ensure you are delivering what customers need most.</description>
			</item>
			<item>
				<title>Say-Do Metrics: Avoiding Agile Banditry in Your Organization</title>
				<link>https://engineering-leadership.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.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>Mastering Evidence-Based Management (EBM) for Product Owners: Maximizing Value Delivery</title>
				<link>https://engineering-leadership.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.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.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Evidence-Based Portfolio Management</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/evidence-based-portfolio-management/</link>
				<pubDate>Wed, 16 Dec 2020 13:11:40 +0000</pubDate>
				<guid>https://engineering-leadership.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>3 best ways to wreck Kanban. Use vanity metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</link>
				<pubDate>Thu, 29 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/</guid>
				<description>Relying on vanity metrics like story points and velocity can undermine your Kanban strategy, as they do not provide actionable insights. Instead, focus on key metrics such as work in progress, cycle time, throughput, and work item age to identify bottlenecks, optimize flow, and improve predictability. Use data from your workflow tools to drive continuous improvement and make informed decisions for better team performance.</description>
			</item>
			<item>
				<title>Getting Started with Objectives &amp; Key Results</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/getting-started-with-objectives-key-results/</link>
				<pubDate>Mon, 18 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>How do you make a good Forecast?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</link>
				<pubDate>Mon, 09 Sep 2019 11:20:33 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-do-you-make-a-good-forecast/</guid>
				<description>To make better forecasts in agile projects, shift from using metrics like story points and velocity to flow-based metrics such as cycle time, throughput, and work in process, which improve predictability by encouraging smaller, more manageable work items. For budgeting and staffing, calculate team costs per sprint and extrapolate for annual needs, moving from project-based to team-based budgeting. Involve stakeholders early in this transition to address concerns and ensure smoother adoption.</description>
			</item>
			<item>
				<title>OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/guides/okr-guide/</link>
				<pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.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>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</link>
				<pubDate>Thu, 15 Feb 2024 07:00:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/</guid>
				<description>Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions.</description>
			</item>
			<item>
				<title>What is empiricism and why is it so critical to great Agile?</title>
				<link>https://engineering-leadership.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.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>Overview of &#39;applying metrics for predictability&#39; Kanban course</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</link>
				<pubDate>Tue, 20 Feb 2024 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/overview-of-&#39;applying-metrics-for-predictability&#39;-kanban-course/</guid>
				<description>The &amp;ldquo;Applying Metrics for Predictability&amp;rdquo; Kanban course teaches teams how to use key Kanban metrics and probabilistic forecasting to improve delivery predictability, enabling more accurate planning and increased stakeholder trust. Participants learn to interpret data, identify bottlenecks, and make informed decisions that drive efficiency and consistent value delivery. Development managers whose teams struggle with predictability should consider this course to enhance forecasting and workflow reliability.</description>
			</item>
			<item>
				<title>Evidence-Based Management: The Key to Agile Success</title>
				<link>https://engineering-leadership.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.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>Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team&#39;s Success</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</link>
				<pubDate>Mon, 08 Jan 2024 11:00:37 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team&#39;s-success/</guid>
				<description>Relying on story points and velocity as performance metrics creates mistrust and pressure, undermining team collaboration and the core values of Agile. Instead, focus on objective measures like cycle time and throughput to better understand team efficiency and foster a healthier, more productive environment. Shift your metrics to support transparency and continuous improvement rather than arbitrary targets.</description>
			</item>
			<item>
				<title>Understanding the Difference: Traditional Management vs. Evidence-Based Management</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/understanding-the-difference-traditional-management-vs-evidence-based-management/</link>
				<pubDate>Thu, 12 Sep 2024 07:00:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/understanding-the-difference-traditional-management-vs-evidence-based-management/</guid>
				<description>Traditional management relies on experience and authority, often leading to decisions based on intuition or hierarchy rather than data. Evidence-based management uses data collection, team analysis, and outcome validation to drive better decisions and avoid misleading metrics like story points or velocity. Development managers should shift focus from vanity metrics to meaningful data that aligns with organizational goals and encourages continuous improvement.</description>
			</item>
			<item>
				<title>Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership</title>
				<link>https://engineering-leadership.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.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>The Power of Peer Feedback in Immersive Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/</link>
				<pubDate>Wed, 07 Feb 2024 07:00:27 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/</guid>
				<description>Peer feedback in immersive learning accelerates skill development by enabling participants to apply Scrum techniques in real situations, share experiences, and collaboratively solve problems. Facilitated debriefs deepen understanding and build a shared knowledge base, leading to better retention and real-world results. Encourage your teams to actively engage in peer feedback during training to drive continuous improvement and more effective Scrum adoption.</description>
			</item>
			<item>
				<title>Customer Focus</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-focus/</link>
				<pubDate>Tue, 13 May 2025 09:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.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>Site Reliability Engineering</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/</link>
				<pubDate>Mon, 05 May 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Service Level Expectation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/</link>
				<pubDate>Mon, 05 May 2025 09:46:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/</guid>
				<description>A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team&amp;rsquo;s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team&amp;rsquo;s ability to deliver reliably and respond to change.</description>
			</item>
			<item>
				<title>Lead Time</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.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>Ability to Innovate</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/ability-to-innovate/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:20 +0000</pubDate>
				<guid>https://engineering-leadership.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.hinshelwood.com/tags/current-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:21:05 +0000</pubDate>
				<guid>https://engineering-leadership.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.hinshelwood.com/tags/time-to-market/</link>
				<pubDate>Thu, 10 Apr 2025 14:20:01 +0000</pubDate>
				<guid>https://engineering-leadership.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.hinshelwood.com/tags/unrealised-value/</link>
				<pubDate>Thu, 10 Apr 2025 14:19:46 +0000</pubDate>
				<guid>https://engineering-leadership.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>Throughput</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/throughput/</link>
				<pubDate>Wed, 09 Apr 2025 14:41:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/throughput/</guid>
				<description>Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance.</description>
			</item>
			<item>
				<title>Observability</title>
				<link>https://engineering-leadership.hinshelwood.com/concepts/observability/</link>
				<pubDate>Wed, 09 Apr 2025 14:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.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>Evidence Based Management</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/evidence-based-management/</link>
				<pubDate>Fri, 21 Mar 2025 14:44:46 +0000</pubDate>
				<guid>https://engineering-leadership.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>Continuous Improvement</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/continuous-improvement/</link>
				<pubDate>Fri, 21 Mar 2025 13:28:30 +0000</pubDate>
				<guid>https://engineering-leadership.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>Customer Feedback Loops</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/customer-feedback-loops/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Cycle Time</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/cycle-time/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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.hinshelwood.com/tags/deployment-frequency/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Empirical Process Control</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/empirical-process-control/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Evidence Based Leadership</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/evidence-based-leadership/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/evidence-based-leadership/</guid>
				<description>Evidence Based Leadership is a strategic methodology that leverages empirical data to guide decision-making and enhance organisational performance. Originating from the need for accountability and transparency in leadership, this approach enables leaders to make informed choices that align with both organisational goals and team requirements. By focusing on measurable outcomes and real-time feedback, leaders can discern effective practices and areas for improvement, fostering a more adaptive organisational culture. This methodology is particularly valuable in agile and DevOps environments, where the ability to respond swiftly to market changes and customer demands is critical. Evidence Based Leadership encourages continuous learning and adaptation, promoting a long-term perspective that prioritises systemic enhancements to performance and resilience. By embedding data-driven insights into leadership practices, organisations can create a culture of experimentation and innovation, empowering teams to test ideas and learn from their outcomes. This not only boosts team motivation and engagement but also ensures a stronger alignment between strategic objectives and operational execution, ultimately leading to improved results and value delivery.</description>
			</item>
			<item>
				<title>Forecasting</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/forecasting/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Product Management</title>
				<link>https://engineering-leadership.hinshelwood.com/categories/product-management/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Revenue per Employee</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/revenue-per-employee/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/revenue-per-employee/</guid>
				<description>Revenue per Employee is a crucial observability metric that measures an organisation&amp;rsquo;s financial efficiency by calculating total revenue divided by the number of employees. This metric provides valuable insights into how effectively an organisation converts its workforce capacity into revenue, allowing for the analysis of systemic performance rather than focusing on individual contributions. It serves as a financial signal that facilitates empirical examination of workforce alignment, throughput, and productivity trends over time. When utilised appropriately, Revenue per Employee aids in strategic planning, identifies delivery constraints, and assesses the operational impact of organisational changes, such as the adoption of Agile methodologies or Lean transformations. By monitoring this metric over time, organisations can uncover the effects of restructuring, automation, or changes in team composition. Although it is not a diagnostic tool on its own, it plays a significant role in a broader set of delivery and business metrics, enabling leaders to evaluate the performance of their systems. This perspective positions Revenue per Employee as a lens through which to understand system health, rather than as a means of assessing individual or team accountability.</description>
			</item>
			<item>
				<title>Team Performance</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/team-performance/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/team-performance/</guid>
				<description>Team performance is the consistent ability of a team to deliver outcomes through its established system of work, reflecting delivery capability over time as indicated by observable patterns in flow, responsiveness, and quality. This concept originates from the understanding that performance is shaped by the structure and constraints of the operational system, influenced by factors such as team composition, collaboration habits, skill alignment, and clarity of purpose. As a system-level capability, team performance transcends individual or cultural traits, making it crucial for organisations aiming to enhance their agile and DevOps practices. By employing flow metrics, retrospectives, and empirical signals to evaluate performance, organisations can discern whether teams are improving, stagnating, or hindered by external dependencies. High-performing teams demonstrate both consistency and adaptability in their delivery, even amidst change. Enhancing team performance involves a focus on system design, which includes limiting work in progress, refining collaboration patterns, and increasing visibility into obstacles. This systemic approach ensures that improvements are not only effective but also sustainable and repeatable across the organisation, ultimately contributing to more efficient product development and organisational design.</description>
			</item>
			<item>
				<title>Test Automation</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/test-automation/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.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>Metrics and Learning</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/</link>
				<pubDate>Tue, 11 Feb 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/</guid>
				<description>Metrics and Learning is a fundamental concept that centres on the utilisation of data, metrics, and feedback to drive continuous improvement within teams and organisational processes. Originating from the need for empirical decision-making, this approach allows organisations to enhance their value delivery by systematically collecting and analysing performance metrics. By doing so, teams can pinpoint areas for enhancement, monitor their progress, and adjust their strategies in alignment with changing customer demands. The focus on learning through metrics fosters a culture of experimentation and adaptability, enabling teams to respond swiftly to feedback and pivot as necessary. This systemic approach not only facilitates immediate improvements but also lays the groundwork for sustained development and innovation. Unlike methodologies that may be prescriptive, Metrics and Learning empowers teams to take ownership of their performance, which is essential for maintaining agility in a fast-paced environment. By integrating metrics into everyday operations, organisations can establish a continuous feedback loop that informs practices and strategies, ultimately leading to more effective and resilient product development.</description>
			</item>
	</channel>
</rss>
