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:

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