Can a single team deliver value?

Suppose you have a 3-tier system:

3 tiers, features aligned along tiers

When you deliver to your customers, is your work typically contained to a single tier? Or does the feature work tend to span tiers, so that it looks more look more like:

3 tiers, features aligned across tiers

If it looks like that, do you find things take longer than you want them to? Do you have frequent rework?

If you have a 3-tier system like above, you likely have separate teams for each tier. Front-end team? Back-end team? IoT team?

Do you notice what lies in the gaps?

3 tiers, features aligned across tiers, revealing handoffs.png

Handoffs–where hope, aspiration, and clarity go to die. No team is able to independently deliver value, and they’re going to be waiting on each other a lot.

Do your customers care about your tiers, or are they more interested in what you can deliver that makes their lives better?

If it’s the latter, why do your organize your development team structure around your tiers?


Like this message? I send out a short email each day to help software development leaders build organizations the deliver value. Join us!


Get the book!

Ready to learn how to build an autonomous, event-sourced microservices-based system? Practical Microservices is the hands-on guidance you've been looking for.

Roll up your sleeves and get ready to build Video Tutorials, the next-gen web-based learning platform. You'll build it as a collection of loosely-coupled autonomous services, developing a message store interface along the way.

When you're done, you'll be ready to contribute to microservices-based projects.

In ebook or in print.