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:

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