high performers had MTTR 168x faster than low performers b. CREATE OUR CENTRALIZED TELEMETRY INFRASTRUCTURE i. Remove the silos of information – Developers don’t just log what’s interesting to development fact-based problem-solving e. ENABLE CREATION OF PRODUCTION METRICS AS PART OF DAILY WORK i. Create infrastructure to make it easy for Dev or Ops to create telemetry for functions built ii. Generate graphs problems g. FIND AND FILL ANY TELEMETRY GAPS i. Expand metrics from business, application, infrastructure, client software, and deployment pipeline levels 1. With every production incident identify

risks of the underlying infrastructure must be measured and quantified, so that the total risks and impacts to software applications are understood.  Deploy immutable infrastructure, such as containers concept of immutable infrastructure is an IT strategy in which deployed components are replaced in their entirety, rather than being updated in place. Deploying immutable infrastructure requires standardization standardization and emulation of common infrastructure components to achieve consistent and predictable resultConceptual Model DevSecOps LifecycleDevSecOps Pillars DevSecOps EcosystemDevSecOps Software Factory

share local discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards and tools, including security 4 ability to not be responsible for unsupported platforms ii. Systematically review production infrastructure and services for items that are causing disproportionate amounts of failure and unplanned work; other security/auditing relevant requirements iv. Reduce the friction by providing application/infrastructure stacks that are pre- approved and appropriately configured and secured. f. INTEGRATE SECURITY

Segregated technical and business functions  Development  Operations (Operational Waterfall)  Infrastructure Ops  Product Ops  Product Management  Every technology under the sun  Solaris, Windows iterations, planning and demos  Put everything into a repository (configurations, scripts, etc.) Infrastructure as Code  Turned over repeatable and automatable tasks to the product team wherever possible  How we need to improve  Sharing ideas, code, Community of Practice, etc.  Test Driven Infrastructure  Blue – green deployments  Combining DevOps Scrum – planning, standups, boards, and backlogs

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 Software: 2. Foreword xix can update independently without having to update other services. iii. Decouple from shared infrastructure – shared databases iv. Bounded context – compartmentalized and well-defined interfaces k. KEEP PRODUCTIVITY i. Enable Dev teams to spend more time building functionality, as opposed to created infrastructure ii. Automation – across the board iii. Create known, good environments that are ready for production

by Ops was the highest predictor of both IT performance & organizational performance d. MAKE INFRASTRUCTURE EASIER TO REBUILD THAN TO REPAIR i. Quickly building enables quickly re-creating on demand rather pre-prod(s), dev, & new) iv. Immutable Infrastructure 1. Once created no changes are allowed 2. Changes must be put into version control and then new infrastructure is created 3. To prevent variance:

test. Software engineers will oversee their code in production and help make changes to the infrastructure if necessary to improve performance.  Fairness and social responsibility: The workplace must engineer role is increasing in importance. Tests and infrastructure are now both represented in code; with SDN, soon even the network will be. Infrastructure can now be tested, like code; it can be placed in

through scripted tests.  It is deployed automatically with automated deployment tools onto infrastructure that can be automatically provisioned. The choice we have to make:  Option 1: These techniques