Our Metrics

Pulzen provides a comprehensive suite of metrics and actionable insights to help development teams and organizations continuously improve their productivity, quality, and collaboration. Our platform combines industry-leading frameworks such as SPACE, DORA, GitHub Copilot and DevExp with a rich library of ready-to-use prompts, enabling teams to monitor, analyze, and optimize every aspect of their software delivery lifecycle.

We focus on quantitative, privacy-respecting data—never storing or analyzing sensitive code or business logic. Pulzen’s metrics cover everything from code review velocity, deployment frequency, and cycle time, to team communication, developer well-being, and tool adoption. With our AI-powered prompt library, users can quickly access tailored visualizations and reports, empowering data-driven decision-making at every level.

Whether you want to track high-level KPIs, drill down into team or individual performance, or explore trends in collaboration and automation, Pulzen gives you the tools and clarity to drive continuous improvement and deliver better software, faster.

SPACE Framework Metrics

Performance

• Code Review Velocity: Measures the speed at which code reviews are completed. This metric helps teams understand how quickly code changes are being reviewed and integrated, supporting faster delivery and reducing bottlenecks in the development process.
• Code Review: Tracks the number and frequency of code reviews performed. Monitoring code review activity helps ensure code quality, encourages collaboration, and promotes knowledge sharing among team members.
• Approval rate: Measures the percentage of code reviews that are approved. This metric provides insight into the quality and readiness of code changes, as well as the effectiveness of the review process.
• Time to Approval Code Review: Tracks the average time it takes for a code review to be approved. This helps teams identify delays in the review process and optimize workflows for faster integration of changes.

Activity

• Commits: Counts the number of commits made to the codebase by users and teams.
• Lines of Code: Lines of code of the commits by user.
• Deploy Frequency (DORA): Measures how often code changes are deployed to production.

Communication & Collaboration

• PR Merge Times: Tracks the time taken to merge pull requests.

Efficiency & Flow

• Code Review Timing: Measures the duration of the code review process.

DORA and DevExp

• Merge Frequency: Measures how often code changes are merged into the main branch. This metric helps teams understand the pace of integration and collaboration.
• Deployment Frequency: Measures how often code changes are deployed to production. High deployment frequency is a sign of continuous delivery and agile practices.
• Coding Time: Tracks the total time developers spend actively writing code. It provides insight into development effort and productivity.
• Pickup Time: Measures the time it takes for a code change or task to be picked up after it is created. This helps identify delays in the workflow and optimize task assignment.
• Review Time: Tracks the duration between when a code change is submitted for review and when the review is completed. It helps teams monitor review efficiency and identify bottlenecks.
• Close Time: Measures the time taken to close a pull request from its creation. This metric provides visibility into workflow efficiency and cycle completion.
• Deploy Time: Measures the time it takes to deploy code changes to production after they are merged. It helps teams optimize release processes and reduce time-to-market.
• Cycle Time: Represents the total time from the start of work on a change until it is deployed to production. This end-to-end metric is key for understanding delivery speed and identifying improvement opportunities.

GitHub Copilot Metrics

• Seat usage: This metric measures the number of seats or licenses being used compared to the total available. It is useful for evaluating resource utilization efficiency.
• IDE per user/team: This metric measures the use of Integrated Development Environments (IDEs) by user or team. It is useful for understanding preferences and usage patterns of development tools.
• Language per user/team: This metric tracks the programming languages used by each user or team. It is useful for identifying which programming languages are being used the most.
• % Suggestion accepted: This metric measures the percentage of suggestions accepted by users compared to the total number of suggestions made by Copilot. It indicates the receptivity and efficiency of each suggestion delivered.
• % Lines accepted: This metric measures the percentage of lines of code that are accepted or integrated into the developer's code. It helps evaluate the quality and acceptance of the suggestions.
• % Suggestion by chat: This metric measures the percentage of suggestions made through GitHub Copilot Chat. It is useful for understanding the dynamics of Chat usage.
• Daily usage of GitHub Copilot: This metric provides a visual representation of the daily usage of GitHub Copilot. It helps identify peak usage times and patterns over a period of time.

Pulzen Metrics

This section includes advanced and specialized metrics that go beyond standard productivity and delivery indicators. Here you’ll find insights into anomalous activity (such as ghost or burnout developers), the quality and impact of contributions (commit score), and detailed breakdowns of commits, pull requests, and workflows. These metrics help teams detect risks, recognize valuable work, and gain a deeper understanding of their development process at multiple levels.

Ghost Developer

This metric measures drops in user activity by analyzing data from Version Control Systems (VCS) and collaboration platforms like Teams. It compares each user's historical and current activity to identify significant decreases, helping teams detect disengagement or potential offboarding early.

Burnout Developer

This metric identifies signs of overactivity by monitoring both VCS data and Teams activity. It takes into account excessive work, activity outside of regular hours, and weekend work, providing early warnings of possible developer burnout and supporting well-being initiatives.

Commit Score

This metric uses a custom formula to evaluate the value and impact of each commit. By analyzing factors such as the number of changes, additions, deletions, and commit frequency, Commit Score helps teams identify high-value contributions and understand the significance of code changes over time. This enables better recognition of impactful work and supports data-driven decision-making in code reviews and project planning.

Commit detail

This metric tracks activity over time by user, team, and repository, measuring the number of commits as well as code additions and deletions. It provides a detailed view of contribution patterns and codebase evolution across different dimensions.

Pull Request detail

This metric tracks the number of pull requests in open, closed, and merged states, segmented by user, team, and repository. It also measures the time to merge for each pull request, providing insights into review cycles, collaboration efficiency, and delivery speed across different dimensions.

Workflow detail

This metric tracks the number of workflows or pipelines executed, segmented by user, team, and repository. Each workflow is categorized by status—canceled, failed, or successful—and the duration of each workflow is also measured. All these metrics are analyzed from two perspectives: the creator of the pull request (the code author) and the reviewer/approver who triggers the workflow. This dual focus provides a comprehensive view of automation efficiency, collaboration, and delivery quality across your development process.

Pulzen Prompt Library

Some of our Pulzen Prompt Library is a curated collection of actionable metrics and insights that can be quickly accessed or requested through Pulzen's AI-powered platform. This library enables teams to monitor, analyze, and improve their software development process using ready-to-use prompts and visualizations tailored to real-world needs.

Collaborators and Performance

• Here, you can check your top 10 contributors using a prompt like: Create a chart with top 10 contributors based on commits
• ... or perhaps you like to identify the lowest-performing users with: Create a chart with lowest 10 contributors
• Wondering which developer made the most significant line of code changes in a single commit? Try this: Who has the most line of code changes by commit?
• Don't want to look at just one? You can explore this instead: Create a chart with the top 10 of users by lines of code changed in total
• Or take a look at the inverse with: Create a chart with the lowest 10 of users by lines of code changed in total

Pull Requests

• Curious about how many pull requests each team has? You can use this prompt: Give me the count of pull request per team
• Curious about pull request approval rates across teams? Here's an option: Do you know the average approval rate of a pull request per team?
• Want to track the other side of the story? Check this prompt for rejection rates: Do you know the average rejection rate of a pull request per team?

Commits Activity by Teams

• Interested in seeing commit activity across teams? Try this prompt: Show me a chart with the commits quantity by teams
• Curious about which teams are leading in commit activity? Check this out: Give me the top 3 teams with more commits count
• Want to see which teams are trailing in commit activity? Here's a prompt for that: Give me the lowest 3 teams commit count

Pull Request Approval Time

• Interested in knowing how long it takes for pull requests to get approved across teams? Use this prompt: Give me the average time per pull request per team to be approved

Workflows

• Do you want to know how many workflows have been executed per team? Try this prompt: Show me a chart with the number of workflows executed per team
• Do you want to know which workflows have the longest execution time? Check this out: Give me the total duration of workflows grouped by month and sorted by status
• ... or maybe you'd like to know which workflows have the shortest execution time: Give me the total duration of workflows grouped by month and sorted by status

GitHub Copilot

• Do you want to know how many suggestions GitHub Copilot has made per team? Try this prompt: Show me a chart with the number of GitHub Copilot suggestions sorted by month
• Do you want to know how much GitHub Copilot has been used in your company? Check this out: Give me the number of GitHub Copilot suggestions
• Do you want to know which users have used GitHub Copilot the most? Check this out: Which users use GitHub Copilot the most?
• Do you want to know which IDE is most used by GitHub Copilot users? You can use this prompt: Create a pie chart with the number of GitHub Copilot suggestions per IDE
• Do you want to know which programming language is most used by GitHub Copilot users? You can use this prompt: Create a pie chart with the number of GitHub Copilot suggestions per programming language
• Do you want to know chat usages, lines acceptance, and chat acceptance over time by month? You can use this prompt: Give me a line chart of usages total suggestions, total chat, total chat acceptance and total lines acceptance over time by month ordered

Cycle Time

• Do you want to know how long a work cycle takes to complete per team? Try this prompt: What is the average work cycle time per team?
• Do you want to know how long a work cycle takes to complete per user? Try this prompt: What is the average work cycle time per user?

Jira Activity

• Do you want to know how many Jira issues have been created per user? Try this prompt: Show me a chart with the number of Jira issues created per user

Ghost Developers

• How can I obtain a list of my ghost developers, ordered by the ghost score?: Give me a list of my ghost developers, ordered by the ghost score

Developer Burnout

• Do you want to know which developers have the highest burnout score? You can use this prompt: Give me a list of my developers with the highest burnout score

Microsoft Teams Activity

• Do you wanna know top ten developers with more meetings? You can use this prompt: Give me a list with the top 10 developers with more meetings
• Do you wanna know the average minutes of screen shared by the team members in Microsoft Teams? You can use this prompt: Give me a line chart with the average minutes of screen shared in Microsoft Teams of the top 10 developers
• Do you wanna know the average minutes of screen shared by the team members in Microsoft Teams? You can use this prompt: Give me a widget with the average minutes of screen shared in Microsoft Teams

Deploy Frequency

• Do you want to know the deploy frequency per month per team? You can use this prompt: Give me a line chart with the deploy frequency per month per team
• Do you want to know the deploy frequency per week? You can use this prompt: Give me a line chart with the deploy frequency per week
• Do you want to know the best user by deploy frequency? You can use this prompt: Give me a pie chart with the deploy frequency per user

Merge Frequency

• Do you want to know the merge frequency per month per team? You can use this prompt: Give me a line chart with the merge frequency per month per team
• Do you want to know the merge frequency per week for the last month? You can use this prompt: Give me a line chart with the merge frequency per week for the last month
• Do you want to know the merge frequency per user? You can use this prompt: Give me a pie chart with the merge frequency per user
• Do you want to know the total merge frequency? You can use this prompt: Give me a widget with the total merge frequency