including software and security engineers, data specialists, testers, quality assurance, and configuration managers. Ideally these participants are co-located in the same physical space. While Agile some established periods where the operational community cannot integrate new releases. 9.5 Configuration Management (CM) The many smaller developments and flexible requirements process that characterize additional CM methods for Agile include:  Assign the daily management of configuration items to the Agile team, while a Configuration Manager focuses on program/enterprise-level activities such as creating

Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps 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 and repeatable 3. Automate deployment & configuration of middleware 4. Copying packages to production servers 5. Restarting VMs, containers, applications, etc. 6. Generating configuration files 7. Run automated smoke

easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow is performing work in small batch sizes. 2. Large batch sizes

possible. Control our destiny  Started to engineer solutions for issues related to product configuration and deployment  Built a strong relationship with development (built empathy)  Development

engineers to track what they need to track, at the drop of a hat, without requiring time-sucking configuration changes or complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR

source code repository is powerful way to share local discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards