Team Topologies for Delivery
A focused chapter on team topologies for delivery, with practical delivery concerns, trade-offs, and the operational questions behind CI/CD work.
Why Team Structure Determines Your Delivery Speed
Imagine a team responsible for shipping a new feature to an application used by thousands of people. The team has a backend developer, a frontend
When Your Team Owns the Whole Journey: Stream-Aligned Teams and Delivery
Picture this: your team wants to add a new filter to the search feature in your e-commerce app. You have the design ready, the code written, and the tests
Why Letting Every Team Build Their Own Pipeline Backfires
Imagine this: your organization has five stream-aligned teams. Each team builds its own CI/CD pipeline from scratch. One team picks Jenkins, another goes
Helping Teams Get Better Without Becoming Their Crutch
A stream-aligned team is building a new feature. The code works. The tests pass locally. But when they look at the pipeline, they realize they need to add
When a Feature Team Should Not Touch the Code: The Case for a Complicated-Subsystem Team
Your team is building an e-commerce platform. You own the checkout flow, the product catalog, and the user profile page. Everything is going well until
Three Ways Teams Work Together Without Creating Bottlenecks
You have a platform team that built a great CI/CD pipeline. A stream-aligned team needs to use it. But instead of just running their deployments, they
When Your Team Model Stops Helping Delivery
You have three teams building features. Each team set up their own pipeline. Each team manages their own environments. Each team has their own way of