Large batch sizes of work are considered a barrier to high performance in Lean and Agile because they increase the amount of work in progress (WIP), which leads to longer cycle times, higher variability, lower quality, and reduced feedback and learning. Large batches also increase the risk of waste, rework, and delays, as well as the complexity and uncertainty of the work. Lean and Agile advocate for reducing batch sizes and limiting WIP, which enables faster flow, shorter feedback loops, higher quality, and more value delivery. Some of the practices that help reduce batch sizes and limit WIP are:
Pulling versus pushing work, which means that work is initiated only when there is a demand and capacity for it, rather than being assigned or scheduled in advance.
Making work visible, which means that the status and progress of work are transparent and accessible to all stakeholders, using tools such as Kanban boards, burn-down charts, and dashboards.
Limiting work-in-progress, which means that the number of work items in each stage of the workflow is restricted, based on the available resources and throughput, to prevent bottlenecks and overloading. References:
Integrating ITIL 4 and Design Thinking | Cognixia, section “What is Design Thinking?”
Service design: ITIL 4 practice guide | Axelos, section 2.1.1
ITIL 4 , DESIGN THINKING & RAPID - Devoteam, section “Design Thinking”
ITIL4 meets design thinking | Axelos, section “Design thinking”
