We wanted to make this easier for you, so we’ve changed the naming of some features to better reflect their true purpose. Here is what we changed :

Velocity Report will help you determine the amount of work your team can cover, and become a useful tool for sprint planning meetings. You can visualize how much value each sprint delivers so you can accurately predict the team's workload for future sprints.

You can find the Velocity Report in the Sprints report, under the Daily Stand-Ups section. To enable the Velocity Report for your account, you'll need to integrate with Jira/ Jira Server/ Azure Boards

The report displays the number of story points completed vs the number of story points defined during a sprint.

The Azure Pipelines integration is now available to offer you insight into your pipeline activities. By integrating with your Azure Pipelines account, you'll be able to see how much time it takes for a PR to get deployed, from the moment it's merged. More metrics into CI/CD activities will be available soon.

Learn how to integrate with Azure Pipelines here.

The GitHub Issues integration is now available to offer you a complete view of what’s happening in your development process. 

Learn how to integrate with GitHub Issues here.

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 the option to compare engineer stats with team average stats using the Developer Progress feature. This will help you spot underperformers and identify coaching opportunities. Comparing engineer stats with team average stats can also help you discover top performers and recognize their wins.