with Information Security and Compliance: e. Myth—DevOps Means Eliminating IT Operations, or “NoOps” f. Myth—DevOps is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Partially done work: b. Extra processes: c. Extra features: d. Task switching: e. Waiting: f. Motion: g. Defects: h. Nonstandard or manual work:i. Heroics: d. The Second Way: The Principles your condition now? d. What is your next target condition? e. What obstacle are you working on now? f. What is your next step? g. What is your expected outcome? h. When can we check? 6. PART II—WHERE

day every exercise and new piece of information is evaluated and debated; more similar to R&D lab. f. REDEFINE FAILURE AND ENCOURAGE CALCULATED RISK-TAKING i. Leaders reinforce the culture through their fast flow, deployability, and operations will derive NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring work as repeatable conferences, give talks, and then sharing back to the organization what was learned ii. Attend Meetups! f. CREATE INTERNAL CONSULTING AND COACHES TO SPREAD PRACTICES i. Capital One – SMEs hold open office

with overlays of production changes iii. Tools – StatsD, JMX, codahale, New Relic, Prometheus, etc. f. CREATE SELF-SERVICE ACCESS TO TELEMETRY AND INFORMATION RADIATORS i. Spread the information – anyone deliberate change scheduling, gather representatives, not authorize changes, but to schedule and sequence. f. ENABLE PEER REVIEW OF CHANGES i. Require peer reviews, not external board approval ii. Peer review

tests fail 3. Developers working in small batches on trunk rather than long-lived feature branches f. BUILD A FAST AND RELIABLE AUTOMATED VALIDATION TEST SUITE i. Slow and periodic feedback kills – larger Enable fast flow through common promotion process anyone can run without manual steps and handoffs f. INTEGRATE CODE DEPLOYMENT INTO THE DEPLOYMENT PIPELINE i. Ensures packages created by CI are suitable