Agile KPIs – iceScrum

Documentation This documentation applies only to iceScrum v7.
For old iceScrum R6, read the documentation or migrate.

More advanced indicators (such as Lead Time and Cycle Time) to improve inspection and adaptation.

Agile KPIs


Out of the box, iceScrum offers a wide choice of agile indicators that you may expect in any good agile tool. When your license allows it, this App is enabled by default and offers additional indicators available as widget that you can add to your dashboards. There are great tools to incorporate in your team’s toolbet in order to improve inspection and adaptation.

Cycle time (Stories)

In iceScrum, the Cycle Time is the average time taken for a story from the moment the team starts working on it until it is completed. It is often used in Lean / Kanban, but it can be a great addition to Scrum as well as it encourages improving the flow of stories and reducing bottlenecks and stocks.

In iceScrum, the moment a team starts working on a Story is deduced from its tasks: it’s the time its first task is at least “In progress”. The completion date is the moment a story is marked as “Done” (which can be done in the middle of a sprint, at the end of the sprint, automatically or manually…).

Data is gathered only one done stories, for a period of 90 days (roughly 3 months) before the last story has been marked as “Done”.

For this indicator to be meaningful, it requires that the team splits stories into tasks and update them on a regular basis.

Ideally, you want the Cycle Time to be significantly lower than a sprint duration, which means that stories are delivered on a regular pace and that the team does not suffer from the “tunnel effect”.

Lead time (Stories)

In iceScrum, the Lead Time is the average time taken for a story from the moment it is defined until it is completed. It is often used in Lean / Kanban, but it can be a great addition to Scrum as well as it encourages improving the flow of stories and reducing bottlenecks and stocks.

The moment a story is defined may vary depending on what you mean by “Defined”, that is why you may choose among three dates as the starting point: the moment a Story is “Suggested”, “Accepted” or “Estimated”. The completion date is the moment a story is marked as “Done” (which can be done in the middle of a sprint, at the end of the sprint, automatically or manually…).

Data is gathered only one done stories, for a period of 90 days (roughly 3 months) before the last story has been marked as “Done”.

Ideally, you want the Lead Time to be as short as possible, as it represents the time taken to answer a need that has been identified. The Lead Time is broken down into the time spent at each state in between so you can identify bottlenecks and take appropriate action.

Throughput (Stories)

In iceScrum, the Throughput is the number of stories completed per rolling week. It is often used in Lean / Kanban, but it can be a great addition to Scrum as well as it encourages improving the flow of stories and reducing bottlenecks and stocks.

It is calculated only for the current release, as it is meaningful only for continuous periods of work. It is averaged up to a 4 weeks range if data is available in the current release.

For this indicator to be meaningful, it requires that stories are completed on a regular basis. It also requires that stories are roughly the same size as the effort is not taken into account.

Ideally, you want the Lead time to be high, which means that there is a great flow of completed stories and little tunnel effect.


Try it for free now
All you need for your Agile project management