You're reading from Becoming an Agile Software Architect Strategies, practices, and patterns to help architects design continually evolving solutions

Product type Paperback

Published in Mar 2021

Publisher Packt

ISBN-13 9781800563841

Length 372 pages

Edition 1st Edition

Tools

JIRA

Concepts

Agile

Author (1):

Rajesh R V

View More author details

Table of Contents (19) Chapters

Preface

1. Section 1: Understanding Architecture in the Agile World

2. Chapter 1: Looking through the Agile Architect's Lens FREE CHAPTER

3. Chapter 2: Agile Architecture – The Foundation of Agile Delivery

4. Section 2: Transformation of Architect Roles in Agile

5. Chapter 3: Agile Architect – The Linchpin of Success

6. Chapter 4: Agile Enterprise Architect – Connecting Strategy to Code

7. Chapter 5: Agile Solution Architect – Designing Continuously Evolving Systems

8. Section 3: Essential Knowledge to Become a Successful Agile Architect

9. Chapter 6: Delivering Value with New Ways of Working

10. Chapter 7: Technical Agility with Patterns and Techniques

11. Chapter 8: DevOps and Continuous Delivery to Accelerate Flow

12. Chapter 9: Architecting for Quality with Quality Attributes

13. Chapter 10: Lean Documentation through Collaboration

14. Chapter 11: Architect as an Enabler in Lean-Agile Governance

15. Section 4: Personality Traits and Organizational Influence

16. Chapter 12: Architecting Organizational Agility

17. Chapter 13: Culture and Leadership Traits

18. Other Books You May Enjoy

Structuring teams within flow teams

Flow teams are autonomous and are as big as 100 people. To operate effectively and efficiently, flow teams need an internal structure. Different strategies can be used for structuring teams within flow teams.

The primary principle is to create sub-flow teams within flow teams, but this time the flow is at the feature level. The following diagram captures three different possibilities of feature-based team structuring:

Figure 12.24 – Compositions of feature-based teams

As shown in the diagram, a feature can span across multiple systems, be within a system, or span across modules of a system. In this context, a feature is a set of continuously evolving requirements. For example, in a tour booking scenario, payment, search, and booking are long-lasting and evolving features. A stable, fixed-capacity team is required to develop and maintain those features. A flow team may have a mix of teams such as feature teams spanning...