Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Avoiding Over Utilization Field Trip

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

You can read in many places (for example here or in Don Reinersten’s Book The Principles of Product Development Flow) that when you avoid overutilization (that is, use less than 100% capacity) a system (like a road or a scrum team) that handles items with variation (like cars or stories for software) you get better cycle time – that is, items flow faster through the system.

That makes sense. However, I was wondering about the throughput. I can understand that if a team is less busy they will process items faster, but if they are less busy it means some people don’t do something some of the time. So what will happen to the throughput?

I was thinking about this on my way home from a client yesterday and suddenly I found myself on a pedestrian bridge above a highway (road 2 in Israel).

As you can see, the northbound lanes (going out of Tel Aviv) are jammed (the lanes are fully utilized) while the southbound lanes are pretty free. So I thought to myself why not check the throughput?

I measured one minute and counted the cars going on the northbound lanes (the jammed lanes): Sixty. Good. Now I counted how many cars go under the bridge in one minute in the southbound lanes: Forty. It was a bit disappointing. It sure wasn’t worth all the strange looks I got from passersby on the bridge. I was hoping to get a better result on the free lanes. However, traffic was not very intense going to Tel Aviv so I decided to give it another try tomorrow morning.

All that night I couldn’t sleep from excitement and finally, dawn came and I was ready to go out and count cars again. The only problem was that counting the cars too early would not do so I waited for morning to advance a bit, for my kids to wake up and demand the full service they deserve and for traffic to build up.

Finally I got to that bridge again. This is how traffic looked this morning.

As you see there is no traffic Jam. In fact the utilization of the road is pretty low – a lot of asphalt is enjoying a warm Israeli winter Sun. Again I started my stopper and counted cars on the northbound lanes. The tension was high in the air. A friend of mine who happened to be on that bridge shouted “Don’t jump!”

What would I do if I can’t beat the traffic jam throughput of Sixty? I was looking to build intuition here and if I couldn’t prove it to myself how could I persuade my clients?

The traffic was good but there were some gaps. I watched the seconds go by. And then, finally… Eighty cars! What a relief.

This means (to me) that there may be something there in that theory, that if we better managed the traffic we could get better throughput. But it’s not just better throughput, it is better cycle time too! Those cars were going around 90 or 100 kilometers per hour! We could get more cars per hour and even get them faster wherever they’re going!

Could this be true for software, too? Could it be that if we better manage the level of utilization of our software teams and the flow of development items into the teams we will get higher throughput and improved cycle time?

(To be continued)

Subscribe for Email Updates:

Categories:

Tags:

An Appreciative Retrospective
LAB
Effective Agile Retrospectives
Atlassian
Certified SAFe
AgileSparks
SPC
Manage Budget Creation
Nexus Integration Team
Agile Project
Coaching Agile Teams
Releases Using Lean
speed @ scale
Scrum
Agile Outsourcing
Frameworks
Managing Projects
Lean and Agile Techniques
Atlaassian
NIT
Scrum Primer
Webinar
Enterprise DevOps
Agile Exercises
Agile Mindset
speed at scale
Scrum Values
The Agile Coach
RTE
Scrum Guide
TDD
Nexus and Kanban
Lean Software Development
Agile for Embedded Systems
Jira admin
SAFe DevOps
ROI
Daily Scrum
predictability
POPM
Pomodoro Technique
The Kanban Method
Jira Plans
Continuous Deployment
Agile Risk Management
EOS®
Kaizen
Slides
AI
Sprint Planning
Nexus vs SAFe
Scaled Agile Framework
Agile Basics
Program Increment
Agile Product Development
Agile Program
Jira
Reading List
RTE Role
Kanban Basics
Continuous Integration
Lean Agile
Agile Assembly Architecture
Presentation
Agile Delivery
Scrum.org
LPM
Applying Agile Methodology
Agile Israel Events
Implementing SAFe
ARTs
A Kanban System for Software Engineering
Acceptance Test-Driven Development
Scrum and XP
Story Slicing
User stories
Kanban
What Is Kanban
Tips
Self-organization
Sprint Retrospectives
Lean Agile Management
Agile and DevOps Journey
Continuous Delivery
Continuous Improvement
Code
Large Scale Scrum
Business Agility
SAFe Release Planning
System Team
Managing Risk on Agile Projects
Agile Testing Practices
Artificial Intelligence
Scrum Master
Jira Cloud
Lean Startup
Kanban Kickstart Example
Team Flow
Certification
Tools
Professional Scrum Master
Lean Agile Organization
agileisrael
Lean-Agile Software Development
Agile Community
Quality Assurance
Product Management
RSA
Spotify
Systems Thinking
Lean and Agile Principles and Practices
Agile Product Ownership
Portfolio for Jira
SAFe
Covid19
Agile Games and Exercises
Advanced Roadmaps
Nexus and SAFe
ALM Tools
BDD
Software Development
Amdocs
Professional Scrum with Kanban
Accelerate Value Delivery At Scale
Lean Budgeting
ART Success
Agile in the Enterprise
Achieve Business Agility
ScrumMaster Tales
Lean Agile Basics
chatgpt
Scrum With Kanban
Lean Agile Leadership
Operational Value Stream
Games and Exercises
Principles of Lean-Agile Leadership
Introduction to Test Driven Development
Agile Games
System Integration Environments
Process Improvement
Risk Management on Agile Projects
Agile Release Planning
QA
Introduction to ATDD
Risk Management in Kanban
Agile
Limiting Work in Progress
Agile Marketing
Built-In Quality
Lean Risk Management
Agile Israel
Product Ownership
Test Driven Development
Kanban 101
PI Planning
Agile India
Software Development Estimation
Kaizen Workshop
IT Operations
Kanban Game
Iterative Incremental Development
DevOps
Rapid RTC
Scrum Master Role
Value Streams
Agile Project Management
Lean-Agile Budgeting
Agile Development
Implementation of Lean and Agile
Agility
WIP
Continuous Planning
Agile Release Management
Engineering Practices
ATDD
GanttBan
Development Value Streams
lean agile change management
SA
Elastic Leadership
Perfection Game
Risk-aware Product Development
ATDD vs. BDD
Agile Techniques
Legacy Code
Entrepreneurial Operating System®
Hybrid Work
LeSS
Video
System Archetypes
Nexus
Professional Scrum Product Owner
Sprint Iteration
Legacy Enterprise
AI Artificial Intelligence
Agile Contracts Best Practices
Keith Sawyer
Planning
Release Train Engineer
PI Objectives
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart