Technical Agility

Assessment Template Details

Lean Agile Intelligence

Technical Agility

This template focuses on the cutting-edge technical practices that enable teams to build quality into their application, making it more reliable. Influenced by many Agile technical thought leaders, this template provides teams with an opportunity to measure and improve on technical practices such as Pair Programming, TDD, Safe DevOps, and BDD assessment.

Ideal For

Any team focused on advancing its agile technical practices.

References

Works of thought leaders that influenced the Growth Criteria, assigned Stage, and associated Business Outcomes.

Go to References >

Questions by Dimension

21 total questions

Quality

• Collective Code Ownership
• Dependency Inversion Principle
• DevOps Build Cycle
• DevOps Deploy & Config
• DevOps Monitoring
• DevOps Recovery
• DevOps Release
• DevOps Reporting
• DevOps Security
• DevOps Testing
• Health of Codebase
• Incremental Design
• Interface Segregation Principle
• Open/Closed Principle
• Pair Programming
• Single Responsibility Principle
• Team Agile Architecture
• Team Definition of Done
• Team Definition of Ready
• Team Focus on Quality
• Test-First Programming (TDD)

Question Growth Criteria Example

Team Agile Architecture

Starting (0)

There is a lack of clarity on the holistic technology vision for the team's product(s)

The UI, frameworks, and databases of the team's product(s) is mostly tightly coupled with the business rules, and difficult to change

Developing (1)

A holistic technology vision exists for the team's product(s)

The team's product(s) are organized into modules

The team's product(s) leverage APIs and libraries

Enterprise data and security policies are implemented in the team's product(s)

Emerging (2)

Spikes are leveraged to inform architectural decisions for the team's product(s)

The team's product(s) contains components with well-defined APIs and/or messages/events

The team's product(s) utilizes configuration as code (entire configuration stored as source code)

The team uses no or minimal branching for their product(s)

The team considers deployment during design of their product(s)

Adapting (3)

The team's product(s) have fine-grained domain-based services for critical business needs

The architecture of the team product(s) is not dependent on the user interface

The team's product(s) utilizes infrastructure as code

The team coaches other teams on advanced Agile Architecture techniques

Optimizing (4)

The architecture of the team's product(s) is not dependent on the database

The business rules of the team product(s) can be tested independently of UI, database, or any other external elements

Thanks to the team’s success, influence, and commitment to knowledge sharing, the team’s advanced Agile Architecture techniques have been adopted throughout the enterprise and is considered a best practice supported by leadership