Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

From Utilization to Done

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

There is this thing.

It’s coming up again and again.

I would say it is the root of all evil.

At least some of it.

I am referring to the need of many software development managers to make sure all their employees are fully utilized. It usually surfaces when you start talking about real team work or about agile execution.

Having all your employees fully utilized is not a bad thing for itself. It is just not the goal. The goal is to get software development done. The problem starts when “people fully utilized” gets in the way of getting software development done.

Making a sprint plan with people having exact tasks for the next two weeks is a very good way to make sure everyone are busy. This will also kill flexibility to respond to arising issues, something that usually happens in software development. Making a sprint plan with just a list of stories and then assigning people per need is a good way to make sure stories get done.

Having a daily meeting, asking each person for what they did yesterday and their plans for today is a good way to make sure people are working. having the daily meeting around stories and what happened with them yesterday and the plan for today is a good way to make sure they will get done.

Should we get stories done at all costs? No. We should balance between speed and throughput, depending on our context. In some places speed is more important,  in others throughput. However, it seems that “people fully utilized” is so prevalent we can safely give it some blows and it will still be there , guarding us from doing really silly stuff.

Once you get the utilization thing off your mind things become easier. This is because suddenly you have one clear goal – getting these stories done. Remember – this is your real goal. And don’t worry about the people, they will find something to do.

 

 

Subscribe for Email Updates:

Categories:

Tags:

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