Technical Advancement

Assessment Template Details

Lean Agile Intelligence

Technical Advancement

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 reflect and improve on the technical 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 advancing its agile technical practices.

Ideal for

This template is ideal for any team focused on advancing its agile 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

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)

Practice Technique Criteria Example

Team Agile Architecture

Starting

  • There is no holistic technology vision for the Product
  • Architecture is tightly coupled and difficult to change

Developing

  • A holistic technology vision exists for the Product 
  • The Product is organized into modules
  • APIs and libraries are leveraged
  • Spikes are leveraged to inform architectural decisions
  • Enterprise data and security policies are implemented

Emerging

  • Components exist with well-defined APIs and/or messages/events
  • Configuration as code (entire configuration stored as source code)
  • No or minimal branching
  • Deployment is considered during design

Adapting

  • Fine-grained domain-based services exist for critical business needs
  • The architecture of the Product is not dependent on the user interface
  • We coach other teams on advanced Agile Architecture techniques

Optimizing

  • Infrastructure as code
  • The architecture of the Product is not dependent on the database
  • The business rules 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 been adopted throughout the enterprise and is considered a best practice supported by leadership