The DevOps handbook

1. Dev and Ops goals
   1. Dev: respond to changes in market
   2. Ops: provide stable and secure service
   3. The Corre chronic conflict
      1. The downward spiral
         1. every company is a technology company
         2. 3 Acts

            Nota:

            • Act 1: Tech Debt + Ethernal Promise to fix + sys more prone to failure are the most important Act 2: Compensate broken promise with not planned/analysed new promises (+ tech debt) Act 3: Everything becomes more difficult/slower and tightly coupled. getting worse until we lose in the marketplace
         3. Costs: Learned helplessness + burnout And Lost in value creation

Nota:

• Posibles elementos a incluir desde Desarrollo para evitar el downward spiral

1. Small development teams

   Nota:

   • Lower stress and higher satisfaction
   1. frequent deployments even during the day
      1. Dark Launches
   2. Long term
      1. No culture of fear
   3. Peer reviews

1. Value streams

   Nota:

   • The sequence of activities required to design, produce, and deliver a good or service to a customer, including the dual flows of information and material.
   • Tech VS. The process required to convert a business hypothesis into a Technology-enabled service that delivers value to the customer
   1. Metrics
      1. Deployment Lead Time

         Nota:

         • From Check In to Version Control to running in production, includes testing and operation. More predictable and Mechanic. The one we should focus on
      2. Process Time

         Nota:

         • Process time starts when someone begins working on the request
      3. % C/A

         Nota:

         • Percent Complete and Accurate. It reflects the quality of output of each step in our value stream
      4. Total Lead Time

         Nota:

         • Lead time starts when the request is made and ends when it's fulfilled (what the user experiences)
2. The Three Ways
   1. Flow

      Nota:

      • Fast Flow of work from development to operations to the customer (deliver value quickly)
      • Goal: Reduce Lead Time
      1. Continuous Build, integration, test & deployment
      2. Environments on demand
      3. Limit WIP

         Nota:

         • Reduce negative impact of multitasking
         1. Limit # cards on columns
      4. Make Our Work Visible

         Nota:

         • To see where work is flowing well and where work is queued or stalled
         1. Visual work boards
      5. Reduce Batch Sizes

         Nota:

         • Large batch sizes -> skyrocketing levels of WIP and variability in flow
         • Small batch sizes -> less WIP, faster lead times, faster error detection, less rework
         1. Continuous deployment
      6. Reduce # of Handoffs
         1. Automate portions of work
         2. Reorganize teams

            Nota:

            • Reorganize teams so they can deliver value without dependencies
   2. Feedback

      Nota:

      • Enable Fast & constant flow of feedback from ops to dev at all stages of the value stream
      1. Continually shorten & amplify feedback loops
   3. Continual Learning and Experimentation

      Nota:

      • Enables the creation of a generative, high trust culture that supports a dynamic, discipined & scientific approach to experimentation and risk-taking, facilitating the creation of organizational learning
3. convergence of DevOps
   1. Theory of Constraints
   2. Toyota Kata Movement
   3. continuous delivery
   4. Lean
      1. Lean Principles
   5. Agile
   6. Infraestructure as a code