In short
- Definition: The ease, speed and safety with which a new version of a system can be released into an environment.
- Goal: Deliver changes to users frequently and reliably, with minimal disruption.
- Example S.M.A.R.T. requirement: Deployment in under 30 minutes with no downtime, and a change failure rate below 5%.
1. Definition
As a non-functional requirement, deployment describes how easily, quickly and safely a new version of a system can be released into an environment, up to production [1], [2].
If deploying is painful, teams deploy rarely, and every release becomes risky. Make it boring.Key takeaway
It covers automation (a repeatable pipeline instead of manual steps), safety (tests, approvals, gradual rollout, rollback) and impact on users (zero or minimal downtime).
The DORA research program measures software delivery with a small set of metrics, including deployment frequency, lead time for changes, change failure rate and time to restore after a failed deployment [3], [4].
2. Goal
The goal is to deliver changes to users frequently and reliably, with minimal disruption, so that fixes and improvements reach them fast.
Manual, infrequent deployments bundle many changes together, which makes failures more likely and harder to diagnose.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Deployment frequency | Deployments per week | On demand, at least weekly | Pipeline history |
| Lead time for changes | Hours from commit to production | < 24 h | Pipeline timestamps |
| Change failure rate | % of deployments causing an incident | < 5% | Incident records linked to deployments |
| Deployment downtime | Minutes | 0 (zero-downtime deployment) | Monitoring during releases |
| Rollback time | Minutes | < 15 min | Rollback drills |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Web application: “Every release shall be deployed through the automated pipeline in under 30 minutes, with no user-visible downtime, and a rollback shall be possible within 15 minutes.”
- Quality: “The change failure rate shall stay below 5% over every quarter.”
- Regulated system: “Each production deployment shall be traceable to an approved change and a tested build, with the evidence kept for 3 years.”
5. Questions to Ask Stakeholders
- How often does the business want to release changes?
- Is downtime acceptable during a release, and when?
- Which approvals are required before production?
- How will a bad release be detected and rolled back?
- Which environments must the pipeline cover?
- Who is allowed to trigger a deployment?
6. Common Pitfalls
- Manual steps in the release. They cause errors and slow everything down. Automate end to end.
- No rollback plan. Every deployment needs a tested way back, including for database changes.
- Big-bang releases. Small, frequent changes are safer than large, rare ones.
7. Related NFRs
- Configuration Management — versioned configuration makes deployments repeatable.
- Testability — automated tests are the safety net of frequent deployment.
- Availability — zero-downtime deployment protects uptime.
- Operability — operators need clear runbooks and visibility during releases.
8. FAQ
A set of measures of software delivery performance, such as deployment frequency, lead time for changes, change failure rate and recovery time.
A release technique, such as blue-green or rolling deployment, where users keep using the service while the new version is installed.
Yes, if approvals and evidence are built into the automated pipeline.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| DORA | DevOps Research and Assessment | Research program that defines four key metrics for software delivery performance. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Database | Organized store of data that software can query and update. | [8] |
| Incident | Unplanned interruption or degradation of a service. | [9] |
| Pipeline (CI/CD) | Automated sequence of steps that builds, tests and deploys each code change. | [10] |
| Production environment | The live system that real users use, as opposed to test environments. | [11] |
| Rollback | Returning to the previous version after a change causes problems. | [12] |
| Runbook | Step-by-step procedure for routine operations or for handling a known problem. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
| Uptime | Time during which a system is working and available. | [15] |
10. Sources and Further Reading
- [1] “Continuous deployment.” Wikipedia. https://en.wikipedia.org/wiki/Continuous_deployment (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “DORA’s software delivery performance metrics.” DORA. https://dora.dev/guides/dora-metrics-four-keys/ (accessed Nov. 18, 2026).
- [4] “Continuous delivery.” DORA. https://dora.dev/capabilities/continuous-delivery/ (accessed Nov. 18, 2026).
- [5] “DevOps.” Wikipedia. https://en.wikipedia.org/wiki/DevOps (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [9] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [10] “CI/CD.” Wikipedia. https://en.wikipedia.org/wiki/CI/CD (accessed Nov. 19, 2026).
- [11] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [12] “Rollback (data management).” Wikipedia. https://en.wikipedia.org/wiki/Rollback_(data_management) (accessed Nov. 19, 2026).
- [13] “Runbook.” Wikipedia. https://en.wikipedia.org/wiki/Runbook (accessed Nov. 19, 2026).
- [14] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [15] “Uptime.” Wikipedia. https://en.wikipedia.org/wiki/Uptime (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @spacex; inline photo by @arw_, both on Unsplash.




