https://engineering-leadership.hinshelwood.com/categories/kanban/ Recent content in Kanban on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ Mon, 15 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ 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. https://engineering-leadership.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ Mon, 03 Mar 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ 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. https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Sat, 15 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ 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. https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ 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. https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Mon, 08 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ 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. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Thu, 07 Mar 2024 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process. https://engineering-leadership.hinshelwood.com/videos/getting-started-with-kanban/ Wed, 14 Feb 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/getting-started-with-kanban/ Kanban helps teams improve workflow and productivity by visualizing work, setting clear processes, and using metrics like cycle time and throughput to drive continuous improvement. Start with a small, willing team, define and visualize your workflow, and use data to identify and address bottlenecks. Begin with a pilot, focus on collaboration and regular feedback, and use metrics to build credibility and guide ongoing enhancements. https://engineering-leadership.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Thu, 20 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving. https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Tue, 04 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Using a separate “Blocked” column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible. https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/ Not all delays are equal; waiting for approval is different from being blocked by missing dependencies. Treating all delays as blocks hides real workflow issues and reduces accountability. Make delay sources explicit, track idle time, and highlight true blockers to identify and fix underlying problems. https://engineering-leadership.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/ Fri, 29 Mar 2024 16:42:17 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/ Using Azure DevOps to implement a Caman strategy helps hybrid teams visualise and manage work more effectively by establishing shared workflow rules, customising boards and columns, and tracking key metrics like lead and cycle time. Involving the whole team in defining and refining these rules improves transparency and reduces local optimisations that can harm overall flow. Development managers should ensure their teams collaborate on workflow setup in Azure DevOps and regularly review it to optimise efficiency and clarity. https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/ Fri, 16 Feb 2024 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/ 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. https://engineering-leadership.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Tue, 13 Feb 2024 15:44:53 +0000 https://engineering-leadership.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Using Blocked columns on Kanban boards hides the true status of work, encourages team disengagement, and leads to stale tasks and inflated work-in-progress limits. Instead, teams should tag blocked items within their current workflow stage and provide clear context, which maintains transparency and accountability. Managers should avoid Blocked columns and use tags or annotations to highlight issues without disrupting the flow or losing critical information. https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Mon, 29 Jul 2024 06:45:02 +0000 https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ 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. https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Mon, 03 Mar 2025 15:46:26 +0000 https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Kanban focuses on improving workflow by removing constraints and bottlenecks, not by pushing people to work harder or longer. Key to better delivery is reducing work in progress and identifying blockers to increase efficiency. Managers should identify and address the biggest constraint in their current workflow to see meaningful improvements. https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/ Thu, 29 Feb 2024 07:00:09 +0000 https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/ 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. https://engineering-leadership.hinshelwood.com/guides/kanban-guide/ Thu, 01 May 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/guides/kanban-guide/ Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work. https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/ Tue, 09 May 2023 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/ 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. https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Thu, 15 Feb 2024 07:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ 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. https://engineering-leadership.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Wed, 06 Mar 2024 07:00:17 +0000 https://engineering-leadership.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ 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. https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/ Mon, 26 Feb 2024 14:06:47 +0000 https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/ Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow. https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/ Wed, 28 Feb 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/ Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements. https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ Thu, 03 Jul 2025 05:22:41 +0000 https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together. https://engineering-leadership.hinshelwood.com/articles/improvements-in-visual-studio-alm-from-the-alm-summit/ Fri, 08 Feb 2013 03:18:22 +0000 https://engineering-leadership.hinshelwood.com/articles/improvements-in-visual-studio-alm-from-the-alm-summit/ Highlights new Visual Studio ALM features from the ALM Summit, including Git support, web-based test management, Kanban swim lanes, and flexible work item tagging. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/ Wed, 23 Aug 2023 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/ 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. https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Mon, 01 Jul 2024 07:00:24 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency. https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Mon, 24 Jun 2024 06:48:02 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements. https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/ Tue, 27 Feb 2024 07:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/ Defining and visualising your workflow in Kanban creates shared understanding, clarity, and alignment among team members, which leads to greater efficiency. Establishing clear rules for task selection, workflow stages, and work in progress is essential for a stable and productive system. Take time to document and visualise your process so everyone knows how work flows and can contribute effectively. https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Mon, 22 Jul 2024 06:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ 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. https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Fri, 25 Aug 2023 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Kanban is popular in creative industries because it adapts to existing workflows, reduces chaos, and helps teams align on priorities without stifling creativity. It improves efficiency by visualising work, shortening cycle times, and encouraging collective decision-making. Development managers should consider mapping their team’s current process with Kanban to enhance collaboration and deliver creative work more predictably. https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ Mon, 08 Jul 2024 06:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ A clear and accurate Kanban board is essential for understanding and improving your team’s workflow. Map your actual process, adjust columns to reflect real work stages, and use visual cues to highlight priorities and bottlenecks. Regularly review and adapt your board to boost team collaboration, identify issues early, and drive continuous improvement. https://engineering-leadership.hinshelwood.com/articles/professional-kanban-trainer-for-applying-professional-kanban/ Tue, 19 Jan 2021 14:49:00 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-kanban-trainer-for-applying-professional-kanban/ The new Kanban Guide provides a clear, open framework for optimizing value flow in software teams, complementing Scrum and fostering collaboration between the two communities. Professional Kanban training now offers focused, in-depth learning on Kanban principles and practices, with certification and resources available independently of the course. Development managers can leverage these guides and training to improve workflow efficiency and team performance. https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability. https://engineering-leadership.hinshelwood.com/tags/throughput/ Wed, 09 Apr 2025 14:41:23 +0000 https://engineering-leadership.hinshelwood.com/tags/throughput/ 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. https://engineering-leadership.hinshelwood.com/categories/kanban/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/categories/kanban/ Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments.