Market Leader in Development Analytics
(G2 Crowd’s Winter, Summer & Spring 2022)
Backed by Y Combinator
experience featured in TechCrunch
New Case Study:
Learn how Carrier (Fortune 100 enterprise company) leverage Waydev
Learn how to gain visibility into your engineering teams and accelerate your product velocity.
Get all the updates, at each step, without any manual input from your engineering team. Waydev supports you to effectively manage and track all your software development projects.
See high level stats and work patterns or zoom into specific activities, know when your sprint is at risk, understand what most of your team’s time is spent on.
As a manager, it’s important to know how everyone is doing individually and as a team. Managing big development teams is no walk in the park. You have to juggle several activities, join long meetings, lead unproductive stand-ups, and then hopefully, get some work done. Gain a bird’s eye view of your team’s output and work habits.
How to use the Work Log
The Work Log report helps engineering managers make decisions backed by data, set expectations proactively, and help their team improve over time.
The Work Log helps managers gain visibility into their onboarding process, understand where their team is focusing their attention, or notice when there’s an unexpected spike in activity.
As you can see, the Work Log is a powerful new way to manage your engineering team more effectively. Use it to:
Click any item in the Work Log report to zoom in and find out valuable information, such as:
Additionally you can:
Keep a pulse on your sprint progress. Visualize and mitigate sprint risk using our forecast model.
The Sprints feature can be found in the Daily Stand-Ups submenu and provides an overview of your active sprints. It helps you visualize whether your sprint is at risk, where team members may be over capacity, or whether they are falling behind with work. Keep a pulse on your sprint progress. Visualize and mitigate sprint risk using our forecast model. Identify capacity issues and scope creep.
How to use the Sprints feature
The red bar indicates the current day in relation to the sprint, while the green bar points out the sprint progress in relation to the elapsed time from the sprint start. We gather evidence from multiple data points in order to provide a forecast of your sprint risk.
The Issues list, situated below the sprint risk forecast comprises all the Issues in the sprint and you can view:
If there is no avatar next to the identifier, it means that the Issue is unassigned.
You can view the Open Issues, Closed Issues, and Issues that Need Attention. You can sort the table by identifier, status, time in progress, and story points.
You can select another team by clicking on the team name on the upper left side of the page.
Your weekly and monthly reports are all stored and can be found in one place. You can choose to view or download them, so you needn’t worry about going through your email to find a report.
You can sort reports by team and period. On the rightmost side of the page, you can either view the report or download it as a PDF.
Find out where your engineers’ work focus is. View how events impacted your team’s performance over time and direct your data-driven decisions.
How to use the Project Timeline Feature
The Project Timeline helps you visualize how teams are doing relative to other teams, relative to industry benchmarks, and relative to your own trends, by using four metrics that customers find most actionable in the code-based activity. These metrics are:
In the Project Timeline, you can visualize how those metrics are trending during the sprint or over the trailing week, month, quarter, 6-month period, or a custom time frame.
Commits per Active Day
Commits per Active Day measures the average number of commits per active author per active day. If you consistently see that your team had several commits every day, this means that they’d been working almost every day of the week, including weekends. The team may have too much on their plate, and it’s time for some expectation, realignment upwards in the work funnel. This is worth making a note of before a retrospective begins so it can surface tactfully into your team discussion.
On the other hand, if the Commits per Active Day is unusually low for the team compared to prior periods, that might be a signal that something outside the normal delivery process is slowing them down.
Total Impact metric
Total Impact helps you and your team understand the general complexity of changes that your team is moving forward in your product.
The Project Timeline will help you and your team quickly see signals of process blockers affecting the health of your software development process during conversations in your retrospectives. Use this data to generate an open conversation around team-led expectations versus actuals to provide a platform for innovative ideas that otherwise may have passed with the agenda items.
This report provides a view of how work trend evolved over time. Use this visualization to spot any irregularities and spikes, such as high spikes of Churn.
You can also see the top performers for each metric:
With Waydev’s tracking features it is now easy to keep a pulse on your your engineers’ performance through weekly and monthly detailed reports.