Overview
Streamlining change approval is a DevOps capability that aims to reduce the time it takes for changes to be approved and deployed to production. In traditional development processes, change approval can be a bottleneck that slows down the delivery of new features and updates to customers. DevOps seeks to eliminate this bottleneck by introducing automation and collaboration between development, operations, and other stakeholders.
In addition to automation, DevOps also emphasizes collaboration and communication between team members and stakeholders involved in the change approval process. This includes developers, operations personnel, quality assurance teams, and business stakeholders. By involving all parties in the approval process and establishing clear guidelines and workflows, DevOps teams can ensure that changes are thoroughly tested and approved before being deployed to production.
By streamlining the change approval process, DevOps teams can achieve faster delivery times, increased agility, and better customer satisfaction. The ability to quickly deliver new features and updates can help organizations stay ahead of the competition and respond to changing customer needs more effectively.
Streamlining change approval practices
Peer Review Process
- Ffor individual changes, enforced at the time of code check-in, and reinforced by automated tests.
Detecting Issues
- Such as regressions, performance degradation, and security vulnerabilities as soon as possible after changes are committed, using automated tools and techniques.
Ongoing Analysis
- To identify and flag changes that pose a high risk to the system, so that they can receive additional scrutiny and validation.
End-to-End Change Process
- To identify areas of inefficiency or delay and experimenting with ways to integrate validation activities into the development platform.
Information Security Controls
- Into the platform, infrastructure, and development tool chain, rather than relying on manual reviews as part of the software delivery process.
Adoption expectations
| System Components | MVP | MVP+ |
|---|---|---|
Adopt peer-review change approval process |
+ |
+ |
Identify, track and define SLAs for all required change approval steps in the software delivery process |
+ |
+ |
Shift left change approval activities |
|
+ |
Automate change approval process where possible |
|
+
|
Roles
| Name | Responsibilities |
|---|---|
Scrum Master/Team Coach |
Coach and support usage of the best engineering practices to support release on demand |
Release Train Engineer |
Streamline delivery process encouraging automation and shortening manual verification steps |
Product Owner |
Define scope and provide acceptance of new features on the earliest stages of the process |
Build Engineer |
Integrate automated quality gates and deployment process |
Test Automation Engineer (TAE) |
Implement automated tests in advance allowing continuous testing process
|
