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:

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