and leaner. But its great strength will be that it will be more agile, more flexible, ready to deploy quickly, innovative, and technologically advanced. That is the force for the future.” - Secretary releases, and the ability of the development environment to regularly build, integrate, test, and deploy capabilities. Acquisition, contracting, budget, test, and related processes constrain development consider six months as the release timeframe. Many private sector companies using Agile techniques deploy capabilities every month, but that cycle is likely too short for the DoD environment. Conversely

the deployment pipeline 1. Deploying the same way to every environment (begin practicing how to deploy to production in development) 2. Smoke testing our deployments – test connections to supporting ii. Blue-Green Deployment 1. Strategy a. Multiple environments with only 1 serving traffic b. Deploy to inactive environment, test, c. Swing traffic to new environment, Rollback by swinging traffic graceful performance degradation 5. Increase resilience through SOA ii. Perform Dark Launches 1. Deploy features to production without releasing to users2. Perform background testing and risk-reduction

security at all phases of the software lifecycle: plan, develop, build, test, release, deliver, deploy, operate, and monitor. In DevSecOps, testing and security are shifted to the left through automated and quantified, so that the total risks and impacts to software applications are understood.  Deploy immutable infrastructure, such as containers. The concept of immutable infrastructure is an IT strategy

Transforms or Kolmogorov-Smirnov 4. Ch. 16 – Enable Feedback So Development and Operation Can Safely Deploy Code a. USE TELEMETRY TO MAKE DEPLOYMENTS SAFER i. Actively monitor production telemetry whenever ever-safer systems of work iii. John Allspaw – A newly hired junior engineer asked permission to deploy a small HTML change. Allspaw responded, “I don’t know; is it? Did you have someone review your

that keep 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

Instead, we focus on reducing the risk of deploying functionality later than “as soon as possible.” We deploy small value-adding chunks, continuously.  In the Waterfall, we were worried about getting FOC delivered