Lucas F. Costa • 8/31/2022

Useful engineering metrics and why velocity is not one of them

Read Original

This article critiques the use of velocity and burndown charts in software engineering, comparing them to horoscopes for their lack of actionable insight. It proposes modeling an engineering team as a queueing system and details core metrics like arrival rate and throughput to better monitor performance, identify bottlenecks, and improve predictability.

0 comments
#software development #agile #Team Productivity
Useful engineering metrics and why velocity is not one of them

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes