Go to Plandek
All Collections
Metrics and Metrics Settings
Metrics and Metrics Settings
Collection of articles explaining the metrics available in Plandek and the various metric settings
50 articles in this collection
Written by
Will Lytle
and
Luke Thomas
Ticket Scope
Choose your sprint and see how the scope of that sprint changed, seeing added and removed tickets each day
Written by
Will Lytle
Updated over a week ago
How is Rolling Average calculated?
Written by
Will Lytle
Updated over a week ago
Created pull requests
The number of pull requests created on your code repositories
Written by
Will Lytle
Updated over a week ago
Filters
Decide the data you do and don't want to see to make each metric specific to your context and need
Written by
Will Lytle
Updated over a week ago
Change Failure Rate
Identify the percentage of deployments which fail and the overall risk this poses to development
Written by
Will Lytle
Updated over a week ago
Backlog Health
Understand how healthy your backlog is and if your change pipeline is in the correct state to support delivery
Written by
Will Lytle
Updated over a week ago
Average Duration
Highly flexible metric that can be used to calculate response times along with MTTR using ticket data.
Written by
Luke Thomas
Updated over a week ago
Code Cycle Time
Core to your engineering and delivery capability is the Pull Request process, and this metric will give you key insight into its efficiency
Written by
Will Lytle
Updated over a week ago
Breakdowns
Slice each metric the way you want to compare and contrast data trends across a large variety of factors
Written by
Will Lytle
Updated over a week ago
Metrics settings overview
Learn how to harness the power of Plandek through our robust set of metric settings
Written by
Will Lytle
Updated over a week ago
Sprint Flow
Track exactly how tickets are progressing throughout a Sprint, enabling you to spot potential risks to meeting your Sprint goals
Written by
Will Lytle
Updated over a week ago
Active work metric
Ensure your work aligns with business priorities and enables focus across your value streams. Can be used for Flow Distribution
Written by
Luke Thomas
Updated over a week ago
Code knowledge
How well is knowledge spread across your engineering teams? By looking at the relationship between PR author and commenters we can find out
Written by
Will Lytle
Updated over a week ago
Release/Fix Version Flow
Track progress against a specific release or fix version, for those teams and programmes who are very release or project oriented
Written by
Will Lytle
Updated over a week ago
Ticket/Story Points Flow
Track how a release, sprint, project or some other scope of work is evolving over time to spot any potential risks to your delivery
Written by
Will Lytle
Updated over a week ago
Removing Outliers with percentiles
Exclude statistical outliers by refining the range of data included in certain key rate metrics
Written by
Will Lytle
Updated over a week ago
Mean workflow cost
Written by
Will Lytle
Updated over a week ago
Ticket commit hotspots
Highlights the relationship between your tickets and the affected number of files in your codebase
Written by
Will Lytle
Updated over a week ago
Story points scope
Choose your sprint and see how the scope of that sprint changed, seeing added and removed story points each day
Written by
Will Lytle
Updated over a week ago
Time between deployments
Measuring the mean average of time between the deployments
Written by
Will Lytle
Updated over a week ago
Speeding transitions rate
Sometimes tickets are moved through transitions/statuses faster than we might expect
Written by
Will Lytle
Updated over a week ago
Deployment data
Limit the tickets you see in Delivery Time & Code Cycle Time to only those that have been part of a Production Deployment
Written by
Luke Thomas
Updated over a week ago
Ticket complexity
Using a variety of different measurements you are able to understand the complexity of completed tickets
Written by
Will Lytle
Updated over a week ago
Mean time to resolve PRs
Pull requests are an important part of the development process, but how quickly are they being reviewed and merged?
Written by
Luke Thomas
Updated over a week ago
Total workflow cost
Written by
Will Lytle
Updated over a week ago
Percentiles
Rather than just the mean average, you can also calculate an exact percentile value where needed in our metrics
Written by
Will Lytle
Updated over a week ago
Unresolved tickets story points
All the same views as Unresolved Tickets of backlogs, work in progress, and burndown charts but organised by Story Points
Written by
Will Lytle
Updated over a week ago
Workflow / Build Failure Rate
Written by
Will Lytle
Updated over a week ago
Frequency of deployments
Summarised as a number of deployments per day, a great core metric to monitor as you strive toward continuous delivery
Written by
Will Lytle
Updated over a week ago
First Time Pass Rate & Return Rate
Do tickets pass through your workflow from left to right in one clean pass, or are returns and defects affecting your delivery
Written by
Will Lytle
Updated over a week ago
Unresolved tickets
An incredibly versatile metric allowing you to create views of backlogs, work in progress and related burndown charts
Written by
Will Lytle
Updated over a week ago
Sprint Override
All of our ticket based metrics can be 'filtered' purely based on specific sprints, including dynamic options (last and current)
Written by
Luke Thomas
Updated over a week ago
Unit of Measurement
You don't need to be limited to ticket count and story points, you can measure tickets with any numeric field you want
Written by
Luke Thomas
Updated over a week ago
Mean Time To Recover from Workflow Failures
Written by
Will Lytle
Updated over a week ago
Number of deployments
Get full visibility of production deployments across all your CI/CD pipelines
Written by
Will Lytle
Updated over a week ago
Mean Time Between Workflow Failures
Written by
Will Lytle
Updated over a week ago
Sprint (target/work added) completion
Core Scrum metric so you can understand the overall success of your sprints and a closer look at the outcome of tickets at sprint end
Written by
Will Lytle
Updated over a week ago
Mean Workflow Time
Looks at the mean average of workflow run times
Written by
Will Lytle
Updated over a week ago
Make dashboard chart
Choose the best visualisation for each metric card that you want to make available on the dashboard view
Written by
Will Lytle
Updated over a week ago
Returned tickets
Great way to see tickets that have moved the wrong way in your workflow, and you get to choose the 'return' transitions
Written by
Will Lytle
Updated over a week ago
Delivery time
Time is a critical factor in software delivery, so being able to understand Lead/Cycle time and potential bottlenecks makes this a must-have
Written by
Will Lytle
Updated over a week ago
Number of Workflows
The raw count of the number of workflows that have been run
Written by
Will Lytle
Updated over a week ago
Flakiest Files
A sorted list of files in the codebase and how frequently a commit resolves in a failed build
Written by
Will Lytle
Updated over a week ago
Created tickets
Get an instant view of the created tickets across your ticket data, allowing the usual flexibility in breakdowns and filters
Written by
Will Lytle
Updated over a week ago
Completed tickets story points
If you use Story Points then this will allow you to explore the total completed by a variety of different perspectives
Written by
Will Lytle
Updated over a week ago
Completed tickets
A simple but highly configurable way to understand what you are delivering, either by ticket count, story points or any numeric field
Written by
Will Lytle
Updated over a week ago
Commits without a ticket reference
If you need full audit history between your tickets and your code commits, then you'll want to see the gaps this metric highlights
Written by
Will Lytle
Updated over a week ago
Flow efficiency
Do your tickets spend time queuing? Find out the active vs inactive time of your completed tickets
Written by
Will Lytle
Updated over a week ago
Commits without a pull request
If your process defines that every commit should have a related pull request, then this will tell you when they don't
Written by
Will Lytle
Updated over a week ago
Commits Count
Pure engineering metric looking at all commits to all branches for the in-scope code repositories
Written by
Will Lytle
Updated over a week ago