Features

We are working agile and customer driven.
We are listening to you as our customers giving us valuable feedback and input to improve this product by your needs!


Which problem do we solve


After launching Agile Notebook Tool for SCRUM Masters which includes basic KPI measures managers approached us to deliver a special version only to gain and deliver data prepared for managers and leads.
Most of them use tools measuring DORA metrics and efficiency by data gathered due to Git examination, DORA does not makes sense if the team depends on other teams and does not own the whole process.

To figure out team's performance is quite complex and it is not sufficient using only cycle time, pull requests time or rejections or simply velocity.
At first place we have to have a look if the agile implementation is efficiently implemented and if it is supportive before paying attention to the technical excellence. Because without a well working project or agile workflow, having the right “definition of ready” and “definition of done”, which heavily influences the technical execution, we cannot derive the right measures and root causes for broken technical flows and why the team is not performing.


How do we solve


Performance view:

Tells you the current velocity, is the estimation stable, how much work do we have in front of us, gives you insights about how much is the technical debt, helps you to calculate the sprint capacity in absence of some members.
Provides historical data about gone sprints and allows to make forecasts about future sprints and if they are properly planned.

Statistics view:

Helps you to find bottlenecks in the process and to ask the right questions.
It shows items first response time, duration, how often a status change backward happened, i.e. from review to in progress and the time an issue stayed in a stage.
Furthermore it gives insights who worked on what, how many persons participated on an item and who did something.

History:

This view provides historical data about the development over the time like velocity, open and closed stories, bugs and technical debt to plan your strategy better. What did we achive regarding feature and technical initiatives, how many defects appeared and how is their development over time?
Did the QA improve? Does the teams work up technical debt and defects and what is their distribution.

Policy check:

The policy check checks with various rules if the agile process is followed and if the SCRUM master or project manager pays attention to the Jira usage.
Example policies are if there is an unestimated story in a sprint or an item in progress has no assignee.

VCS KPIs

Gives you a developer performance index based on VCS activity to identify developers real impact.
See commits per developer per day or per repository to identify if they worked on certain topics.
It also shows the overall code contribution, how many lines added and removed in total.


Screenshots