Scrum Plus DevOps

Assessment Template Details

Lean Agile Intelligence

Scrum Plus DevOps

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. Various processes, techniques, and methods can be employed within the framework, such as DevOps. This template focuses on the practices and characteristics of a high-performing Scrum team that compliments the framework with DevOps technical practices. Influenced by many Scrum and DevOps thought leaders and the recent version of the Scrum Guide (2020), this template provides an opportunity for Scrum teams to reflect and improve on the behaviors, qualities, and practices required of a high-performing Scrum team in today’s fast-moving business environments. This template is ideal for new and seasoned Scrum teams using DevOps technical practices.

Ideal for

This template is ideal for new and seasoned Scrum teams using DevOps technical practices.

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 Backlog Refinement
• Team Product Backlog
• Team Product Owner


• Team Accountability
• Team Safety
• Team Synergy


• DevOps Build Cycle
• DevOps Deploy & Config
• DevOps Release
• DevOps Testing
• Team Agile Architecture
• Team Definition of Done
• Team Focus on Quality


• Scrum Team
• Team Daily Stand-Up
• Team Sprint
• Team Sprint Planning
• Team Sprint Review


• Team Retrospective


• Team Scrum Master

Practice Technique Criteria Example

Team Focus on Quality


  • Quality is an afterthought; the team only worries about it in the end


  • The team has a whole-team view towards quality where everyone is responsible for it
  • The team has dedicated QA-skilled people that are responsible for acceptance testing
  • "Acceptance Testing Completed" is part of the Definition of Done for PBIs completed in an iteration (i.e., Sprint)
  • Developers write unit tests as part of story development


  • Testers are actively involved in writing PBIs
  • The team has quality standards beyond the Definition of Done such as checklists, templates, and test case repositories
  • Others will chip in on testing when QA is overloaded
  • Refactoring technical debt is required when making changes to an outdated piece of code
  • The team considers non-functional requirements from the very beginning of the Product


  • The team has a pyramid-based test strategy that is baked into their team's Definition of Done; it includes unit tests, integration tests, acceptance tests, and UI tests
  • The team is experimenting with ATDD and BDD
  • The team coaches other teams on advanced Quality techniques


  • The team actively practices ATDD and BDD
  • Thanks to the team’s success, influence, and commitment to knowledge sharing, the team’s advanced Quality techniques been adopted throughout the enterprise and is considered a best practice supported by leadership