not far removed groups. b. Shift away from periodic inspections and approvals; move to integrated peer reviews performed continually as part of daily work c. THE DANGERS OF CHANGE APPROVAL PROCESSES most about it.” iii. 2014 State of DevOps Report – high performing organizations relied more on peer review and less on external approval of change. The more organizations relied on change approvals authorize changes, but to schedule and sequence. f. ENABLE PEER REVIEW OF CHANGES i. Require peer reviews, not external board approval ii. Peer review help improve overall quality, provide cross-training

special committees for approval and processing and then waiting for responses 3. Instead a. Use peer reviews of our proposed changes to gain whatever assurance is needed that our changes will operate

progressing at faster rates iii. Pair with individuals from other organizations & teams iv. Participate in peer reviews e. SHARE YOUR EXPERIENCES FROM DEVOPS CONFERENCES i. Cost is always a consideration. BUT

mechanisms to mitigate risks more effectively using 1. Automated testing 2. Automated deployment 3. Peer reviews iv. 2013 State of DevOps Report – no statistically significant difference in change success

would have a quick meeting between the program team, me, and the business unit leader who was my peer. The main purpose of these meetings was to laugh a lot, make fun of the Star Chamber’s serious facial