This template focuses on the technical and collaborative practices that enable teams to build quality into their application, making it more reliable. Influenced by many DevOps pioneers and thought leaders, this template provides teams with an opportunity to reflect and improve on the DevOps practices required to build a resilient and stable application in today’s fast-moving business environments.
Any team focused on DevOps.
Works of thought leaders that influenced the Practice's Technique Criteria, assigned Agility Stage, and impacted Business Outcomes.
16 total practices
• Team Focus on Value
• Team Synergy
• DevOps Build Cycle
• DevOps Deploy & Config
• DevOps Monitoring
• DevOps Recovery
• DevOps Release
• DevOps Security
• DevOps Testing
• Team Agile Architecture
• Team Definition of Done
• Team Flow of Value
• Team Self-Organization
• Team Learning Culture
• Team Retrospective
• Team Leadership Engagement
The team has a manual and reactive build processes with little or no management of artifacts, source code, and reporting
Source Code is versioned and managed in VCS
Management of build artifacts
Scheduled or polling build process that integrates code at least daily
Builds can be recreated from source code using an automated process
Centralized dedicated build server
Triggered automated build and test cycle, including tagging and versioning, every time a change is committed
A build will automatically fail if quality standards are not met in areas such as code analysis, security, performance, etc.
Broken Builds are fixed immediately
Build Metrics are gathered and made visible to all stakeholders
The team coaches other teams on advanced DevOps Build techniques
The team regularly discusses DevOps Build metrics and is consistently enhancing the DevOps Build process with automation
Thanks to the team’s success, influence, and commitment to knowledge sharing, the team’s advanced DevOps Build techniques been adopted throughout the enterprise and is considered a best practice supported by leadership