Understand the SPACE framework for developer productivity and how Periscope implements it through PR analytics.
SPACE is a developer productivity framework introduced by researchers at Microsoft, GitHub, and the University of Victoria. It argues that productivity is multidimensional and cannot be captured by a single metric. Instead, it proposes five dimensions:
SPACE’s Satisfaction dimension requires surveys and qualitative data, which Periscope does not collect. If you use developer experience surveys, the quantitative SPACE metrics in Periscope provide useful context for interpreting survey results.
Tracks the number of PRs merged per week. Throughput gives you a high-level view of your team’s shipping cadence. Consistent throughput suggests healthy flow; drops may indicate blockers, context switching, or team capacity issues.Learn more about throughput
Measures the time from when a pull request is opened to when it is merged. Long cycle times indicate bottlenecks in code review, CI pipelines, or team coordination. Periscope provides p50, p75, and p95 percentiles so you can distinguish between typical and worst-case experiences.Learn more about cycle time
Plots PR size against cycle time to reveal whether larger changes are creating review bottlenecks. This helps teams set data-informed guidelines for maximum PR size.Learn more about size vs time
DORA and SPACE are complementary. DORA focuses on the output of the delivery pipeline (how fast and reliably you ship), while SPACE focuses on the inputs and experience of the development process.A practical approach:
Use DORA metrics to track your delivery pipeline health — are you shipping frequently, quickly, and reliably?
Use SPACE metrics to understand why — are cycle times long because of large PRs? Is throughput dropping?
