DEV Community

Discussion on: How do you measure engineering performance and process healthiness?

Collapse
 
georgeguimaraes profile image
George Guimarães

Hey, Stephen

Thanks for the answer! I stopped estimating User Stories in Story Points because I've seen the team having time-consuming discussions on whether a given US worth 1 or 2 points.

So, instead of estimating, I like to have some discussions on "how to implement given User Story." It's a good practice that aligns the team and turns anyone eligible for developing it later. In other words, it avoids queues and improves the overall speed of development.

So, instead of measuring Story Points, I rather measure the number of delivered User Stories.

When it comes to the metric from when the ticket first goes to "in progress" to "complete", I'm total with you!

I call this metric Lead Time, however, some people call it Cycle Time. I explained why I don't like Cycle Time in this article.

I also wrote another blog post called 50 Shades of Lead Time that explain how to apply this idea to other steps of software development.