Development Experience

Development Experience  

Info

DevEx metrics reflect the timescale you choose at the top of the page. These metrics provide visibility into what a developer’s day-to-day looks like once a pull request (PR) is issued and compares it to the previous time period (denoted in grey). These values use KPIs from the Metrics Dashboard and reflect the Metrics Calculation method you’ve selected in Company Settings.  

• Pickup wait time: The time elapsed between a pull request (PR) being issued and the first comment made by a reviewer. 
• Merge wait time: Measures the time it takes for a PR to be merged into the main branch after it has been approved.
• Deploy wait time: The time it takes for a PR to be deployed into production after it has been merged.

Tip

High values (or values trending up from the previously measured period) in any of these categories indicate process bottlenecks and an opportunity to improve DevEx and developer productivity. Here are the insights you can take away from each DevEx metric and how to improve them:

High Pickup Wait Time: Lots of idle time and associated context switching. Focus is split, and quality (along with delivery timelines) will likely suffer. Here’s what you can do: 

• Work to keep PRs small
• Set Team Goals against both pickup time and PR size
• Put another resource on the product to ensure things stay on track
• Use SEI+ Automation to automatically add estimated review time labels or review/approve safe changes automatically

High Merge Wait Time: With idle time and context switching comes loss of focus; the result is high Merge Wait Time. Mitigating this risk is a matter of tracking work effectively and keeping it top of mind. Developers can use real-time alerting in their communication and collaboration tools to keep the work moving. 

High Deploy Wait Time: Something is preventing developers from shipping their code to production. The most likely culprits are lack of visibility or process alignment. Developers can use real-time alerting in their communication and collaboration tools to keep the work moving. Additionally, high deploy wait times for either individual developers or the entire organization are good opportunities to review policies and adjust things like Acceptance testing design and CI/CD policies.