an Agile practice that defines the exit criteria under which user stories are considered to be done. (See also definition of ready .)
— DevOps for the Modern Enterprise, Mirco Hering
3 of our books and 1 talk define this term — and their definitions are worth reading side by side.
an Agile practice that defines the exit criteria under which user stories are considered to be done. (See also definition of ready .)
— DevOps for the Modern Enterprise, Mirco Hering
At the end of each development interval, we must have integrated, tested, working, and potentially shippable code, demonstrated in a production-like environment, created from trunk using a one-click process, and validated with automated tests.
— The DevOps Handbook, in “11 Enable and Practice Continuous Integration”, Gene Kim, Jez Humble, Patrick Debois, John Willis, and Nicole Forsgren
the Definition of Done is that everything runs in production according to service level agreement (SLA)
— Measure Efficiency, Effectiveness, and Culture to Optimize DevOps Transformation, in “Scenarios”, Mirco Hering, Dominica Degrandis, and Nicole Forsgren
you have delivered code with tests and telemetry, and the telemetry that goes with your code will substantiate or diminish the hypothesis that motivated that deployment
— Dylan Smith, Sam Guckenheimer · Progressive Deployment, Experimentation, Multitenancy, No Downtime, Cloud Security, Oh My!, Las Vegas 2018 · at 25:02
See also Done · Agile · definition of ready · user stories · abstract environment configuration · agile development
Filed under DevOps & Delivery
Every book and audiobook, the video library, the courses, and the MCP. The papers stay free.