<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Throughput on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/throughput/</link>
		<description>Recent content in Throughput on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership-preview.hinshelwood.com/tags/throughput/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rethinking Capacity Planning</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/</link>
				<pubDate>Mon, 21 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/</guid>
				<description>Capacity planning should focus on optimising system flow and predictability, not tracking individual hours or task assignments. Shifting from micromanagement to managing work as a system at portfolio, category, and team levels helps prevent overload, improves value delivery, and enables reliable forecasting. Development managers should prioritise system-level metrics, enforce work-in-progress limits, and empower teams to pull well-prepared work, creating sustainable and predictable delivery.</description>
			</item>
			<item>
				<title>Work can flow across the Sprint boundary</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</link>
				<pubDate>Tue, 30 Jan 2018 20:12:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/</guid>
				<description>Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</link>
				<pubDate>Sat, 15 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</guid>
				<description>Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals.</description>
			</item>
			<item>
				<title>Overview of &#39;applying flow metrics for Scrum&#39; course</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</link>
				<pubDate>Mon, 19 Feb 2024 07:00:09 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-&#39;applying-flow-metrics-for-scrum&#39;-course/</guid>
				<description>The &amp;ldquo;Applying Flow Metrics for Scrum&amp;rdquo; course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement.</description>
			</item>
			<item>
				<title>Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</link>
				<pubDate>Mon, 08 Jan 2024 07:00:06 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/</guid>
				<description>Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting.</description>
			</item>
			<item>
				<title>Deciphering the Enigma of Story Points Across Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</link>
				<pubDate>Thu, 21 Sep 2023 08:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/</guid>
				<description>Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes.</description>
			</item>
			<item>
				<title>Story Points: A Ghost of Agile Past</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</link>
				<pubDate>Fri, 29 Dec 2023 07:00:14 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/</guid>
				<description>Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance.</description>
			</item>
			<item>
				<title>Stop Starting and Start Finishing: The Key to Team Success</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</link>
				<pubDate>Wed, 31 Jan 2024 14:26:11 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/</guid>
				<description>Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact.</description>
			</item>
			<item>
				<title>Maximizing Transparency and Improvement in Software Engineering with Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</link>
				<pubDate>Mon, 29 Jul 2024 06:45:02 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/</guid>
				<description>Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement.</description>
			</item>
			<item>
				<title>Kanban Guide for Scrum Teams</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide-for-scrum-teams/</guid>
				<description>Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery.</description>
			</item>
			<item>
				<title>3 best ways to wreck Kanban. Use vanity metrics</title>
				<link>https://engineering-leadership-preview.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-preview.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>Kanban Guide</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</link>
				<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/</guid>
				<description>Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work.</description>
			</item>
			<item>
				<title>How do you make a good Forecast?</title>
				<link>https://engineering-leadership-preview.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-preview.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>In WIP, less is more.  Why?</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/in-wip-less-is-more-why/</link>
				<pubDate>Tue, 09 May 2023 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/in-wip-less-is-more-why/</guid>
				<description>Limiting work in progress leads to higher productivity because multitasking and context switching reduce efficiency and slow down progress. Keeping tasks small and focusing on finishing before starting new work helps teams deliver more in less time. Development managers should encourage teams to reduce simultaneous tasks and prioritize completing work to improve outcomes.</description>
			</item>
			<item>
				<title>Does Kanban integrate into a Scrum environment?</title>
				<link>https://engineering-leadership-preview.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-preview.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>The Key to a Kanban Strategy: Understanding WIP Limits</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</link>
				<pubDate>Wed, 06 Mar 2024 07:00:17 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/</guid>
				<description>Setting work-in-progress (WIP) limits is essential for an effective Kanban strategy because it prevents overload, exposes bottlenecks, and improves workflow. The optimal WIP limit for each stage should be found through experimentation and regular adjustment, aiming for a balance that maximizes flow without causing idle time or bottlenecks. Start small, monitor results, and adjust limits as needed to boost team productivity and collaboration.</description>
			</item>
			<item>
				<title>Overview of &#39;applying metrics for predictability&#39; Kanban course</title>
				<link>https://engineering-leadership-preview.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-preview.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>Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team&#39;s Success</title>
				<link>https://engineering-leadership-preview.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-preview.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>Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</link>
				<pubDate>Wed, 23 Aug 2023 07:00:10 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/</guid>
				<description>Kanban can be applied to any workflow to provide visibility into how work moves through your system, enabling teams to optimise delivery speed and manage capacity effectively. By using data analysis and probabilistic forecasting, such as Monte Carlo simulations, you can set realistic expectations with stakeholders and make more informed decisions. Consider adopting Kanban to improve transparency, predictability, and continuous improvement in your development processes.</description>
			</item>
			<item>
				<title>Why Limiting Work in Progress is Key to Success in Kanban</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</link>
				<pubDate>Mon, 22 Jul 2024 06:00:19 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/</guid>
				<description>Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable.</description>
			</item>
			<item>
				<title>Throughput</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/throughput/</link>
				<pubDate>Wed, 09 Apr 2025 14:41:23 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>
	</channel>
</rss>
