DevOps Metrics: DORA Four Keys, Flow & Reliability

What you'll build

What you will be able to do

Each lab ends with a concrete result that you build yourself and the checker confirms, cell by cell.

• Turn six weeks of Harbor Lane's production deployment log into deploys per week, per service, and the share of working days on which the team shipped.
• Calculate the commit-to-production lead time of 16 Checkout changes in hours and summarise it the way DORA does: with the median, a high percentile and the share within a target.
• Count Harbor Lane's March deploys and failures per service, calculate the change failure rate the right way (weighted, not averaged) and add DORA's newer rework rate.
• Turn twelve Harbor Lane incidents into minutes to restore, compare the median with the mean, isolate the incidents caused by deployments and see how much one outage dominates.
• Classify five Harbor Lane teams into Elite, High, Medium or Low on each DORA key with approximate-match lookups, and give each team an overall tier: its weakest key.
• Measure the Checkout team's flow over four weeks in March: cycle time per item, work in progress on eight snapshot days, flow efficiency, and a Little's law cross-check.
• Turn the Checkout API's 99.9% availability SLO into an error budget in minutes for a 12-week window, calculate the weekly burn rate, track the budget left and chart it.
• Build the Checkout team's half-year DORA dashboard: deploys per week and change failure rate per month, the quarter-on-quarter change, and a combo chart that shows speed and stability together.