Every Project Manager wants to reduce waste on their projects. The problem usually lies in detecting which parts of the process are ineffective. We are introducing the Cycle Time Report to help you deal with this exact issue.
End To End Lead Time
First of all, the End To End Lead Time is there to show you the overall pace of your team. It is the median time in which the ticket goes from being created to being closed. This includes all the steps in your process - analysis, planning, delivery, etc. This metric is great for strategic planning and the overall overview on the team's efficiency.
Delivery Lead Time
Delivery Lead Time helps you drill down to only the delivery step. You are doing analysis and planning while the ticket is in the Assembla Planners Backlog Milestone and moving it to Current Milestone when it is ready to be worked on. Delivery Lead Time will show you exactly how much time a ticket spends in your delivery pipeline. This metric (when compared to End To End Lead Time) will show you how effective you are at planning and analysis.
Analyze the delivery step further with Cycle Time. This will eliminate all the waiting. In a pull system, tickets in status "New" are waiting until a developer picks it up and works on it. Cycle Time will show you how much time a ticket spends in every other status, waiting in "New" eliminated. This metric (when compared to Delivery Lead Time) will show you how much waiting you have in your Current pipeline and which steps on the process are the slowest.
For each of these metrics, we show the median value and the standard deviation. If your standard deviation is high, you can not trust the median. First step in optimizing your process will usually be making sure that you can get standard deviation as low as possible. Most common reason for this is tickets being too different in development effort needed. Try to break down bigger tasks into smaller ones.
What is the relative cost of a software bug fix? Some sources state up to 150-fold increases in costs of fixing bugs in latest steps of the pipeline. Time Cycle Report will show you the quality percentage in your tickets. 85% means, that 85 out of 100 of your tickets go through your pipeline without any hiccups - developers do not throw the issue back to analysis, Quality Assurance does not find bugs, etc. Any status regression in the ticket will decrease the quality. This is the best place to start with the Time Cycle Report.
Use Cases for the Time Cycle Report
This is far from everything an insightful manager will do with this report, but it might give you some ideas:
Reduce disruption that impacts efficiency, quality, and value - look at what parts of the process are slowest and ask yourself why that is
Create Service Level Agreements - agree with your team that tickets should be delivered on your prefered time scale and easily monitor your team's success
Continuously improve - track the overall Quality rating of your tickets. This is one of the easiest ways to ensure that you are improving
You can find the Time Cycle Report in the Metrics subtab of your Tickets Tool. Share the insights that you have got from the Time Cycle Report in the comments!
This report is available with the Renzoku feature pack. Subscribe for your free project here!