Measuring SPACE framework metrics in GitLab

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Overview

The SPACE framework presents five categories to measuring developer productivity:

S – Satisfaction & Well Being
P – Performance
A – Activity
C – Collaboration & Communication
E – Efficiency & Flow

Proposal

1. Adding SPACE framework metrics into to value-stream mapping.
2. Add SPACE Metrics report to Insights.

SPACE <> Gitlab metrics mapping (WIP):

• Satisfaction
  • number of code reviews per developer (?)
• Performance
  • Deployment Frequency
  • Time to restore service
  • Median time to merge
  • Code-review velocity - both an individual- and a team-level metric
• Activity
  • Commits per Day
  • Merge request throughput
  • Number of issues closed
  • How many reviews have been completed in a given time frame (?)
  • number of commits, coding time (total time spent or times of day), and number of code reviews completed.
• Communication and collaboration
  • Contributor count
  • Code reviews
  • MR Approvers & Commenters
• Efficiency and flow
  • Cycle Time
  • Lead Time
  • MR Response Time
  • Code Review Cycle Time
  • Cycle Time by Stage
  • Work Patterns (?)

How DORA and SPACE can be used together?

https://www.youtube.com/watch?v=Hydf67rDUrY

Open questions

1. Clarify SPACE & DORA in the context of value-stream

Validation

Competition

• faros-ai: View well known engineering metrics such as DORA and SPACE --> https://github.com/faros-ai/faros-community-edition#-features