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:

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