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:

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