ScoreWeighted total SPACE score calculated from active dimension scores and metric weights.
-
-
Performance
Evaluates the outcomes and quality produced by development work. Merged changes, developer-caused defects, and bug-fix speed indicate whether valuable results are delivered reliably.
00
Table.mergedCountNumber of merge requests merged in the selected period. For a developer, this is MRs created by that developer and merged.
-
-
Table.bugCausedCountNumber of bug issues attributed to this project or developer in the selected period.
-
-
Table.bugFixLeadTimeHoursAverage hours from bug issue creation to completion for fixed bugs in the selected period.
-
-
Activity
Evaluates the volume and continuity of development work through commits, issues, bug handling, and code changes. Activity is a proxy for work performed, not an outcome or quality measure by itself.
00
Table.commitCountTotal commits in the selected period, filtered by project, branch, and developer when selected.
-
-
Table.issueCreatedCountNumber of issues created in the selected period.
-
-
Table.bugFoundCountNumber of bug issues found or reported in the selected period.
-
-
Table.bugFixedCountNumber of bug issues completed or fixed in the selected period.
-
-
Table.linesAddedTotal added lines from commits in the selected period.
-
-
Table.linesDeletedTotal deleted lines from commits in the selected period.
-
-
Table.linesTotalTotal changed lines from commits in the selected period. This is additions plus deletions.
-
-
Communication
Evaluates collaboration and knowledge sharing through review participation, comments on others' merge requests, and constructive discussion during development.
00
Review ParticipationReview participation count. For a developer, this counts other people's MRs where they left an effective review comment in the selected period. For a project, this counts non-author reviewer participation on project MRs.
-
-
Review Comments GivenNumber of effective review comments posted on other people's MRs in the selected period. Author replies on their own MRs are not included.
-
-
MR Discussion DensityDiscussion density: average number of non-author review comments received per created MR. This is shown as context and is not directly used for scoring, because higher is not always better.
-
-
Efficiency
Evaluates whether work flows smoothly with limited delays and interruptions. Merge lead time and review wait time show how efficiently changes reach completion.
00
Table.mergedLeadTimeHoursAverage hours from MR creation to merge for MRs merged in the selected period. This uses the same MR set as merge count.
-
-
Review Wait TimeAverage hours from MR creation to the first review comment.
-
-
Uninterrupted Focus TimeAverage uninterrupted focus time per workday. Higher values indicate more time available for sustained deep work.
-
-
Context Switch FrequencyAverage number of switches between tasks, projects, or meetings per workday. Lower values indicate less fragmented work.
-
-
Satisfaction
Evaluates developer satisfaction and well-being through job meaning, developer efficacy, sustainability, and confidence that improvements can happen.
00
Job Satisfaction & MeaningSub-score calculated from work value, meaningful work, team satisfaction, and recommendation intent.
-
-
Developer EfficacySub-score calculated from information access, development environment support, support flow, and confidence in outcomes.
-
-
SustainabilitySub-score calculated from sustainable workload, fatigue, detachment, and excessive pressure. Negative questions are reverse-scored.
-
-
Improvement PotentialSub-score calculated from psychological safety and expectation that improvement suggestions can lead to real change.