SPACE metrics
Which SPACE metrics Prodgator shows, where they come from, and which ones are hidden when fewer than 5 people contributed.
The SPACE metrics page reports developer productivity across five dimensions: satisfaction and well-being, performance, activity, communication and collaboration, and efficiency and flow. It needs the Business plan, and the Editor role or the View SPACE metrics permission. Every number is for the whole organization or one repository. There are no per-person scores or rankings.
The 5-contributor minimum
Some metrics are built from people's own pull requests and reviews. To avoid singling anyone out, those metrics are hidden when fewer than 5 distinct people (bots excluded) authored or reviewed a pull request in the selected period and view. The page shows a note in place of each hidden value. Prodgator never shows the number of contributors.
Metrics counted from pipelines and deployments are totals, not per-person data, so they are always shown, whatever the team size.
| Metric | Source | Follows the 5-contributor minimum |
|---|---|---|
| Change failure rate | Deployments to protected environments | No |
| Default-branch pipeline success | Pipeline runs on / | No |
| CI duration on main (median) | Pipeline runs on / | No |
| Protected deployments | Deployments to protected environments | No |
| Pipeline runs | Pipeline runs | No |
| Pull requests merged | Pull request and merge request events | Yes |
| Reviews submitted | Pull request and merge request events | Yes |
| Review coverage | Pull request and merge request events | Yes |
| Time to first review (median) | Pull request and merge request events | Yes |
| Reviewers per author | Pull request and merge request events | Yes |
| PR cycle time (median and 75th percentile) | Pull request and merge request events | Yes |
| Pulse survey results | Monthly survey answers | Separate rule: 5 responses |
Protected environments
Change failure rate and protected deployments count deployments to protected environments only: deployment environments that a gate covers and does not exclude. An environment's name does not matter. Past days are counted by your gates as they are today. Until a gate protects a deployment environment, both metrics are empty and the page links to Gates.
When the pipeline and deployment metrics are shown and the pull request metrics are hidden, the view is partial: you see the first group and a note on the rest. A longer period or all repositories can include enough people.
Pulse survey
The optional monthly survey covers satisfaction, workload, code review and focus time. Results appear only for completed months with at least 5 responses, for the whole organization and never per repository. This rule is separate from the contributor minimum.
What is not measured
- Any per-person metric, score or ranking.
- Lines of code and commit counts.
- Hours worked, online status, keystrokes or calendar data.
- Meeting load, interruptions and on-call burden.
- Product and customer outcomes.
- Pull requests on Bitbucket. GitHub pull requests, GitLab merge requests and Azure Repos pull requests are collected.
- Pull requests from before collection started. There is no backfill.
When numbers appear
A daily rollup at 02:15 UTC counts each day on the following day. Pull request events are kept for 35 days.