Track you team's lead and cycle times to understand how quickly your team can introduce new features to your end users. You can filter the data according to task type so that you can track a specific aspect of your work such as bugs, user stories, or support tickets. 



Lead time is the total time that elapses from the creation of a task until its completion. 

Reaction time is the time that elapses from the creation of a task until the work is started.

Cycle time is the total time that elapses from the moment when the work is started on a task until its completion.



Lead time trend shows your average lead times during the last 30 days. The blue area, cycle time, shows how quickly tasks are completed once the work is started on a task. The yellow line shows the average number of tasks in progress (WIP) at any given time.  



A breakdown of Reaction times and Lead times shows the actual distribution (histogram) for the tasks completed during the last 30 days, providing insight on a category level. That helps in spotting anomalies, which can go unnoticed when looking at averages only. 


Learn more

Common questions

How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?

Cycle time is calculated only for completed tasks so in both of those cases cycle time would be undefined.

When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?

The clock starts when a task is moved to a workflow state that is mapped to "open" or "in progress" workflow state.  

Are weekends included in the cycle time calculations?

At the moment weekends are always included in the cycle time, as are non-business hours.

If a card is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?

Cycle time is counted only when task is in progress so the time spent on "done" state is not included in the calculation. 

How is the reaction time calculated?

Reaction time starts running when a task is moved into a state that is mapped to the "open" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “open” workflow state, then the reaction time is zero.