Multi-Team Agile Effort - Ways of Working

Assessment Template Details

Lean Agile Intelligence

Multi-Team Agile Effort - Ways of Working

This template focuses on the best practices and characteristics of a high-performing Multi-Team Agile effort. Influenced by many Agile & Lean thought leaders, this template provides an opportunity for Multi-Team Effort leadership and/or participants to reflect and improve on the behaviors, qualities, and practices required of a high-performing Multi-Team Agile effort in today’s fast-moving business environments. This template is ideal for a Multi-Team Agile Effort already accustomed to working in an Agile way at scale and want to improve their practices to optimize the benefits of Agile.

Ideal For

Cross-functional leaders of a multi-team product, program, or value stream.

References

Works of thought leaders that influenced the Practice's Technique Criteria, assigned Agility Stage, and impacted Business Outcomes.

Go to References >

Questions/Practices by Practice Dimension

26 total practices

Value Driven

• Multi-Team Backlog Refinement
• Multi-Team Envisioning & Ideation
• Multi-Team Focus on Value
• Multi-Team Product Backlog
• Multi-Team Product Leadership

Dynamics

• Multi-Team Accountability
• Multi-Team Safety
• Multi-Team Synergy

Quality

• Multi-Team Agile Architecture
• Multi-Team DevOps
• Multi-Team Focus on Quality
• Multi-Team Technical Enablers

Adapt

• Multi-Team Cadence
• Multi-Team Composition
• Multi-Team Demo
• Multi-Team Flow of Value
• Multi-Team Release Plan
• Multi-Team Roadmap
• Multi-Team Stand-Up
• Multi-Team Sustainable Pace

Improve

• Multi-Team Learning Culture
• Multi-Team Metrics
• Multi-Team Retrospectives

Leadership

• Multi-Team Lead Facilitator
• Multi-Team Leadership
• Multi-Team Self-Organization

Practice Technique Criteria Example

Multi-Team DevOps

Starting (0)
  • No application monitoring
  • The Multi-Team Effort builds, tests, and releases manually
  • Operations and Development are two different silos
  • Environment inconsistencies exist all over the place 
Developing (1)
  • The Multi-Team Effort has a centralized dedicated build server for widely-used/high volume product(s)
  • An automated build is triggered every commit for the widely-used/high volume product(s)
  • Unit tests are written as part of story development for widely-used/high volume product(s)
  • Application health is monitored and managed for widely-used/high volume product(s)
  • Operations and development teams of the Multi-Team Effort collaborate to manage risk and touchpoints when they need to
Emerging (2)
  • Issues flagged by application health monitoring of widely-used/high volume product(s) are immediately acted upon 
  • Unit Tests are triggered every commit for widely-used/high volume product(s), and issues are addressed immediately
  • Automated releases for widely-used/high volume product(s), including data migrations, can be deployed across multiple environments with one-click deploy
  • Operations and development teams of the Multi-Team Effort regularly collaborate to manage risk and touchpoints
Adapting (3)
  • Automated acceptance tests are written as part of story development for widely-used/high volume product(s)
  • Automated acceptance tests for core features of widely-used/high volume product(s) are triggered during the build process
  • Automated test suites enforce a quality gate requirement for widely-used/high volume product(s)
  • Automated security testing exists for widely-used/high volume product(s)
  • Automated performance testing exists for widely-used/high volume product(s)
  • Contributors to the Multi-Team Effort coach other Multi-Team Efforts on advanced DevOps techniques
Optimizing (4)
  • Automated acceptance tests for all features  of widely-used/high volume product(s) are  triggered during the build process
  • The Multi-Team Effort consists of both development and operations people that are responsible for the product all the way to production
  • Thanks to the Multi-Team Effort’s success, influence, and commitment to knowledge sharing, their advanced DevOps techniques have been adopted throughout the enterprise and is considered a best practice supported by leadership