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:

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