document the environment specifications 1. Create a common build mechanism to create it on demand 2. Codified in automated environment build process iii. Environments will be stable, reliable, consistent documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops was the highest each month. 40K code commits/day, 120K automated test suites, 75M tests cases/day e. CONTINUOUSLY BUILD, TEST, AND INTEGRATE OUR CODE AND ENVIRONMENTS i. Create automated test suites to increase frequency

we gave them.” 2. Accidents are due to the inevitable design problems in complex systems that we build; they are system problems – not individual problems iii. Effective practices 1. Blameless post-mortems interested in attending the meeting iv. Guidance 1. Pull all factual evidence (chat logs, etc.) to help build the timeline; any specific metrics observed, investigative paths taken, results, and other resolutions deployments. g. INJECT PRODUCTION FAILURES TO ENABLE RESILIENCE AND LEARNING i. Crumple zones in cars – build in failure modes that keep issues away from critical areas. ii. Michael Nygard, author of Release

business model or product idea is to build the complete product to see whether the predicted demand actually exists.” ii. How to build a feature: 1. Ask, “Should we build it, and why?” 2. Perform cheapest

tools in place.  It is coded in a way that resists hard-to-find defects like concurrency errors. Build Versus Buy Everyone knows that in every case under the sun, in any example one can imagine, when making decisions, if an IT product can be acquired “off the shelf,” it is better to do so than to build it. This obvious fact is neat, plausible, and in most cases, wrong. The economics of software development believed that it was riskier to develop custom code.  So, today’s choice is no longer really between build and buy. It is between quickly assembling best-practice frameworks with continuous user feedback

capabilities (how it will support future agility and how it will offer options in the future). Build Versus Buy: In a world where IT capabilities were delivered as a single “product” at the end of a risk, we should think of something we can do that will help us gain information to mitigate it. We build something, measure results, and thereby learn enough to cope with the uncertainty. “The purpose of influence the use of technology in areas he or she does not directly control. To do so, the CIO must build relationships with peers; understand the outcomes they desire; demonstrate how his or her ideas can

retrieve our golden asset, careful to carry mirrors to avoid petrification. Good luck, Agile fellows. Build Versus Buy: Everyone knows that in every case under the sun, in any example one can imagine, when making decisions, if an IT product can be acquired “off the shelf,” it is better to do so than to build it. This obvious fact is neat, plausible, and in most cases, wrong. Governance and Oversight: Governance

Tools for Large-Scale Scrum, Craig Larman  Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Jez Humble and David Farley  The Phoenix Project: A Novel About

One benefit of Agile is that once a budget has been established the program can be structured to “build to budget.” The funding that the program receives then drives the number of releases it can manage

to automate, monitor, and apply 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

Size and cost estimation – does anyone really know in absolute terms how many SLOC it will take a build a product or capability, or is it more in keeping with our nature to size something relatively to