environments 2. Deployment tools 3. Testing standards and tools, including security 4. Deployment pipeline tools 5. Monitoring and analysis tools 6. Tutorials and standards ii. Google – Single repository for fast flow, deployability, and operations will derive NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring work as repeatable Integrate security with our deployment pipeline iv. Integrate security with our telemetry for better detection and recovery v. Protect our deployment pipeline vi. Integrate our deployment activities

fast flow of work by implementing continuous delivery i. Create the foundation of our deployment pipeline ii. Enabling fast & reliable automated testing iii. Enabling & practicing continuous integration objectives of QA & Operations to improve outcomes 2. Ch. 9 – Create the Foundations of Our Deployment Pipeline a. Enterprise Data Warehouse program by Em Campbell-Pretty - $200M, All streams of work were significantly Environments can be more production-like in a consistent and repeatable wayiii. Building a deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and code quality (static

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 Church of Graphs. i. Expand metrics from business, application, infrastructure, client software, and deployment pipeline levels 1. With every production incident identify missing telemetry that could help detect and identify opportunity costs. d. INTEGRATE A/B TESTING INTO OUR RELEASE i. A/B testing requires fast CD to support ii. Use feature toggles to control experiments, cohort creation, etc. iii. Use telemetry

Requirements Definition Packages (RDPs) to capture a subset of the IS ICD scope and/or Capability Drop (CD) documents for smaller items such as applications (see Figure 13). Services and requirements oversight As illustrated in Figure 14, each RDP captures a set of requirements prioritized for a release. A CD captures the release backlog requirements allocated to a sprint and forms the basis for a sprint backlog capabilities to inform and shape future releases. Lastly, short development timelines provide a steady pipeline to infuse mature technologies effectively integrated into the system and enterprise. An Agile

Requirements Definition Packages (RDPs) to capture a subset of the IS ICD scope and/or Capability Drop (CD) documents for smaller items such as applications o Replace comprehensive Preliminary Design Reviews