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:

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