Story point estimation computer

Story point estimation doesn’t matter on the wrong things

Back with a somewhat controversial topic. I find estimation for the sake of estimation a waste of time as teams generally focus on the wrong items in the backlog and agonize over the stuff that really doesn’t matter. What really matters is that top 15% which is truly important for the organization and your customers. That’s what you should focus on and leave the rest to discussions. Really, Why don’t you think story points matter? It’s not that I think they don’t matter, I think they’re an inefficient use of time for most teams. Here’s more to it: My team

Cycle time formula

Cycle time formula in software delivery

It’s been a bit busy but I’m back with a requested article. How to calculate cycle time via a formula. This will be a quick article as calculating cycle time is really quick. For more in depth information, make sure you check out my article on DORA metrics and WIP limits. With that said, let’s define cycle time and go from there. What is cycle time? Cycle time in software delivery is a key metric used to measure the efficiency and effectiveness of a development process. It’s the amount of time from when work begins on a piece of software


Cycle time definition in software delivery

Back with a quick article today. I’m here to discuss the cycle time definition from a software delivery standpoint. Not to be confused with the lean approach from automotive industry. However, I will talk about it from a software delivery standpoint. For a really in depth guide and how to roll this out organizationally potentially, check out DORA metrics which can go hand in hand with a potential agile solution for your enterprise. It’s important to not get lost into frameworks and process. Make sure the customer feedback loops are short, high value is being driven and internal team members