Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE ON-DEMAND CREATION OF DEV, TEST, AND PRODUCTION ENVRIONMENTS i. Major contributing cause behaves in a production-like environment ii. Don’t just document the environment specifications 1. Create a common build mechanism to create it on demand 2. Codified in automated environment build process everything, everything is checked into version control 1. Application code & dependencies 2. Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests

operations and automation forward by “light-years” and had performed huge number of production deployments. g. INJECT PRODUCTION FAILURES TO ENABLE RESILIENCE AND LEARNING i. Crumple zones in cars – build in issues away from critical areas. ii. Michael Nygard, author of Release It! Design and Deploy Production-Ready Software, “If you do not design your failure modes, then you will get whatever unpredictable—and operations influence components used in production or have the ability to not be responsible for unsupported platforms ii. Systematically review production infrastructure and services for items that

within each element of their programs, thus helping them to succeed in an increasingly complex environment. Agile has emerged as the leading industry software development methodology, and has seen growing Some practices can even be applied to non-IT acquisitions. Program managers should evaluate the environment, constraints, and objectives to determine the right structure and methods to apply. Agile requires offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint force will be smaller and leaner. But its great strength will be that it will

simultaneously. Key Measures Mean-time to production: the average time it takes from when new software features are required until they are running in production. Average lead-time: how long it takes for into the production environment. Deployment frequency: how often a new release can be deployed into the production environment. Production failure rate: how often software fails during production. Mean-time Mean-time to recovery: how long it takes applications in the production stage to recover from failure. Key Principles to implementing a successful DevSecOps approach  Remove bottlenecks (including human

times more frequent) ii. Code and change deployment lead time (two hundred times faster) iii. Production deployments (sixty times higher change success rate) iv. Mean time to restore service (168 times releases, where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing, this large batch release creates sudden, high levels of WIP This validates our common experience that the larger the change going into production, the more difficult the production errors are to diagnose and fix, and the longer they take to remediate. iii.

equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry as part of their daily workii. If it was important enough for an engineer engineer to implement, it is certainly important enough to generate enough production telemetry so that we can confirm that is it operating as designed and outcomes are being achieved. iii. Logging Levels

much time to get my products into production.  Thought I would get over there fix “their” problems.  Discovered, multiple teams involved in snowflake environment support.  The practice team wasn’t cross-trained on each other’s concerns – empathy  Combined the development support team with the production support team.  Operations becomes familiar with new features in QA, rather than in front of and More opportunities to fail, iterate, and improve.  Incented innovation and optimization.  Environment homogenization and assimilation – no snowflakes  Deployment methodologies, automation, monitoring

this approach can focus IT planning, reduce risk, eliminate waste, and provide a supportive environment for teams engaged in creating value. If you missed last month, you can find the handout for Part passes its tests; that is a yes-or-no question independent of quality.  Once the feature is in production, we can assess its quality based on its fit to need, or perhaps its actual success in accomplishing people who normally do development will help test. Software engineers will oversee their code in production and help make changes to the infrastructure if necessary to improve performance.  Fairness and

a way that lets it interoperate with the rest of the legacy system. We launch that piece into production and have users use it seamlessly as if it is part of the legacy system.  Then we take another this approach can focus IT planning, reduce risk, eliminate waste, and provide a supportive environment for teams engaged in creating value. Risk: The presence of uncertainty is the simple reason why

the capacity of each resource, each bowl; the set of bowls are my dependent events, my stages of production. Each has exactly the same capacity as the others, but its actual yield will fluctuate somewhat