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:

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