Cycle Time

Cycle time dashboard

Cycle Time is the amount of time a team/ person spends actually working on a work item up until it is ready for delivery. It is among the most widely tracked metrics among engineering teams and a great way to identify bottlenecks in the development process. Since cycle time begins at the time of coding and ends with deployment, it gives a complete and holistic view of all the steps in the process, what's working, and what's not.

In other words, it refers to the period of time from an engineer's first commit to the deployment of code.

Cycle Time dashboard

Simply put, the cycle time dashboard helps you `identify bottlenecks and pain points by tracking PR cycle times``.

Apps powering this dashboard

  1. Git/VCS apps
  2. CI-CD tools

Check out all apps supported by Hatica here

Available filters

  1. Date range picker
  2. Repo
  3. View by Teams (managed teams, custom teams) and individuals

Some reasons to use this dashboard

  • Understand the velocity, for selected teams or selected repositories, from first commit to deployment
  • View the Pull Requests on a particular day, which results in the cycle time value of that day
  • Gain visibility into how long each stage of the cycle time takes for your team(s)

Different ways to reduce your cycle time

  • Starting small and fast: You can deliver more by starting with smaller PRs and producing customer deliverables quickly.
  • Automate, automate, automate: Use automated tools to save efforts and delivery time. You can implement continuous integration through automated releases and invest the remaining time in coding.
  • Slicing the giant PR: Breaking the work items into smaller chunks and iterating frequently enables your team to perform better. It also reduces the pickup time and review time for the pull requests significantly. The general industry standard for PR size is 300 lines of codes(LOC).

Further reading