DevOps Fundamentals

Assessment Template Details

Lean Agile Intelligence

DevOps Fundamentals

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. This template is ideal for any team focused on DevOps.

Ideal for

This template is ideal for any team focused on DevOps.

Source Reference

Works of thought leaders that influenced the Practice and associated Agility State Criteria Statements.

Go to Source Reference >

Questions/Practices by Practice Dimension

Value Driven

• Team Focus on Value

Dynamics

• Team Synergy

Quality

• DevOps Build Cycle
• DevOps Deploy & Config
• DevOps Monitoring
• DevOps Recovery
• DevOps Release
• DevOps Security
• DevOps Testing
• Team Agile Architecture
• Team Definition of Done

Adapt

• Team Flow of Value

Improve

• Team Learning Culture
• Team Retrospective

Leadership

• Team Leadership
• Team Self-Organization

Practice Technique Criteria Example

DevOps Build Cycle

Starting

  • The team has a manual and reactive build processes with little or no management of artifacts, source code, and reporting

Developing

  • 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

Emerging

  • Centralized dedicated build server 
  • Triggered automated build and test cycle, including tagging and versioning, every time a change is committed

Adapting

  • 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 

Optimizing

  • 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