Refactoring

Refactoring

Share this post

Refactoring
Refactoring
Why You Should Measure Cycle Time ➰
Copy link
Facebook
Email
Notes
More

Why You Should Measure Cycle Time ➰

A primer on the most popular engineering metric.

Luca Rossi's avatar
Luca Rossi
Feb 12, 2021
∙ Paid
7

Share this post

Refactoring
Refactoring
Why You Should Measure Cycle Time ➰
Copy link
Facebook
Email
Notes
More
2
Share

Hey 👋 this is Luca! Welcome to a 🔒 weekly edition 🔒 of Refactoring.

Every week I write advice on how to become a better engineering leader, backed by my own experience, research and case studies.

You can learn more about Refactoring here.

To receive all the full articles and support Refactoring, consider subscribing 👇

Become a better tech leader ✨


Last week we explored software delivery metrics and how they predict overall engineering efficiency.

This week I follow up, with a broader scope, to discuss my favorite metric of all: Cycle Time.

📈 The Rise of Engineering Analytics

Over the last couple of years, several analytics tools rose to support a data-driven approach to Software Engineering.

You may (or may not) know a few of them: LinearB, Code Climate, Waydev, Flow.

They connect to your code hosting (e.g. Github) and automatically create measures based on commits, PRs, and releases.

Among these measures, I would argue that Cycle Time is the most significant one. To the point that if you had to focus on just one KPI for your dev process, it should probably be it.

Let's see what it's all about.

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2025 Refactoring ETS
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More