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:

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