Optimising engineering team delivery using the Cycle Time metric

Dimitri Koubaroulis
7 min readbeginner
--
View Original

Overview

The article discusses the importance of the Cycle Time metric in optimizing engineering team delivery at SafetyCulture. It emphasizes how measuring and visualizing flow can enhance productivity, predictability, and team morale, ultimately leading to improved delivery health.

What You'll Learn

1

How to measure cycle time effectively for your engineering team

2

Why optimizing flow is more beneficial than focusing on velocity

3

How to use JIRA and plugins to visualize cycle time trends

4

When to take corrective actions based on cycle time data

Prerequisites & Requirements

  • Understanding of agile methodologies like Scrum and Kanban
  • Familiarity with JIRA for work management

Key Questions Answered

What is cycle time and why is it important for engineering teams?
Cycle time is the duration from when work starts on a task until it is completed. It is crucial for engineering teams as it helps measure the flow of work, predict delivery timelines, and identify areas for improvement, ultimately enhancing delivery health.
How can teams optimize their cycle time?
Teams can optimize their cycle time by measuring and visualizing it, discussing stability with team members, and implementing corrective actions when cycle times exceed healthy ranges. This leads to productive conversations and actionable insights that can enhance delivery.
What tools can be used to track cycle time effectively?
JIRA's built-in cycle time reports and the 'Actionable Agile' plugin are effective tools for tracking cycle time. These tools allow teams to visualize trends, analyze data, and derive actionable insights to improve their delivery process.
What are the benefits of focusing on flow over velocity?
Focusing on flow rather than velocity provides a clearer understanding of delivery health in terms of customer value. It improves predictability, streamlines operations, boosts team morale, and allows for agility in process changes, making it a more effective metric for teams.

Key Statistics & Figures

Average cycle time
5.3 days
This average indicates the typical duration for task completion within the team.
Percentage of tasks completed within average cycle time
64%
This percentage reflects the efficiency of the team's delivery process.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Project Management
Jira
Used for managing work and tracking cycle time metrics.
Plugin
Actionable Agile
Enhances JIRA's capabilities for tracking and visualizing cycle time.

Key Actionable Insights

1
Regularly visualize your team's cycle time to identify trends and spikes.
By keeping track of cycle time trends, teams can proactively address issues before they escalate, ensuring a smoother delivery process.
2
Engage in discussions with your team when cycle time is unstable.
These conversations can lead to valuable insights and corrective actions that stabilize cycle time, enhancing overall team performance.
3
Utilize JIRA plugins to enhance your cycle time tracking capabilities.
Plugins like 'Actionable Agile' provide deeper insights and visualization options, making it easier to analyze cycle time data effectively.
4
Aim for a cycle time of 3-5 days for optimal delivery health.
Setting a target cycle time helps teams maintain a steady flow of work, ensuring timely delivery of value to customers.

Common Pitfalls

1
Failing to address spikes in cycle time can lead to prolonged delivery issues.
Without timely intervention, teams may experience delays in their delivery process, affecting overall productivity and morale.
2
Overemphasizing velocity can obscure true delivery health.
Focusing solely on story points may mislead teams about their actual performance and hinder their ability to deliver customer value effectively.

Related Concepts

Agile Methodologies
Scrum And Kanban Frameworks
Cycle Time Optimization Techniques