You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Dealing with multiple tasks and plans and ensuring that team members finish their work within the given time can be challenging task. However, to address this challenge, it is essential to establish an efficient monitoring system that can keep track of deadlines and provide better control over team performance. Regularly calculating Cycle and Lead time is integral to achieving this goal. Time between Statuses can help you with this.
But what exactly are Cycle and Lead time? Let's explore this further.
Cycle time refers to the time it takes to complete a particular action from start to finish while the task is in progress.
Lead time covers a more extended period, starting from when a request for action is made (not when work commences) until the task is completed, including any time spent waiting in a queue.
Time Between Statuses is a Jira add-on that allows you to track the time it takes for an issue to move between different statuses in your workflow. By measuring the time between each status change, you can get a more accurate picture of your project's cycle time and lead time and identify areas for improvement.
Here's how to use Time Between Statuses to monitor cycle time and lead time:
1. Define your workflow: Before you can start tracking cycle time and lead time, you'll need to define your project's workflow. This involves setting up different statuses that represent the various stages of your project's development. For example, you might have statuses like "To Do", "In Progress", "Review", and "Done".
2. Default 24/7 calendar or your working calendar (excluding non-working time).
3. Configure Time Between Statuses: Once you've defined your workflow, you'll need to configure Time Between Statuses to track the time between each status change. This involves setting up the statuses you want to track and defining the periods you want to measure.
4. View the Time Between Statuses report: Once you've configured Time Between Statuses, you can view the Time Between Statuses report to monitor your project's cycle time and lead time. The report displays the time it takes for an issue to move between each status and the average time it takes to move between each status.
5. Use the data to improve your workflow: By analyzing the Time Between Statuses report data, you can identify areas where your workflow can be improved. For example, if issues take a long time to move from "In Progress" to "Review", you may need to adjust your process to streamline this transition.
Cycle time and lead time are critical metrics that can help you optimize your project workflow and productivity. Time Between Statuses by SaaSJet is a powerful tool that can help you monitor these metrics by tracking the time it takes for issues to move between different statuses in your workflow.
We are pleased to offer to you a 30-day trial of Time Between Statuses. Furthermore, our add-on is available for free for up to 10 users, allowing you to evaluate its effectiveness in your service processes.
5 accepted answers