Dev/Test environments matched Prod. They fixed forward, but changes not put back into version control. Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b the system are shared in a version control repository ii. Version control is for everyone in the value stream iii. Everything, everything, everything is checked into version control 1. Application code includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops was the highest predictor of both IT performance & organizational performance d

integrity and code signing – all contributors should have their own key and sign all commits to version control. All created packages should be signed and hash recorded for auditing h. ENSURE SECURITY certain types of test code) 4. Ensure every CI process is in an isolated container 5. Make the version control credentials of the CI system read-only 3. Ch. 23 – Protecting the Deployment Pipeline a demonstrate high success rates and low MTTR iii. Link and provide traceability from planning to version control to production implementation for visibility and auditing c. WHAT TO DO WHEN CHANGES ARE

GIT is a version control system that is used for software development and other version control tasks. As a distributed revision control system it is aimed at speed, data integrity, and support for

Horner Kanban for the People! 2 Steve Miller Crucial Conversations (Agile Book Club!) 0 Nick Tuck Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Ray Page Release Planning Planning 1 Adam Raggett Agile Transparency 1 Eric Collins The Servant: Agile Book Club 1 Nick Tuck Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Agile Transformation Agility

Frequent code updates and automated testing create a high demand32 for managing the complexity of version control. If issues arise, the team can revert to earlier versions and identify the steps that must managers should ensure their programs use the appropriate development and test tool environments, version control, and change management mechanisms to incorporate continuous integration into the development Blogs  Disciplined Agile Delivery blog by Scott Ambler and Mark Lines  Agile Management by Version One  Scott Ambler's IBM Blog  Leading Answers Blog  Effective Practices for Software

Steve Miller Crucial Conversations (Agile Book Club1) Nick Tuck Version Control Comparison Dr Mark Roth Release It (Agile Book Review) Aug 2014 Ray Page

long it takes for a new requirement to be delivered and deployed. Deployment speed: how fast a new version of the application can be deployed into the production environment. Deployment frequency: how often

soon even the network will be. Infrastructure can now be tested, like code; it can be placed in version control.  Technology matters: Most IT people are technologists; they need to work with technology