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