Skip to main content

DevEx

Developer experience & blockers

Scrum Master Guide: Developer Experience & Blockers

The DevEx Index is a composite score derived from two sources: developer surveys (measuring perceived friction, tool satisfaction, and psychological safety) and DORA / SPACE metrics (deployment frequency, lead time, change failure rate, and mean time to resolution). Track your team's score over time and investigate drops in any quarter. Use the trend โ€” not a fixed threshold โ€” to decide when a focused retro is warranted.

Unlinked PRs are pull requests merged during the period that have no associated Jira ticket or work item. They represent invisible work โ€” effort that doesn't appear in planning or retrospectives. Use the unlinked_pull_requests endpoint to identify which teams have the highest ratio and run a targeted linking hygiene session.

DevEx Index by Team

Healthy
Frontend81
Platform78
Data72
Mobile65

Unlinked PRs

Action needed
23pull requests merged without a linked ticket
Platform9
Mobile7
Data4
Frontend3

DORA Metrics Reference

Deployment Frequency

Track how often the team pushes deployments. See the impact of process and tooling changes to ensure continuous improvement.

Lead Time for Changes

Understand the duration of your full value delivery cycle, from the moment a change is selected for development to its deployment.

Mean Time to Resolution

Measure the time from the start of an incident to its resolution, and minimize system downtime.

Change Failure Rate

Monitor the frequency of incidents or deployment failures to guarantee uninterrupted delivery of value to your customers.

API Explorer

MockMock

Scrum Master Playbook: DevEx & Unlinked Work

Retrospective: DevEx deep dive

Use devex_insights_by_team at the end of each quarter to present survey scores alongside DORA indicators. Teams showing a declining DevEx trend should identify the top friction sources โ€” tooling, review wait time, or unclear requirements โ€” and commit to one improvement per sprint.

Linking hygiene sprint ritual

Pull unlinked_pull_requests weekly (narrow window: last 7 days) and share the list in your team Slack channel. Assign a rotating "link captain" who retrospectively links or flags PRs before the sprint closes. This keeps your allocation data accurate and eliminates invisible work.

DORA baseline & goal-setting

At the start of each quarter, record your team's four DORA metrics using team_metrics. Set specific, measurable targets based on your team's baseline and track weekly progress in your sprint review. Pair DORA improvements with DevEx survey results to confirm that tooling changes are actually felt by engineers.

Customer-reported DevEx outcomes: Kaleris achieved 21% more productive and 19% more efficient engineering teams (jellyfish.co/platform/devex/). Platform rated 4.5/5 on G2 and 4.8/5 on Gartner.