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:

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