What is Deployment Frequency?

Deployment frequency is how often code is shipped to production and is a key DORA measure of delivery throughput. Frequent, small deployments reduce risk and accelerate the feedback loop between building and learning. Counting non-production deploys inflates it and obscures real delivery cadence. For context, elite teams deploy on demand, often multiple times per day; high performers deploy between daily and weekly, per DORA research. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Deployment Frequency alongside Lead Time for Changes and Change Failure Rate; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Define every included record and value consistently, and reconcile the total to its source system before comparing periods. Use stable production boundaries and timestamp definitions, and distinguish planned work from incidents, rollbacks and failed deployments. Measure at service or team level and keep the start event, end event and production boundary stable; portfolio averages can hide a fragile component. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Treat the metric as a prompt for system improvement: reduce batch size, automate safe delivery, strengthen observability, rehearse recovery and use blameless reviews to eliminate recurring failure modes. Common pitfalls: counting non-production deploys. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.