The Azure Boards integration is now available to help you visualize sprint progress, understand the costs behind unplanned work, see how much each feature and epic costs, and more.

Learn how to integrate with Azure Boards here.

We're excited to introduce our new budgeting reports. As an engineering executive, you can now see how much each feature and epic costs, understand the costs behind unplanned work, bug fixing, and visualize the progress for each of your key business initiatives. Read more about the new reports below.

Project Costs - Accelerate Innovation and Maximize Business Impact

Resource Planning - Visualize the Financial Costs of Engineering Work

These reports are available for Jira users at the moment. You can access the new features in the Reports section.

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.

We're excited to announce our new design! It features a more friendly user interface and usability improvements that effectively convey our vision of engineering leadership. View more snippets of our new design below.

Developer Summary Redesigned

The new Developer Summary report is designed to help you visualize work patterns and track individual progress over time. With it, engineering managers can quickly spot and eliminate any blockers that are holding their team members down. 

Gain a better understanding of what's going on before one-to-ones and add a layer of data to performance reviews with the Developer Summary.

Team Performance Overhaul

The new Team Performance report was developed to help engineering executives build customizable high-level performance reports.

We’ve brought our new brand positioning and visual identity system to life on our website with a better articulation of how Waydev can transform engineering work metrics into impactful decisions for technology organizations across the globe.

We've added PR stats in the Team Progress and the Developer Progress features. Learn more about Team Progress and Developer Progress.

If you want to hide developers' names from other users on the platform, you can do it by following this guide.

We've just launched our integration with Azure DevOps Server. Learn more about integrating Azure DevOps Server here.

The Activity Heatmap feature now displays the time zone used for the stats.

We added Throughput, Productive Throughput, and Commits/ Active Day in Targets. Learn more about Targets.

You can now view more than 5 engineers in the Work Log, using the 'Per Page' filter.

You can now sort individual engineer stats in the Dashboard. You can do this by clicking on each metric's name.

We’re thrilled to announce that Hiten Shah decided to hunt us on Product Hunt today! Since our last launch, we’ve managed to add Pull Request stats and Tickets stats using the integration with Jira and soon Azure.

I would be delighted to have your upvote and know your feedback. Without feedback from our community, we wouldn’t have made it to this point. Thank you, Waydev Community!

We've added trendlines that help you track the evolution for each metric in the Developer Performance, Team Performance, and Repositories Stats reports. Click on any metric to display its trendlines.

We've worked with our customers' feedback to develop metrics that reflect the Pull Request Velocity. You can now visualize the average duration for each step of the pull request cycle. 

We also built quantitative pull request metrics, such as the number of pull requests merged without rebasing, the number of pull requests merged without review, and more.

You can find the Pull Request Velocity metrics in the Developer Performance, Team Performance, and Repositories Stats reports. Click on the Pull Requests Stats button to toggle the Pull Request Velocity metrics.