The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations¶
Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations: How to Create World-Class Agility, Reliability, and Security in Technology Organizations.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Accidental Vs Essential Complexity
- Lean manufacturing and software DevOps attack accidental process complexity with structurally identical interventions — continuous flow, small batches, eliminated handoffs — in a transfer that is explicit and well documented.
This sourceExplicitly transfers lean-manufacturing principles — continuous flow, small batch sizes, eliminated handoffs — to software delivery, documenting the structurally identical attack on accidental process complexity across the two domains. (Book; no DOI — ISBN 9781942788003.)
- Lean manufacturing and software DevOps attack accidental process complexity with structurally identical interventions — continuous flow, small batches, eliminated handoffs — in a transfer that is explicit and well documented.
- Controlled Reentry
- Software engineering: Process resume after circuit-break (gradual traffic ramp-up), canary deployments (small-scale rollout to detect issues before full rollout), rolling updates with health-check gates, shadow-mode testing (new system runs in parallel before traffic switch), staged rollout after security incident—the cluster of practices Kim, Humble, Debois, and Willis (2016) catalog as "architecting for low-risk releases."
This sourceCatalogs canary, blue-green, dark launch, and rolling-update as low-risk release techniques.
- Software engineering: Process resume after circuit-break (gradual traffic ramp-up), canary deployments (small-scale rollout to detect issues before full rollout), rolling updates with health-check gates, shadow-mode testing (new system runs in parallel before traffic switch), staged rollout after security incident—the cluster of practices Kim, Humble, Debois, and Willis (2016) catalog as "architecting for low-risk releases."
Verification¶
Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:d75b87ab16c5 · see in the full table