NOTES
Note from the Publisher
1.Kim, “State of DevOps: 2020 and Beyond.”
Preface
1.Branden Williams, personal corresponence with the authors, 2015.
2.Christopher Little, personal correspondence with Gene Kim, 2010.
Introduction
1.Goldratt, Beyond the Goal.
2.Immelt, “Let’s Finally End the Debate.”
3.“Weekly Top 10: Your DevOps Flavor,” Electric Cloud.
4.Goldratt, Beyond the Goal.
5.Spear, The High-Velocity Edge, Chapter 3.
6.Christopher Little, personal correspondence with Gene Kim, 2010.
7.Skinner, “Banks Have Bigger Development Shops than Microsoft.”
8.Stehr and Grundmann, Knowledge, 139.
9.Masli et al., “Senior Executive’s IT Management Responsibilities.”
10.“IDC Forecasts Worldwide IT Spending to Grow 6%,” Business Wire.
11.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
12.Azzarello, Debruyne, and Mottura, “The Chemistry of Enthusiasm.”
13.Brooks, The Mythical Man-Month.
14.Kim et al., “Exploring the Uncharted Territory of Microservices.”
15.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
16.Jenkins, “Velocity Culture”; Exner, “Transforming Software Development.”
17.Goldratt, Beyond the Goal.
18.JGFLL, review of The Phoenix Project; Townsend, review of The Phoenix Project; Van Den Elzen, review of The Phoenix Project.
Part I Introduction
1.Beck, et al., “Twelve Principles of Agile Software.”
2.Rother, Toyota Kata, Part III.
Chapter 1
1.Martin and Osterling, Value Stream Mapping, Chapter 1.
2.Martin and Osterling, Value Stream Mapping, Chapter 3.
3.Martin and Osterling, Value Stream Mapping, Chapter 3.
4.Kersten, Project to Product.
5.Forsgren, Humble, and Kim, Accelerate 2018.
6.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
7.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
8.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
9.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
10.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
11.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
12.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
13.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
14.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
Chapter 2
1.Rubinstein, Meyer, and Evans, “Executive Control of Cognitive Processes in Task Switching.”
2.DeGrandis, “DOES15—Dominica DeGrandis—The Shape of Uncertainty.”
3.Bahri, “Few Patients-In-Process and Less Safety Scheduling.”
4.Meeting between David J. Andersen and team at Motorola with Daniel S. Vacanti, February 24, 2004; story retold at USC CSSE Research Review with Barry Boehm in March 2004.
5.Womack and Jones, Lean Thinking. Chapter 1.
6.Ries, “Work in Small Batches.”
7.Goldratt, Beyond the Goal.
8.Goldratt, The Goal, “Five Focusing Steps.”
9.Shingo, A Study of the Toyota Production System.
10.Poppendieck and Poppendieck, Implementing Lean Software, 74.
11.Poppendieck and Poppendieck, Implementing Lean Software, Chapter 4.
12.Edwards, “DevOps Kaizen.”
13.Strear, “Leadership Lessons Learned From Improving Flow.”
14.Strear, “Leadership Lessons Learned From Improving Flow.”
15.Strear, “Leadership Lessons Learned From Improving Flow.”
Chapter 3
1.Perrow, Normal Accidents.
2.Dekker, The Field Guide to Understanding Human Error.
3.Spear, The High-Velocity Edge, Chapter 8.
4.Spear, The High-Velocity Edge, Chapter 8.
5.Senge, The Fifth Discipline, Chapter 5.
6.“NUMMI,” This American Life.
7.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
8.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
9.Spear, The High-Velocity Edge, Chapter 1.
10.Spear, The High-Velocity Edge, Chapter 4.
11.Ayers and Cohen, “Andon Cords in Development Teams.”
12.Ayers and Cohen, “Andon Cords in Development Teams.”
13.Ayers and Cohen, “Andon Cords in Development Teams.”
14.Jeff Gallimore, personal correspondence with the authors, 2021.
15.Sowell, Knowledge and Decisions, 222.
16.Sowell, Basic Economics.
17.Gary Gruver, personal correspondence with Gene Kim, 2014.
Chapter 4
1.Adler, “Time-and-Motion Regained.”
2.Dekker, The Field Guide to Understanding Human Error, Chapter 1.
3.Dekker, “Just Culture: Balancing Safety and Accountability.”
4.Westrum, “The Study of Information Flow.”
5.Westrum, “A Typology of Organisation Culture.”
6.Velasquez et al., 2014 State of DevOps Report.
7.Macri, “Morgue.”
8.Spear, The High-Velocity Edge, Chapter 1.
9.Senge, The Fifth Discipline, Chapter 1.
10.Rother, Toyota Kata, 12.
11.Mike Orzen, personal correspondence with Gene Kim, 2012.
12.“Paul O’Neill,” Forbes.
13.Spear, The High-Velocity Edge, Chapter 4.
14.Spear, The High-Velocity Edge, Chapter 4.
15.Spear, The High-Velocity Edge, Chapter 4.
16.Spear, The High-Velocity Edge, Chapter 4.
17.Taleb, Antifragile.
18.Womack, Gemba Walks, Kindle location 4113.
19.Rother, Toyota Kata, Part IV.
20.Rother, Toyota Kata, Conclusion.
21.Winslow et al., Change in a Successful Organization.
22.Gertner, The Idea Factory.
23.Kersten, Project to Product; Kersten, “Project to Product: From Stories to Scenius.”
24.Brian Eno, as quoted in Sterling, “Scenius, or Communal Genius.”
25.Gertner, The Idea Factory.
26.Gertner, The Idea Factory.
Chapter 5
1.Rembetsy and McDonnell, “Continuously Deploying Culture.”
2.“Nordstrom, Inc.,” Vault (website).
3.Kissler, “DOES14—Courtney Kissler—Nordstrom.”
4.Gardner, “Barnes & Noble, Blockbuster, Borders.”
5.Kissler, “DOES14—Courtney Kissler—Nordstrom.”
6.Kissler, “DOES14—Courtney Kissler—Nordstrom” [Alterations to quote made by Courtney Kissler via personal correspondence with Gene Kim, 2016.]
7.Kissler, “DOES14—Courtney Kissler—Nordstrom” [Alterations to quote made by Courtney Kissler via personal correspondence with Gene Kim, 2016.]
8.Kissler, “DOES14—Courtney Kissler—Nordstrom” [Alterations to quote made by Courtney Kissler via personal correspondence with Gene Kim, 2016.]
9.Kissler, “DOES14—Courtney Kissler—Nordstrom” [Alterations to quote made by Courtney Kissler via personal correspondence with Gene Kim, 2016.]
10.Kissler, “DOES14—Courtney Kissler—Nordstrom” [Alterations to quote made by Courtney Kissler via personal correspondence with Gene Kim, 2016.]
11.Mueller, “Business Model Driven Cloud Adoption.”
12.Unpublished calculation by Gene Kim after the 2014 DevOps Enterprise Summit.
13.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
14.Prugh, “DOES14: Scott Prugh, CSG.”
15.Rembetsy and McDonnell, “Continuously Deploying Culture.”
16.Golden, “What Gartner’s Bimodal IT Model Means to Enterprise CIOs.”
17.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
18.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
19.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
20.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
21.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
22.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
23.Furtado and Knausenberger, “The Air Force’s Digital Journey in 12 Parsecs or Less.”
24.Golden, “What Gartner’s Bimodal IT Model Means to Enterprise CIOs.”
25.Golden, “What Gartner’s Bimodal IT Model Means to Enterprise CIOs.”
26.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
27.Scott Prugh, personal correspondence with Gene Kim, 2014.
28.Moore and McKenna, Crossing the Chasm, 11.
29.Tucci, “Four Pillars of PayPal’s ‘Big Bang’ Agile Transformation.”
30.Fernandez and Spear, “Creating High Velocity Organizations.”
31.Van Kemande, “Nothing Beats Engineering Talent.”
32.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
33.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
34.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
35.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
36.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
37.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
38.Leibman and Clanton, “DevOps: Approaching Cruising Altitude.”
39.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
40.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
41.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
42.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
43.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
44.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
45.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
46.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
47.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
48.Conrad and Hyatt, "Saving the Economy from Ruin (with a Hyperscale PaaS)."
49.Buchanan, “The Wisdom of Peter Drucker from A to Z.”
Chapter 6
1.Kissler, “DOES14—Courtney Kissler—Nordstrom.”
2.Clanton and Ducy, interview of Courtney Kissler and Jason Josephy, “Continuous Improvement at Nordstrom.”
3.Clanton and Ducy, interview of Courtney Kissler and Jason Josephy, “Continuous Improvement at Nordstrom.”
4.Clanton and Ducy, interview of Courtney Kissler and Jason Josephy, “Continuous Improvement at Nordstrom.”
5.Maskell, “What Does This Guy Do? Role of Value Stream Manager.”
6.Edwards, “DevOps Kaizen.”
7.Govindarajan and Trimble, The Other Side of Innovation.
8.Govindarajan and Trimble, The Other Side of Innovation, Part I.
9.Cagan, Inspired, 12
10.Cagan, Inspired, 12.
11.Vance, “LinkedIn.”
12.Clemm, “LinkedIn Started Back in 2003.”
13.Nielsen, “8 Years with LinkedIn.”
14.Clemm, “LinkedIn Started Back in 2003.”
15.Parikh, “From a Monolith to Microservices + REST.”
16.Clemm, “LinkedIn Started back in 2003.”
17.Vance, “LinkedIn.”
18.“How I Structured Engineering Teams at LinkedIn and AdMob for Success,” First Round Review.
19.Vance, “Inside Operation InVersion.”
20.Vance, “LinkedIn.”
21.Clemm, “LinkedIn Started Back in 2003.”
22.“How I Structured Engineering Teams,” First Round Review.
23.Christopher Little, personal correspondence with Gene Kim, 2011.
24.Ryan Martens, personal correspondence with Gene Kim, 2013.
Chapter 7
1.Conway, “How Do Committees Invent?”
2.Conway, “How Do Committees Invent?”
3.Raymond, “Conway’s Law.”
4.Buhr, “Etsy Closes Up 86 Percent on First Day of Trading.”
5.Snyder, “Scaling Etsy.”
6.Snyder, “Scaling Etsy.”
7.Gallagher, “When ‘Clever’ Goes Wrong.”
8.Snyder, “Scaling Etsy.”
9.Snyder, “Scaling Etsy.”
10.Forsgren et al., Accelerate State of DevOps 2019.
11.Snyder, “Scaling Etsy.”
12.Snyder, “Surge 2011.”
13.Snyder, “Surge 2011.”
14.Snyder, “Surge 2011.”
15.McDonnell, “Continuously Deploying Culture.”
16.Fernandez and Spear, “Creating High Velocity Organizations.”
17.Adrian Cockcroft, personal correspondence with Gene Kim, 2014.
18.“A Conversation with Werner Vogels.”
19.Forsgren, Humble, and Kim, Accelerate State of DevOps 2018; Forsgren et al., Accelerate State of DevOps 2019..
20.Spear, The High-Velocity Edge, Chapter 8.
21.Rother, Toyota Kata, 250.
22.Mulkey, “DOES15—Jody Mulkey.”
23.Mulkey, “DOES15—Jody Mulkey.”
24.Canahuati, “Growing from the Few to the Many.”
25.Spear, The High-Velocity Edge, Chapter 1.
26.Prugh, “Continuous Delivery.”
27.Prugh, “Continuous Delivery.”
28.Prugh, “Continuous Delivery.”
29.Dweck, “Carol Dweck Revisits the ‘Growth Mindset.’”
30.Cox, “Disney DevOps.”
31.John Lauderbach, personal conversation with Gene Kim, 2001.
32.Mauro, “Adopting Microservices at Netflix”; Wiggins, “The Twelve-Factor App.”
33.Shoup, “Exploring the Uncharted Territory of Microservices.”
34.Humble, O’Reilly, and Molesky, Lean Enterprise, Part III.
35.Hastings, “Netflix Culture.”
36.Dignan, “Little Things Add Up.”
37.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
38.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
39.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
40.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
41.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
42.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
43.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
44.Mickman and Clanton, “DOES15—Heather Mickman & Ross Clanton.”
Chapter 8
1.“Big Fish Celebrates 11th Consecutive Year of Record Growth,” Big Fish Games (website).
2.Paul Farrall, personal correspondence with Gene Kim, January 2015.
3.Paul Farrall, personal correspondence with Gene Kim, 2014.
4.Paul Farrall, personal correspondence with Gene Kim, 2014.
5.Ernest Mueller, personal correspondence with Gene Kim, 2014.
6.Edwards, “DevOps Kaizen.”
7.Marsh, “Dianne Marsh ‘Introducing Change while Preserving Engineering Velocity.’”
8.Cox, “Disney DevOps.”
9.Daniels, “Devopsdays Minneapolis 2015—Katherine Daniels—DevOps: The Missing Pieces.”
10.Ernest Mueller, personal correspondence with Gene Kim, 2015.
11.Takeuchi and Nonaka, “New Product Development Game.”
12.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
13.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
14.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
15.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
16.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
17.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
18.Chapman and Eltridge. “On A Mission: Nationwide Building Society.”
Chapter 9
1.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
2.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
3.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
4.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
5.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
6.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
7.Campbell-Pretty, “DOES14—Em Campbell-Pretty—How a Business Exec Led Agile, Lead, CI/CD.”
8.“Version Control History,” Plastic SCM (website).
9.Davis and Daniels, Effective DevOps, 37.
10.Velasquez et al., 2014 State of DevOps Report.
11.Sharwood, “Are Your Servers PETS or CATTLE?”
12.Chan, “OWASP AppSecUSA 2012.”
13.Fowler, “Trash Your Servers and Burn Your Code.”
14.Willis, “Docker and the Three Ways of DevOps Part 1.”
15.Forsgren et al., 2020 State of the Octoverse.
16.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
17.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
18.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
19.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
20.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
21.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
22.Holmes, " How A Hotel Company Ran $30B of Revenue in Containers."
Chapter 10
1.Gary Gruver, personal correspondence with Gene Kim, 2014.
2.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
3.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
4.“Imposter Syndrome,” Wikipedia.”
5.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
6.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
7.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
8.Potvin and Levenber, “Why Google Stores Billions of Lines of Codes in a Single Repository.”
9.Messeri, “What Goes Wrong When Thousands of Engineers Share the Same Continuous Build?”
10.Messeri, “What Goes Wrong When Thousands of Engineers Share the Same Continuous Build?”
11.Potvin and Levenber, “Why Google Stores Billions of Lines of Codes in a Single Repository.”
12.Potvin and Levenber, “Why Google Stores Billions of Lines of Codes in a Single Repository”; Messeri, “What Goes Wrong When Thousands of Engineers Share the Same Continuous Build?”
13.Jez Humble and David Farley, personal correspondence with Gene Kim, 2012.
14.Humble and Farley, Continuous Delivery, 3.
15.Humble and Farley, Continuous Delivery, 188.
16.Humble and Farley, Continuous Delivery, 258.
17.Fowler, “Continuous Integration.”
18.Fowler, “Test Pyramid.”
19.Fowler, “Test Driven Development.”
20.Nagappan et al.,“Realizing Quality Improvement through Test Driven Development.”
21.Hendrickson, “On the Care and Feeding of Feedback Cycles.”
22.“Decreasing False Positives in Automated Testing.”; Fowler, “Eradicating Non-determinism in Tests.”
23.Gruver, “DOES14—Gary Gruver—Macy’s—Transforming Traditional Enterprise Software Development Processes.”
24.Jones, “3 Ways to Get Test Automation Done Within Your Sprints.”
25.Shoup, “The Virtuous Cycle of Velocity.”
26.West, “Water scrum-fall is-reality_of_agile_for_most.”
27.Forsgren et al., Accelerate: State of DevOps 2019.
28.Forsgren, Humble, and Kim, Accelerate: State of DevOps 2018.
Chapter 11
1.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
2.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
3.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
4.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
5.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
6.Gruver and Mouser, Leading the Transformation, 60.
7.Gary Gruver, personal communication with the authors, 2016.
8.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
9.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
10.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
11.Kim, “The Amazing DevOps Transformation of the HP LaserJet Firmware Team.”
12.Atwood, “Software Branching and Parallel Universes.”
13.Cunningham, “Ward Explains Debt Metaphor.”
14.Mueller, “2012: A Release Odyssey.”
15.“Bazaarvoice, Inc. Announces Its Financial Results,” Bazaar Voice (website).
16.Mueller, “DOES15—Ernest Mueller—DevOps Transformations At National Instruments.”
17.Mueller, “DOES15—Ernest Mueller—DevOps Transformations At National Instruments.”
18.Mueller, “DOES15—Ernest Mueller—DevOps Transformations At National Instruments.”
19.Mueller, “DOES15—Ernest Mueller—DevOps Transformations At National Instruments.”
20.Mueller, “DOES15—Ernest Mueller—DevOps Transformations At National Instruments”
21.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
22.Brown, et al., State of DevOps Report; Forsgren et al., State of DevOps Report 2017.
Chapter 12
1.Rossi, “Release Engineering and Push Karma.”
2.Paul, “Exclusive: A Behind-the-Scenes Look at Facebook Release Engineering.”
3.Rossi, “Release Engineering and Push Karma.”
4.Paul, “Exclusive: a Behind-the-Scenes Look at Facebook Release Engineering.”
5.Rossi, “Ship early and ship twice as often.”
6.Beck, “Slow Deployment Causes Meetings.”
7.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
8.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
9.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
10.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
11.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
12.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
13.Puppet Labs and IT Revolution Press, 2013 State of DevOps Report.
14.Prugh and Morrison, “DOES15—Scott Prugh & Erica Morrison—Conway & Taylor Meet the Strangler (v2.0).”
15.Prugh and Morrison, “DOES15—Scott Prugh & Erica Morrison—Conway & Taylor Meet the Strangler (v2.0).”
16.Prugh and Morrison, “DOES15—Scott Prugh & Erica Morrison—Conway & Taylor Meet the Strangler (v2.0).”
17.Tim Tischler, personal conversation with Gene Kim, FlowCon 2013.
18.Puppet Labs and IT Revolution Press, 2013 State of DevOps Report.
19.Forsgren et al. Accelerate: State of DevOps 2019.
20.Dickerson, “Optimizing for Developer Happiness.”
21.Sussman and Denker, “Divide and Conquer.”
22.Sussman and Denker, “Divide and Conquer.”
23.Sussman and Denker, “Divide and Conquer.”
24.Sussman and Denker, “Divide and Conquer.”
25.Sussman and Denker, “Divide and Conquer.”
26.Kastner, “Quantum of Deployment.”
27.Fitz, “Continuous Deployment at IMVU.”
28.Fitz, “Continuous Deployment at IMVU”; Hrenko, “DOES15—Michael Hrenko—DevOps Insured By Blue Shield of California.”
29.Humble and Farley, Continuous Delivery, 265.
30.Ries, The Lean Startup.
31.Bosworth, “Building and testing at Facebook”; “Etsy’s Feature Flagging,” GitHub (website).
32.Allspaw, “Convincing Management.”
33.Rossi, “Release Engineering and Push Karma.”
34.Protalinski, “Facebook Passes 1.55B Monthly Active Asers.”
35.Protalinski, “Facebook Passes 1.55B Monthly Active Users.”
36.Letuchy, “Facebook Chat.”
37.Letuchy, “Facebook Chat.”
38.Letuchy, “Facebook Chat.”
39.Jez Humble, personal correspondence with Gene Kim, 2014.
40.Jez Humble, personal correspondence with Gene Kim, 2014.
41.Jez Humble, personal correspondence with Gene Kim, 2014.
42.Forsgren, Humble, and Kim, Accelerate State of DevOps 2018; Forsgren et al., Accelerate State of DevOps 2019.
43.Prugh and Morrison, "When Ops Swallows Dev."
44.Prugh and Morrison, "When Ops Swallows Dev."
45.Prugh and Morrison, "When Ops Swallows Dev."
46.Prugh and Morrison, "When Ops Swallows Dev."
47.Prugh and Morrison, "When Ops Swallows Dev."
48.Prugh and Morrison, "When Ops Swallows Dev."
Chapter 13
1.Humble, “What is Continuous Delivery?”
2.Kim et al., “Exploring the Uncharted Territory of Microservices.”
3.Kim et al., “Exploring the Uncharted Territory of Microservices.”
4.Kim et al., “Exploring the Uncharted Territory of Microservices.”
5.Shoup, “From Monolith to Microservices.”
6.Betz, Architecture and Patterns for IT Service Management, 300.
7.Shoup, “From Monolith to Micro-services.”
8.Shoup, “From Monolith to Micro-services.”
9.Shoup, “From Monolith to Micro-services.”
10.Vogels, “A Conversation with Werner Vogels.”
11.Vogels, “A Conversation with Werner Vogels.”
12.Vogels, “A Conversation with Werner Vogels.”
13.Vogels, “A Conversation with Werner Vogels.”
14.Jenkins, “Velocity Culture.”
15.Exner, “Transforming Software Development.”
16.Fowler, “Strangler Fig Application.”
17.Lublinsky, “Versioning in SOA.”
18.Hammant, “Introducing Branch by Abstraction.”
19.Fowler, “Strangler Fig Application.”
20.Huang, “Blackboard CEO Jay Bhatt on the Global Future of Edtech.”
21.Ashman, “DOES14—David Ashman—Blackboard Learn—Keep Your Head in the Clouds.”
22.Ashman, “DOES14—David Ashman—Blackboard Learn—Keep Your Head in the Clouds.”
23.Ashman, “DOES14—David Ashman—Blackboard Learn—Keep Your Head in the Clouds.”
24.Ashman, “DOES14—David Ashman—Blackboard Learn—Keep Your Head in the Clouds.”
25.Ashman, “DOES14—David Ashman—Blackboard Learn—Keep Your Head in the Clouds.”
26.Forsgren et al., State of DevOps Report 2017.
27.Forsgren, Humble, and Kim, Accelerate: State of DevOps 2018; Forsgren et al., Accelerate State of DevOps 2019.
Chapter 14
1.Kim, Behr, and Spafford, The Visible Ops Handbook, Introduction.
2.Kim, Behr, and Spafford, The Visible Ops Handbook, Introduction.
3.Kim, Behr, and Spafford, The Visible Ops Handbook, Introduction.
4.“Telemetry,” Wikipedia.
5.Rembetsy and McDonnell, “Continuously Deploying Culture.”
6.Rembetsy and McDonnell, “Continuously Deploying Culture.”
7.John Allspaw, personal conversation with Gene Kim, 2014.
8.Malpass, “Measure Anything, Measure Everything.”
9.Kersten, IT Revolution, and PwC, 2015 State of DevOps Report.
10.Forsgren et al., Accelerate: State of DevOps 2019.
11.Turnbull, The Art of Monitoring, Introduction.
12.Cockcroft, “Monitorama.”
13.Prugh, “DOES14: Scott Prugh, CSG—DevOps and Lean in Legacy Environments.”
14.Figureau, “The 10 Commandments of Logging.”
15.Dan North, personal correspondence with Gene Kim, 2016.
16.Chuvakin, “LogLogic/Chuvakin Log Checklist.”
17.Kim, Behr, and Spafford, The Visible Ops Handbook, Introduction.
18.North, “Ops and Operability.”
19.John Allspaw, personal correspondence with Gene Kim, 2011.
20.Agile Alliance, “Information Radiators.”
21.Ernest Mueller, personal correspondence with Gene Kim, 2014.
22.Gupta, “Visualizing LinkedIn’s Site Performance.”
23.Wong, “Eric the Intern.”
24.Wong, “Eric the Intern.”
25.Wong, “Eric the Intern.”
26.Ed Blankenship, personal correspondence with Gene Kim, 2016.
27.Burrows, “The Chubby Lock Service for Loosely-Coupled Distributed Systems.”
28.Lindsay, “Consul Service Discovery with Docker.”
29.Mulkey, “DOES15—Jody Mulkey—DevOps in the Enterprise: A Transformation Journey.”
30.Forsgren et al., Accelerate: State of DevOps 2019.
Chapter 15
1.Netflix Letter to Shareholders.
2.Roy Rapoport, personal correspondence with Gene Kim, 2014.
3.Hodge and Austin, “A Survey of Outlier Detection Methodologies.”
4.Roy Rapoport, personal correspondence with Gene Kim, 2014.
5.Roy Rapoport, personal correspondence with Gene Kim, 2014.
6.Roy Rapoport, personal correspondence with Gene Kim, 2014.
7.Boubez, “Simple Math for Anomaly Detection.”
8.Limoncelli, “Stop Monitoring Whether or Not Your Service Is Up!.”
9.Boubez, “Simple Math for Anomaly Detection.”
10.Dr. Nicole Forsgren, personal correspondence with Gene Kim, 2015.
11.Jacobson, Yuan, and Joshi, “Scryer: Netflix’s Predictive Auto Scaling Engine.”
12.Jacobson, Yuan, and Joshi, “Scryer: Netflix’s Predictive Auto Scaling Engine.”
13.Jacobson, Yuan, and Joshi, “Scryer: Netflix’s Predictive Auto Scaling Engine.”
14.Chandola, Banerjee, and Kumar, “Anomaly Detection: A Survey.”
15.Tarun Reddy, personal interview with Gene Kim, Rally headquarters, Boulder, CO, 2014.
16.“Kolmogorov-Smirnov Test,” Wikipedia.
17.Boubez, “Simple Math for Anomaly Detection.”
18.Boubez, “Simple Math for Anomaly Detection.”
Chapter 16
1.Walsh, “Ad Firms Right Media.”
2.Nick Galbreath, personal conversation with Gene, 2013.
3.Galbreath, “Continuous Deployment.”
4.Galbreath, “Continuous Deployment.”
5.Galbreath, “Continuous Deployment.”
6.Canahuati, “Growing from the Few to the Many.”
7.Lightbody, “From Inception to Acquisition.”
8.Chakrabarti, “Common Ops Mistakes.”
9.Sussna, “From Design Thinking to DevOps and Back Again.”
10.Anonymous, personal conversation with Gene Kim, 2005.
11.Limoncelli, “SRE@Google.”
12.Treynor, “Keys to SRE.”
13.Limoncelli, “SRE@Google.”
14.Limoncelli, “SRE@Google.”
15.Limoncelli, “SRE@Google.”
16.Tom Limoncelli, personal correspondence with Gene Kim, 2016.
17.Tom Limoncelli, personal correspondence with Gene Kim, 2016.
Chapter 17
1.Humble, O’Reilly and Molesky, Lean Enterprise, Part II.
2.Intuit, Inc., “2012 Annual Report.”
3.Cook, “Leadership in an Agile Age.”
4.Cook, “Leadership in an Agile Age.”
5.Cook, “Leadership in an Agile Age.”
6.“Direct Marketing,” Wikipedia.
7.“Fighting Poverty With Actual Evidence: Full Transcript,” Freakonomics (blog).
8.Kohavi, Crook, and Longbotham, “Online Experimentation at Microsoft.”
9.Kohavi, Crook, and Longbotham, “Online Experimentation at Microsoft.”
10.Jez Humble, personal correspondence with Gene Kim, 2015.
11.Wang, “Etsy’s Culture Of Continuous Experimentation.”
12.O’Reilly, “How to Implement Hypothesis-Driven Development.”
13.Kim, “Organizational Learning and Competitiveness.”
14.Kim, “Organizational Learning and Competitiveness.”
15.Kim, “Organizational Learning and Competitiveness.”
16.Kim, “Organizational Learning and Competitiveness.”
17.Kim, “Organizational Learning and Competitiveness.”
18.Kim, “Organizational Learning and Competitiveness.”
19.Kim, “Organizational Learning and Competitiveness.”
Chapter 18
1.Chacon, “GitHub Flow.”
2.Douglas, “Deploying at GitHub.”
3.Allspaw, “Counterfactual Thinking, Rules, and the Knight Capital Accident.”
4.Allspaw, “Counterfactual Thinking, Rules, and the Knight Capital Accident.”
5.Staats and Upton, “Lean Knowledge Work.”
6.Forsgren et al., Accelerate State of DevOps 2019.
7.Forsgren et al., Accelerate State of DevOps 2019.
8.Velasquez et al., 2014 State of DevOps Report.
9.Randy Shoup, personal interview with Gene Kim, 2015.
10.Özil, “Ask a programmer.”
11.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
12.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
13.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
14.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
15.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
16.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
17.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
18.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
19.Cornago, Yadav, and Otto, "From 6-Eye Principle to Release at Scale - adidas Digital Tech 2021."
20.Özil, “Ask a programmer to review 10 lines of code.”.
21.Messeri, “What Goes Wrong When Thousands of Engineers Share the Same Continuous Build?”
22.Thomas and Kumar, “Welcome to the Google Engineering Tools Blog.”
23.Kumar, “Development at the Speed and Scale of Google.”
24.Randy Shoup, personal correspondence with Gene Kim, 2014.
25.Atwood, “Pair Programming vs. Code Reviews.”
26.Atwood, “Pair Programming vs. Code Reviews.”
27.“Pair Programming,” ALICE Wiki page.
28.“Pair Programming,” ALICE Wiki page.
29.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
30.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
31.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
32.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
33.Hendrickson, “DOES15—Elisabeth Hendrickson—Its All About Feedback.”
34.Ryan Tomayko, personal correspondence with Gene Kim, 2014.
35.Ryan Tomayko, personal correspondence with Gene Kim, 2014.
36.Ryan Tomayko, personal correspondence with Gene Kim, 2014.
37.Ryan Tomayko, personal correspondence with Gene Kim, 2014.
38.Ryan Tomayko, personal correspondence with Gene Kim, 2014.
39.Cockcroft, Ducy, and Clanton, “Adrian Cockcroft of Battery Ventures.”
40.Pal, “DOES15—Tapabrata Pal—Banking on Innovation & DevOps.”
41.Cox, “Disney DevOps.”
42.Clanton and Mickman, “DOES14—Ross Clanton and Heather Mickman—DevOps at Target.”
43.Clanton and Mickman, “DOES14—Ross Clanton and Heather Mickman—DevOps at Target.”
44.Clanton and Mickman, “DOES14—Ross Clanton and Heather Mickman—DevOps at Target.”
45.Clanton and Mickman, “DOES14—Ross Clanton and Heather Mickman—DevOps at Target.”
46.Clanton and Mickman, “DOES14—Ross Clanton and Heather Mickman—DevOps at Target.”
47.John Allspaw and Jez Humble, personal correspondence with Gene Kim, 2014.
Chapter 19
1.Spear, The High-Velocity Edge, Chapter 1.
2.Spear, The High-Velocity Edge, Chapter 1.
3.Pepitone, “Amazon EC2 Outage Downs Reddit, Quora.”
4.Morgan, “A Rare Peek into the Massive Scale of AWS.”
5.Cockcroft, Hicks, and Orzell, “Lessons Netflix Learned from the AWS Outage.”
6.Cockcroft, Hicks, and Orzell, “Lessons Netflix Learned from the AWS Outage.”
7.Cockcroft, Hicks, and Orzell, “Lessons Netflix Learned from the AWS Outage.”
8.Dekker, “Just Culture,” 152.
9.Dekker, “DevOpsDays Brisbane 2014—Sidney Decker—System Failure, Human Error: Who’s to Blame?”
10.Allspaw, “Post-Mortems, Sans Finger-Pointing.”
11.Allspaw, “Blameless PostMortems and a Just Culture.”
12.Malpass, “DevOpsDays Minneapolis 2014—Ian Malpass, Fallible Humans.”
13.Milstein, “Post-Mortems at HubSpot: What I Learned from 250 Whys.”
14.Randy Shoup, personal correspondence with Gene Kim, 2014.
15.Google, “Post-Mortem for February 24, 2010 Outage”; Amazon Web Services, “Summary of the Amazon DynamoDB Service Disruption and Related Impacts in the US-East Region.”
16.Macri, “Morgue.”
17.Macri, “Morgue.”
18.Forsgren, Humble, and Kim, Accelerate: State of DevOps 2018.
19.Edmondson, “Strategies for Learning from Failure.”
20.Spear, The High-Velocity Edge, Chapter 4.
21.Spear, The High-Velocity Edge, Chapter 4.
22.Spear, The High-Velocity Edge, Chapter 3.
23.Roberto, Bohmer, and Edmondson, “Facing Ambiguous Threats.”
24.Roberto, Bohmer, and Edmondson, “Facing Ambiguous Threats.”
25.Roberto, Bohmer, and Edmondson, “Facing Ambiguous Threats.”
26.Roy Rapoport, personal correspondence with Gene Kim, 2012.
27.Roy Rapoport, personal correspondence with Gene Kim, 2012.
28.Roy Rapoport, personal correspondence with Gene Kim, 2012.
29.Nygard, Release It!, Part I.
30.Barr, “EC2 Maintenance Update.”
31.Wong and Kalantzis, “A State of Xen—Chaos Monkey & Cassandra.”
32.Wong and Kalantzis, “A State of Xen—Chaos Monkey & Cassandra.”
33.Wong and Kalantzis, “A State of Xen—Chaos Monkey & Cassandra.”
34.Roy Rapoport, personal correspondence with Gene Kim, 2015.
35.Adrian Cockcroft, personal correspondence with Gene Kim, 2012.
36.Robbins, “GameDay.”
37.Robbins et al., “Resilience Engineering.”
38.Robbins et al., “Resilience Engineering.”
39.Robbins et al., “Resilience Engineering.”
40.Robbins et al., “Resilience Engineering.”
41.Robbins et al., “Resilience Engineering.”
42.Krishman, “‘Learning Continuously From Failures’ at Google.”
43.Krishnan, “Weathering the Unexpected.”
44.Krishnan, “Weathering the Unexpected.”
45.Morrison, “How We Turned Our Company’s Worst Outage into a Powerful Learning Opportunity.”
46.Widely attributed to Peter Senge.
Chapter 20
1.Newland, “ChatOps at GitHub.”
2.Newland, “ChatOps at GitHub.”
3.Mark Imbriaco, personal correspondence with Gene Kim, 2015.
4.Newland, “ChatOps at GitHub.”
5.Newland, “ChatOps at GitHub.”
6.Newland, “ChatOps at GitHub.”
7.Newland, “ChatOps at GitHub.”
8.Osterweil, “Software Processes are Software Too.”
9.Arbuckle, “What Is ArchOps: Chef Executive Roundtable.”
10.Arbuckle, “What Is ArchOps: Chef Executive Roundtable.”
11.Arbuckle, “What Is ArchOps: Chef Executive Roundtable.”
12.Metz, “Google Is 2 Billion Lines of Code—and It’s All in One Place.”
13.Metz, “Google Is 2 Billion Lines of Code—and It’s All in One Place.”
14.Metz, “Google Is 2 Billion Lines of Code—and It’s All in One Place.”
15.Messeri, “What Goes Wrong When Thousands of Engineers Share the Same Continuous Build?”
16.Randy Shoup, personal correspondence with Gene Kim, 2014.
17.Limoncelli, “Yes, You Can Really Work from HEAD.”
18.Forsgren et al., Accelerate: State of DevOps 2019.
19.Forsgren et al., Accelerate: State of DevOps 2019.
20. Mell and Grance, The NIST Definition of Cloud Computing, 6.
21.Forsgren et al., Accelerate: State of DevOps 2019.
22.Loura, Jacques, and Garcia, “DOES15—Ralph Loura, Olivier Jacques, & Rafael Garcia—Breaking Traditional IT Paradigms.”
23.Rembetsy and McDonnell, “Continuously Deploying Culture.”
24.Rembetsy and McDonnell, “Continuously Deploying Culture.”
25.McKinley, “Why MongoDB Never Worked Out at Etsy.”
26.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
27.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
28.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
29.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
30.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
31.Cundiff, Geinert, and Rettig, “Crowdsourcing Technology Governance.”
Chapter 21
1.“Kaizen,” Wikipedia.
2.Spear, The High-Velocity Edge, Chapter 8.
3.Spear, The High-Velocity Edge, Chapter 8.
4.Mickman and Clanton, “(Re)building an Engineering Culture.”
5.Ravi Pandey, personal correspondence with Gene Kim, 2015.
6.Mickman and Clanton, “(Re)building an Engineering Culture.”
7.Pomeranz, “Queue Inversion Week.”
8.Spear, The High-Velocity Edge, Chapter 3.
9.Stillman, “Hack Days.”
10.Associated Press, “Number of Active Users at Facebook over the Years.”
11.Zhao, “HipHop for PHP.”
12.Metz, “How Three Guys Rebuilt the Foundation of Facebook.”
13.Metz, “How Three Guys Rebuilt the Foundation of Facebook.”
14.Steve Farley, personal correspondence with Gene Kim, January 5, 2016.
15.Gaekwad, “Agile 2013 Talk.”
16.O’Donnell, “DOES14—Glenn O’Donnell—Forrester—Modern Services Demand a DevOps Culture Beyond Apps.”
17.Smart et al., Sooner Safer Happier, 314.
18.Nationwide, 2014 Annual Report.
19.Steve Farley, personal correspondence with Gene Kim, 2016.
20.Pal, “DOES15—Tapabrata Pal—Banking on Innovation & DevOps.”
21.Pal, “DOES15—Tapabrata Pal—Banking on Innovation & DevOps.”
22.Tapabrata Pal, personal correspondence with Gene Kim, 2015.
23.“All About Target,” Target (website).
24.Mickman and Clanton, “(Re)building an Engineering Culture.”
25.Van Leeuwen and Buytaert, “DOES15—Evelijn Van Leeuwen and Kris Buytaert—Turning Around the Containership.”
26.Mickman and Clanton, “(Re)building an Engineering Culture.”
27.“DevOps Culture: How to Transform."
28.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
29.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
30.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
31.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
32.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
33.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
34.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
35.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
36.Bland, “Fixits, or I Am the Walrus.”
37.Bland, “Fixits, or I Am the Walrus.”
38.Bland, “Fixits, or I Am the Walrus.”
Chapter 22
1.Wickett, “Attacking Pipelines–Security Meets Continuous Delivery.”
2.Wickett, “Attacking Pipelines—Security Meets Continuous Delivery.”
3.Pal, “DOES15—Tapabrata Pal—Banking on Innovation & DevOps.”
4.Justin Arbuckle, personal interview with Gene Kim, 2015.
5.Justin Arbuckle, personal interview with Gene Kim, 2015.
6.Antani, “IBM Innovate DevOps Keynote.”
7.Galbreath, “DevOpsSec: Applying DevOps Principles to Security, DevOpsDays Austin 2012.”
8.Galbreath, “DevOpsSec: Applying DevOps Principles to Security, DevOpsDays Austin 2012.”
9.“OWASP Cheat Sheet Series,” OWASP (website).
10.Collins, Smolen, and Matatall, “Putting to your Robots to Work V1.1.”
11.“What Happens to Companies That Get Hacked? FTC Cases,” Giant Bomb forum.
12.“What Happens to Companies That Get Hacked? FTC Cases,” Giant Bomb forum.
13.Collins, Smolen, and Matatall, “Putting to your Robots to Work V1.1.”
14.Twitter Engineering, “Hack Week @ Twitter.”
15.Twitter Engineering, “Hack Week @ Twitter.”
16.Corman and Willis, “Immutable Awesomeness—Josh Corman and John Willis at DevOps Enterprise Summit 2015.”
17.Forsgren et al., 2020 State of the Octoverse.
18.Forsgren et al., 2020 State of the Octoverse.
19.Verison, 2014 Data Breach Investigations Report.
20.Verizon, 2021 Data Breach Investigations Report, 20.
21.Sonatype, 2019 State of the Software Supply Chain Report.
22.Sonatype, 2019 State of the Software Supply Chain Report.
23.Sonatype, 2019 State of the Software Supply Chain Report.
24.“Jeremy Long: The (Application)Patching Manifesto.”
25.“Jeremy Long: The (Application)Patching Manifesto.”
26.Sonatype, 2019 State of the Software Supply Chain Report.
27.Sonatype, 2019 State of the Software Supply Chain Report.
28.Sonatype, 2019 State of the Software Supply Chain Report.
29.Sonatype, 2019 State of the Software Supply Chain Report.
30.Sonatype, 2020 State of the Software Supply Chain Report.
31.Sonatype, 2020 State of the Software Supply Chain Report.
32.Geer and Corman, “Almost Too Big to Fail.”
33.Forsgren et al., 2020 State of the Octoverse.
34.Temple-Raston, “A ‘Worst Nightmare’ Cyberattack.”
35.Naraine, “Twilio, HashiCorp Among Codecov Supply Chain Hack Victims.”
36.Kash, “New Details Released on Proposed 2016 IT Spending.”
37.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
38.Bland, “DOES15—Mike Bland—Pain Is Over, If You Want It.”
39.Zia, Ramírez, and Kunin, “Compliance Masonry.”
40.Marcus Sachs, personal correspondence with Gene Kim, 2010.
41.“VPC Best Configuration Practices,” Flux7 blog.
42.Galbreath, “Fraud Engineering, from Merchant Risk Council Annual Meeting 2012.”
43.Galbreath, “DevOpsSec.”
44.Galbreath, “DevOpsSec.”
45.Galbreath, “DevOpsSec.”
46.Galbreath, “DevOpsSec.”
47.Galbreath, “DevOpsSec.”
48.Galbreath, “DevOpsSec.”
49.Claudius, “Attacking Cloud Services with Source Code.”
50.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
51.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
52.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
53.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
54.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
55.Johnson, et. al., “How Fannie Mae Uses Agility to Support Homeowners and Renters.”
56.Kimberly Johnson, personal correspondence with the authors, 2021.
Chapter 23
1.Axelos, ITIL Service Transition, 48.
2.Axelos, ITIL Service Transition, 48 and 68.
3.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
4.Mangot and Rajan, “Agile.2013.effecting.a.dev ops.transformation.at.salesforce.”
5.Mangot and Rajan, “Agile.2013.effecting.a.dev ops.transformation.at.salesforce.”
6.Mangot and Rajan, “Agile.2013.effecting.a.dev ops.transformation.at.salesforce.”
7.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
8.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
9.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
10.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
11.Matthew and Mangot, “DOES14—Reena Mathew and Dave Mangot—Salesforce.”
12.Bill Massie, personal correspondence with Gene Kim, 2014.
13.“Glossary,” PCI Security Standards Council website.
14.PCI Security Standards Council, Payment Card Industry (PCI) Data Security Stands.
15.Bill Massie, personal correspondence with Gene Kim, 2014.
16.Bill Massie, personal correspondence with Gene Kim, 2014.
17.Bill Massie, personal correspondence with Gene Kim, 2014.
18.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
19.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
20.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
21.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
22.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
23.Basu, Goyal, and Hansen, "Biz & Tech Partnership Towards 10 'No Fear Releases' Per Day."
24.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
25.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
26.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
27.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
28.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
29.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
30.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
31.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
32.Shinn, “DOES15—Bill Shinn—Prove it! The Last Mile for DevOps in Regulated Organizations.”
33.DeLuccia, Gallimore, Kim, and Miller, DevOps Audit Defense Toolkit.
34.Mary Smith (a pseudonym), personal correspondence with Gene Kim, 2013.
35.Mary Smith (a pseudonym), personal correspondence with Gene Kim, 2013
Conclusion
1.Robbins, “Hacking Culture at VelocityConf.”
Afterword
1.Forsgren et al., 2020 State of the Octoverse.
2.Wiseman, 2021 Work Trend Index: Annual Report.
3.Forsgren et al., “The SPACE of Developer Productivity.”
Appendix
1.Ries, The Lean Startup.
2.Beck et al., “Twelve Principles of Agile Software.”
3.Humble and Farley, Continuous Delivery.
4.Fitz, “Continuous Deployment at IMVU.”
5.Rother, Toyota Kata, Introduction.
6.Rother, Toyota Kata, Introduction.
7.Ries, The Lean Startup.
8.Kim, Behr, and Spafford, The Phoenix Project, 365.
9.Besnard and Hollnagel, Some Myths about Industrial Safety, 3.
10.Besnard and Hollnagel, Some Myths about Industrial Safety, 4.
11.Besnard and Hollnagel, Some Myths about Industrial Safety, 6.
12.Besnard and Hollnagel, Some Myths about Industrial Safety, 8.
13.Besnard and Hollnagel, Some Myths about Industrial Safety, 9.
14.Besnard and Hollnagel, Some Myths about Industrial Safety, 11.
15.Shook, “Five Missing Pieces in Your Standardized Work (Part 3 of 3).”
16.“Post Event Retrospective—Part 1,” Rally Blogs.
17.Macri, “Morgue.”
18.Cockcroft, Hicks, and Orzell, “Lessons Netflix Learned.”
19.Cockcroft, Hicks, and Orzell, “Lessons Netflix Learned.”
20.Rachitsky, “7 Keys to a Successful Public Health Dashboard.”