Metrics available in Plandek

See where in your codebase the most bugs have been fixed or where incidents are being resolved.

A great metric for ensuring that teams are aligned around the right areas that match your business objectives.

Ageing Work in Progress (WIP) is crucial for Kanban teams, exposing stalled items and bottlenecks. Addressing ageing WIP improves flow, ensures timely completion, and boosts team efficiency.

Tracks delivery variation across teams by averaging each team's volatility, providing an org-level view of delivery predictability.

Understanding which of your CircleCI workflows is costing too much to run can highlight candidates for optimization.

Monitoring build counts is crucial for ensuring adequate infrastructure support. Spikes may indicate issues like broken builds, prompting timely resolution.

A great metric for seeing pipelines that are failing and impacting developer efficiency, slowing down their ability to build and deliver software quickly.

A key metric in knowing how much of the code that gets deployed to production results in a degradation of experience for your users.

Code coverage measures the portion of code covered by tests. This metric calculates the average of project averages for each time period. Higher coverage generally means more confidence in stability and reliability during changes or releases.

Cognitive code complexity measures the mental effort required to read and understand code. This metric calculates the average of project averages for each time period. Lower cognitive complexity generally indicates code that is easier to maintain, review, and safely modify over time.

Track your teams' daily, weekly, and monthly commit counts. Engineering leads prefer frequent commits as smaller chunks reduce complexity in code.

A great metric to spot code merged directly without review, often indicating a compliance issue for many businesses.

Understanding what types of work are being completed and the frequency will enable you to get a good understanding of your organizations capacity.

Knowing the rate at which work gets created will give you an idea of how much work you'll need to burn through to keep your backlogs at healthy levels.

Tracking points movement through your process helps monitor progress in real time, quickly identifying bottlenecks, delays, and areas needing improvement.

Tracking ticket movement through your process helps monitor progress in real time, quickly identifying bottlenecks, delays, and areas needing improvement.

Knowing how long it takes to deliver from when a team commits to working on something is key to understanding delivery efficiency.

Knowing your code's production deployment time reveals improvement opportunities. Lengthy deployments delay teams and affect end users' experiences.

A key measure in the DORA framework for assessing DevOps maturity, knowing how often you deploy is a good indicator of how often value is delivered to your users.

A valuable metric reveals the link between file changes and build failures, pinpointing areas needing refactoring and areas impacting development efficiency with failed builds.

Augmenting metrics with data from other systems enhances insights. Tracking custom data like eNPS and test case coverage illustrates impacts effectively.

Knowing how long your delivery process takes is a key step in understanding how to deliver value to your customers sooner and gain that competitive advantage.

Assess where you sit in the DORA framework. Lead Time for change measures the time from a pull/merge request being opened until it is either merged or deployed.

Understanding if teams or individuals are taking on too much work helps you understand if the balance of focus is right.

Slow builds will slow down your development process. Learn which builds might be candidates for optimization.

When you have an interruption to your production services how long it takes to get back up and running and learning what takes the time is key for any high performing tech business.

Regularly deploying to production is crucial for effective software delivery. Tracking deployment frequency encourages the right organizational behaviors.

Discovering quality issues is essential for improvement. Whether unclear ACs or rushed quality gates are the problem, this metric helps identify and address them.

See how knowledge is spread across your engineering team(s), via the relationship of who is participating in whose pull requests

Frequent, small pull/merge requests are crucial for high-performing teams, allowing early feedback, reducing merge conflicts, and minimizing time spent on large reviews.

A visible link between pull/merge requests and delivered work is crucial for compliance and ensures accurate data visibility across various metrics.

Quality Scans Count tracks the frequency of quality scans run across your projects, helping you monitor how consistently your codebase is being analysed for issues.

Highlights how much of recently developed work may have had quality issues that the team need to address.

Software Quality Issues tracks the total or average number of quality issues (such as bugs, vulnerabilities, and code smells) detected by SonarQube across your projects.

Adhering to workflows is key to software delivery. If many tickets race through your process, it may indicate your team isn't using the workflow as intended.

Understanding if workflows are adhered to in software delivery is crucial. A high percentage of work bypassing your process may suggest misuse.

Ensuring teams deliver on their commitments is key to Scrum success. This metric shows completed work vs. commitments, highlighting areas for improvement.

Predictability is key to software delivery. This metric gives you the insights needed to identify improvement areas within your sprint team.

Making sure that teams are agreeing to deliver what they initially commit to is fundamental to good agile practices.

Making sure that teams deliver what they add to a sprint emphasizes focusing only on achievable work, this is fundamental to good agile practices.

Scope outlines the features, user stories, or tasks the team commits to in a sprint or Epic. Understanding this aligns everyone with goals and assesses the impact of changes.

This highlights individual and team delivery efficiency, showing how much work is completed per developer while factoring in how long it takes to complete tasks.

Failing builds will slow down your development process so making sure that these are infrequent is key for driving DevOps excellence in your teams.

Deploying frequently is a key DORA indicator for assessing your DevOps maturity so understanding and monitoring time since the last deployment is vital.

This metric offers flexibility by allowing teams to gauge their responsiveness to specific events within your organization and understand how quickly they are addressing them.

Build failures are part and parcel of software delivery but make sure you are recovering as quickly as possible.

Understanding which of your CircleCI workflows is costing too much to run can highlight candidates for optimization.

Understanding what types of work are being created and the size of backlogs will enable you to plan where you need to focus efforts.

Tracks variation in completed work across regular periods to understand delivery predictability. Low volatility enables accurate planning, increasing stakeholder confidence.

Helps highlight how complex some of the recently completed work was from an engineering perspective, this is vital for teams to understand.

Scope outlines the features, user stories, or tasks the team commits to in a sprint or Epic. Understanding this aligns everyone with goals and assesses the impact of changes.

Understanding parts of the process where work is queued up or waiting for something helps you diagnose what's causing bottlenecks.