dependencies – eliminates “worked on my machine” 3. Package the application to enable repeatable installation and configuration into an environment 4. Environments can be more production-like in a consistent AUTOMATE OUR DEPLOYMENT PROCESS i. Begin with documenting the steps for current deployment process ii. Simplify and automate through the steps 1. Packaging code in method suitable for deployment2. Create deployed code v. 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

characteristics rather than by conducting exhaustive paper analysis. The requirements process prioritizes steps in the development to deliver the highest priority capabilities to the user with each release. Moreover toward traditional development strategies. Rather than simply follow a recipe of Agile methods and steps, programs should try to adopt the Agile philosophy and10 mindset to instill program agility. Establishing programs with software costs over $15M and with COTS or Government off-the-Shelf (GOTS) hardware installation or technology refresh. It does not apply to business systems or IS embedded in weapon systems

better control practices could have detected the risk earlier prevent the issue or could have taken steps to detect and recover faster 2. Accident due to testing failure – seems valid since better testing diminish effectiveness of feedback from the deployment process 2. Increase friction by adding more steps/approvals which tends to increase batch size ii. Toyota Production System – “people closest to a – reviewing work, considers strategic direction, generating ideas for improvement and the next steps 3. Supports ad-hoc cross training ii. Dr. Laurie Williams, 2001 study – “paired programmers are

ninety percent of the time, the tasks would spend in queue a total of nine hours time the seven steps…” Change Control  “We need to tighten up our change controls… what’s preventing us from getting

communication among mindsPast Breakthroughs Solved Accidental Difficulties“If we examine the three steps in software technology that have been most fruitful in the past, we discover that each attacked

Feedback 27 i. KEEP PUSHING QUALITY CLOSER TO THE SOURCE 1. In complex systems, adding more inspection steps and approval processes actually increases the likelihood of future failures. The effectiveness of

NORMAL CHANGES i. If change approval board is required, aim for quick deployment even if manual steps are required ii. Use tooling to generate the artifacts needed for approval. Share evidence and artifacts