Waydev Changelog logo

Changelog

See the latest updates

Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement

Jump to Month

  • July 2026
  • May 2026
  • December 2025
  • November 2025
  • August 2025
  • June 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • August 2024
  • June 2024
  • April 2024
  • March 2024
  • February 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • August 2022
  • July 2022
  • May 2022
  • April 2022
  • March 2022
  • December 2021
  • November 2021
  • October 2021
  • August 2021
  • June 2021
  • May 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
Powered by

Create yours, for free!

Announcement
5 years ago

Introducing Cycle Time

We're excited to introduce one of the essential metrics for engineering organizations - Cycle Time! In essence, Cycle Time indicates how fast does code go from a developer's workstation to production. Studies show that measuring and improving the Cycle Time will enable organizations to innovate at a faster pace, while also improving their teams’ morale and sense of ownership.

The Cycle Time metric is an indicator of an organization's development velocity. The Cycle Time metric is the sum of four metrics, each of these metrics corresponding to a stage in the software development process:

  1. CODING - Time to Issue PR from First Commit. This metric corresponds to the coding time, and is the time elapsed from the first commit to creating a PR.
  2. PICKUP - Time to First Review. This metric indicates how fast do reviewers pick up their peers' PRs for review, and is the time between when a PR is opened and the first time an engineer reviews that PR.
  3. REVIEW - Time to Merge from First Review. This metric signifies how fast do submitters incorporate feedback from their peers in code review, and is the time from a PR's first review to that PR being merged.
  4. DEPLOY - Time to Deploy from Merge. This metric is an indicator for how fast does code get deployed into production, and is the time between when a PR is merged to when it gets released into production.

What does each color indicate? 

We've aggregated benchmark values from our platform for each stage of the cycle time. Green bars indicate leading values, yellow bars indicate average values, and red bars indicate below-average values.

For CODING:

  • Green: Less than 48 hours
  • Yellow: Between 48 and 72 hours
  • Red: More than 72 hours

For PICKUP:

  • Green: Less than 24 hours
  • Yellow: Between 24 and 72 hours
  • Red: More than 72 hours

For REVIEW:

  • Green: Less than 24 hours
  • Yellow: Between 24 and 72 hours
  • Red: More than 72 hours

For DEPLOY:

  • Green: Less than 10 hours
  • Yellow: Between 10 and 24 hours
  • Red: More than 24 hours

You can visualize your teams' cycle time in the Dashboard, Project Timeline, and Team Performance reports. Individual cycle time can be found in the Developer Summary, and Developer Performance reports.