iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Measure DevOps performance with five DORA metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate. Track them for one application or service, define the same start and end events every time, establish a baseline, and study trends rather than turning any number into a quota.
The useful result is not a leaderboard. Taken together, the metrics show how quickly a team delivers changes and how often those changes create instability or unplanned work. That combination gives a practical way to decide what to improve next.
What DORA metrics measure
DORA’s current software delivery performance model has five measures divided into throughput and instability. The first three describe delivery flow; the final two describe how often production changes create urgent or unplanned work. Read the complete set together because a single number can hide an important trade-off.
| Metric | What to measure | DORA grouping |
|---|---|---|
| Change lead time | Elapsed time from a change being committed to version control until it is deployed in production. | Throughput |
| Deployment frequency | How many production deployments occur in a defined period, or the elapsed time between deployments. | Throughput |
| Failed deployment recovery time | Time required to recover when a deployment fails and needs immediate intervention. The current definition focuses on service impairment caused by a production change. | Throughput |
| Change fail rate | The proportion of deployments that require immediate intervention after release, such as a rollback or hotfix. | Instability |
| Deployment rework rate | The proportion of deployments that were unplanned because of a production incident. | Instability |
DORA’s own guidance captures the principle in one sentence: “Context matters. Apply the metrics in the context of the application or service your team is delivering.” A mobile application, a mainframe system and an internal API have different release paths, risk profiles and user expectations, so their raw values are not automatically comparable.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Change lead time
Change lead time is the elapsed duration between two explicit events:
- Start: the change is committed to version control.
- End: that change is deployed in production.
Use the same event for every observation. If one team starts the clock at pull-request creation while another starts it at merge, the resulting figures describe different processes. Likewise, “production” must mean the same environment and release state throughout the series. If your service releases to users through a staged rollout, record which event represents the production deployment: for example, the first production exposure or completion of the rollout. Document the choice instead of changing it for individual releases.
For a single change, calculate:
change lead time = production deployment timestamp − commit timestamp
Recommended Free Tools
For a reporting period, use a distribution or a clearly stated summary such as the median. Averages can be pulled upward by a small number of changes that wait in a long approval queue. Whatever summary you choose, keep it consistent so that movement over time is meaningful.
Deployment frequency
Deployment frequency counts production deployments in a defined period. You can also express it as the time between deployments. DORA’s questionnaire asks, “How often does your organization deploy code to production or release it to end users?” The question deliberately allows the service’s own release mechanism to define a deployment.
Write down what counts before counting:
- Whether a deployment to production counts when it begins, when it completes, or when users can receive the change.
- Whether automated canary, blue-green and phased deployments are one deployment or several events.
- Whether infrastructure-only changes, configuration changes and emergency fixes are included.
- Whether repeated attempts of one release are recorded as separate deployments.
A count without these rules is not reproducible. A service that deploys ten times a day and a service that releases one bundled update each month may both be operating appropriately; frequency is a signal about flow, not a universal quality score.
Failed deployment recovery time
Failed deployment recovery time measures how long it takes to recover from a deployment that fails and requires immediate intervention. DORA’s metric history narrowed this measure to service impairment caused by a production change. It is therefore not the duration of every incident, outage or support event.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDefine the two timestamps in your event dictionary. A practical implementation might start when the team confirms that a production change has impaired the service and end when the service is restored to the agreed operating state. If the team rolls back, the recovery end can be the point at which the rollback restores service; if it applies a hotfix, use the point at which the hotfix is successfully running. Do not silently include a network outage, a capacity event or another incident unrelated to a deployment.
Keep the trigger and recovery criteria stable. Changing the definition from “user-visible impairment” to “first alert” halfway through a quarter will create an apparent improvement or decline that reflects measurement, not delivery performance.
Change fail rate
Change fail rate is the ratio of deployments that require immediate intervention after deployment. Immediate intervention includes actions such as a rollback or a hotfix. The denominator is the set of deployments covered by your service definition during the same period.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Calculate it as:
change fail rate = deployments requiring immediate intervention ÷ total deployments × 100
Record one clear failure decision for each deployment. If a deployment causes several alerts but is fixed without a rollback or hotfix, your written policy should state whether that event meets the “immediate intervention” threshold. The objective is consistency, not a definition that makes the rate look favorable.
Deployment rework rate
Deployment rework rate captures unplanned deployments made because of a production incident. It answers a different question from change fail rate: a deployment can be a successful planned release yet still be followed by a separate, unplanned bug-fix deployment.
Calculate it as:
deployment rework rate = unplanned incident-driven deployments ÷ total deployments × 100
Mark the reason for each deployment when it is created or completed. A scheduled maintenance release, a planned security update and a normal feature release are not rework merely because they were important. An emergency patch created to address a production incident is rework under this definition.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Set a measurement contract before collecting numbers
Most DORA measurement disputes are event-definition disputes. Create a short measurement contract that the development, operations and release participants can all read and apply.
Choose one application or service
Start with one primary application or service. DORA says the measures are best suited to one application or service at a time because context differs across applications and users. A portfolio-wide number can hide the fact that one critical service is improving while another is deteriorating.
Choose a boundary that the team can own from committed change through production operation. If several services are released together, either measure the service with its own deployment events or explicitly document the shared release boundary. Do not combine incompatible boundaries simply to obtain a larger sample.
Write the event dictionary
Define the exact events and fields you will store:
- Commit identifier and commit timestamp.
- Deployment identifier, target service, environment and completion timestamp.
- Whether the deployment was planned, emergency or incident-driven.
- Whether immediate intervention occurred, what action was taken and when it ended.
- Whether a production impairment was caused by the change, and the timestamps for confirmation and recovery.
Include time-zone handling, clock synchronization and the treatment of retries. A deployment record should not be counted twice because a pipeline was re-run, and a commit should not receive a new start time merely because it moved between branches.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Set the observation window
Use a fixed reporting window, such as a calendar month or a rolling six-month period, and keep it when comparing trends. DORA’s research questions ask about deployment frequency, recovery time, lead time and percentage measures, including unplanned bug-fix deployments in the prior six months. A local team can choose a shorter window for rapid feedback, but it should label that choice and avoid comparing it directly with a six-month response.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Decide how to handle missing and exceptional events
Specify what happens when a timestamp is missing, a deployment is canceled, or a staged rollout never reaches its intended audience. Exclude an observation only under a documented rule and report the number excluded. Quietly dropping difficult cases makes the trend less trustworthy.
A practical six-step workflow
1. Select the service and accountable group
Name the application or service, its production environments and the cross-functional group responsible for prioritizing, building, delivering and operating it. Shared ownership matters: assigning the dashboard only to developers or only to operations can turn a system problem into finger-pointing.
2. Agree on boundaries with real examples
Take several recent releases and label their commit, deployment, impairment, recovery and incident-fix events using the proposed rules. Resolve disagreements before automating calculations. Examples expose ambiguities such as whether a canary is a deployment and whether a rollback is a failed deployment or a separate release.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Assemble the minimum data set
Begin with the systems you already use: version control for commit timestamps, the delivery pipeline or deployment platform for production events, and incident records for impairment, recovery and emergency fixes. Link records with a deployment or change identifier where possible. DORA notes that the necessary data often exists across multiple systems; perfect integration is not a prerequisite for a useful first baseline.
4. Establish a baseline
Calculate each metric for the first consistent window and preserve the underlying records. The baseline is a description of the current delivery system, not a grade. Annotate major events such as a migration, a new approval policy or a temporary freeze so that later movement has context.
5. Inspect movement and find a bottleneck
Review the metrics as a set. A long lead time with low deployment frequency may point to batching or a queue. A high frequency paired with rising change fail rate may indicate inadequate testing, risky release practices or weak observability. High deployment rework can reveal that planned work is repeatedly displaced by incidents. Use the numbers to choose one bottleneck to investigate rather than launching several unrelated initiatives.
6. Make a small change, then re-measure
Choose an improvement that the service team can observe, such as reducing an approval queue, adding a deployment check or narrowing a release batch. DORA’s guide suggests that smaller changes can be easier to reason about and recover from. Recalculate the same measures after the next comparable window and discuss the result in a retrospective or team conversation. DORA also points to its Quick Check as a way to prompt discussion; it is not a replacement for a locally defined event model.
Worked calculation with an illustrative release set
The following numbers are an example of the arithmetic, not a benchmark or expected performance level. Suppose one service records 20 production deployments in a month. Four deployments require a rollback or hotfix, and two additional unplanned deployments address production incidents.
| Measure | Example calculation | Result |
|---|---|---|
| Deployment frequency | 20 deployments during the month | 20 per month |
| Change fail rate | 4 ÷ 20 × 100 | 20% |
| Deployment rework rate | 2 ÷ 20 × 100 | 10% |
For lead time, retain each deployment’s commit-to-production duration rather than reducing the service to one arbitrary number. For failed deployment recovery time, retain the elapsed duration for each qualifying change-caused impairment and state whether you report a median, mean or another summary. The event list lets the team see whether one extreme recovery dominates the period.
How to interpret DORA metrics without misusing them
Read throughput and instability together
The objective is not to maximize deployment frequency while ignoring failed changes and rework. DORA reports that speed and stability are correlated for most teams, so a team should look for delivery practices that improve flow without creating avoidable instability. A frequency increase accompanied by a sustained rise in change fail rate deserves investigation, not automatic praise.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Compare the service with its own history
Trend the same service over time and annotate changes in architecture, release policy, team composition and user exposure. Comparing very different applications can mislead: the operational context of a mobile app is not the same as that of a mainframe system. If a comparison is necessary, group services with similar release and operating contexts and explain the grouping.
Do not create universal targets or rankings
DORA warns that targets can encourage gaming, a single metric can conceal complexity, and competition between teams is not the purpose. A deployment-frequency quota may encourage teams to split releases artificially. A fail-rate target may encourage under-reporting of interventions. Use a metric to ask what is happening in the system and what evidence would support an improvement, not to decide which team is “best.”
Keep ownership shared
Delivery performance crosses development, operations, testing, security, product and release work. Review the measurements with the people who can change each part of the path. If only one function owns the metric, other contributors may treat it as someone else’s scorecard, increasing friction rather than learning.
Data sources, automation and tooling choices
You can begin with a spreadsheet or a small query that joins commit, deployment and incident records. The important properties are a stable event dictionary, an auditable source record and a repeatable calculation. Automate only after the team agrees what each event means.
DORA cautions against spending more on measurement integrations than the decision warrants. Data is commonly distributed across several systems, and building highly precise integrations may not justify the initial investment. Start with a conversation, the Quick Check or tools that already provide pre-built integrations, then invest further when a specific decision requires better coverage or freshness. Any software product should be evaluated for whether it preserves your service boundaries, exposes the underlying events and allows you to correct classification errors.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Model history and the current five-metric version
The familiar “four keys” were deployment frequency, lead time for changes, mean time to recover and change fail rate. DORA’s history explains that the recovery measure was renamed and redefined as failed deployment recovery time so that it focuses on service impairment caused by a production change rather than every kind of outage.
In 2024, DORA added deployment rework rate, creating the five-metric model in the current guide. The current metrics guide and DORA’s history page, last updated January 2, 2026, describe five measures. An indexed 2026 Quick Check page presents four questions, while an indexed 2025 version presents five, including deployment rework rate. The reviewed pages do not explain why the 2026 tool omits that question. That tool presentation does not change the definitions in the five-metric guide; use the guide’s five measures when designing a complete local measurement model.
Common pitfalls and their fixes
Mixing event boundaries
Symptom: Lead time starts at pull-request creation for some releases and commit time for others.
Fix: Publish one start and end event for each metric, then recalculate historical data only when the same events can be identified reliably.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCounting every incident as deployment recovery
Symptom: A database outage unrelated to a release inflates failed deployment recovery time.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Fix: Require evidence that a production change caused the service impairment before starting a recovery observation.
Combining services into an opaque average
Symptom: A high-volume, low-risk service masks deterioration in a critical service.
Fix: Measure one application or service first and preserve service-level context in every report.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Optimizing one number
Symptom: Teams split releases to raise frequency or avoid recording failed changes.
Fix: Review throughput and instability together, retain the underlying deployment records and use the numbers for improvement conversations rather than compensation or ranking.
Automating before agreeing on definitions
Symptom: A dashboard produces precise values that different teams interpret differently.
Fix: Test the event dictionary on recent releases first, document exceptions and automate the agreed rules.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What a useful DORA review looks like
A practical review can fit on one service page:
- The five metric definitions and event boundaries.
- The observation window and data coverage.
- A trend for each measure, with notable delivery or operational changes annotated.
- The most important relationship between throughput and instability.
- One bottleneck hypothesis and one small improvement to test.
- The owner shared by the people who can change the delivery system.
This format keeps DORA metrics connected to decisions. The numbers describe how the service is delivered; the team’s discussion explains why they moved and what to try next.
Frequently Asked Questions
Can DORA metrics be used to compare two teams?
Only with strong caution. DORA advises interpreting a service in its own application and operating context; comparing unlike systems can produce a misleading result. Use cross-team data primarily to identify patterns and questions, not to rank people.
Do I need a commercial dashboard to start measuring?
No. Commit, deployment and incident records in existing systems can provide a baseline. DORA recommends starting with available data and investing in integrations only when a specific decision justifies the cost.
What should count as a production deployment for a staged rollout?
Choose one consistent boundary, such as first production exposure or completion of the rollout, and document it for the service. Apply that rule to every comparable deployment, including canaries and blue-green releases.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is failed deployment recovery time the same as overall incident duration?
No. The current DORA definition focuses on service impairment caused by a production change that requires immediate intervention. Unrelated outages and incidents should not be included.
Why might a newer Quick Check show four questions when the model has five metrics?
The indexed 2026 Quick Check presents four questions, while the indexed 2025 version presents five. The reviewed pages do not explain the difference, and it does not alter the five definitions in DORA’s current metrics guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
