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:

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