I want to track the cycle time
- Derya Özdemir
Context: A team lead wants to track the cycle time of issues to identify bottlenecks and improve team efficiency.
User Problem: Tracking the lead time (time from when a task enters the system to when it's delivered) and cycle time (time spent actively working on a task) is essential for improving team performance, especially in Agile environments where continuous improvement and transparency are key. However, I don't have an easy way to monitor this in real-time.
Solution: Time to SLA allows you to track lead time and cycle time directly in your workflows, making it an invaluable tool for Agile and Kanban teams. By visualizing the flow of work and identifying bottlenecks, you can optimize your processes, reduce waste, and deliver value faster.
You can track cycle time through the SLA history feature, which is a helpful tool that displays a record of all the states of your SLA, organized into cycles. Here you can select which SLA’s history you want to view, as well as export it.
Each cycle is made up of a Start and End condition, and by examining your SLA history, you can easily see how long people spent between those conditions, along with all the different statuses of the SLA, like met or exceeded. Whenever an SLA is stopped, the existing cycle will be completed as met or exceeded. And when the issue is reopened, a new cycle starts.
