In this chapter, I’ll introduce the DevOps area matrix, comprising four different areas, to introduce and catalog DevOps: to extend development to operations, to extend operations to development, to embed development into operations, and to embed operations into development. To each area, I’ll provide further details and examples. You’ll also learn that Kanban, a method for incrementally changing an underlying process, can be useful in applying DevOps. Finally, I’ll provide a concrete use case to bring all four areas of the DevOps matrix together and combine them with Kanban. Now let’s start discussing the DevOps area matrix.
KeywordsEvolutionary Change Work Item Operation Team Operation Area Kanban System
Unable to display preview. Download preview PDF.
- 4.See James E. Tomayko, Computers in Space flight: The NASA Experience, Chapter 4: “Computers in the Space Shuttle Avionics System” (Amazon Digital Services, 1988).Google Scholar
- 6.See Masaaki Imai, Kaizen: The Key to Japan’s Competitive Success (McGraw-Hill/Irwin, 1986), and on the Lean movementGoogle Scholar
- 6a.see Mary Poppendieck and Tom Poppendieck, Lean Software Development (Addison-Wesley, 2003), Implementing Lean Software Development (Addison-Wesley, 2006), and Leading Lean Software Development (Addison-Wesley, 2009).Google Scholar
- 9.See Mary and Tom Poppendieck, Leading Lean Software Development (Addison-Wesley, 2010), page 123.Google Scholar
- 10.For more information on common class-of-service definitions and Kanban in general, see David J. Anderson, Kanban-Successful Evolutionary Change for Your Technology Business (Blue Hole Press, 2010).Google Scholar
- 14.See Mary and Tom Poppendieck, Implementing Lean Software Development (Addison-Wesley, 2007), page 83.Google Scholar