Scrum with component teams leads to Waterfall Agile!

This infographic presents the perils of Scrum with component teams. It pushes organizations back in Waterfall Agile, late deliveries and non-sustainable work.

By Philippe Bourgau, under CC BY-SA 4.0, high resolution image

Takeaway

A small ratio of component teams is not necessary bad. When features involve many component teams though, we’re in painful integration and Waterfall. If this is your case, you’d rather rethink your teams organization. Here are 2 strategies:

• Big Picture Event Storming can help you to pick the right team organization
• Continuous improvement and coaching can get your teams to reorganize step by step

During this summer, I’ll post a few similar infographics. Next one is How to play planning poker… Badass Mode!

Stay up to date with content and upcoming products

I usually write about 15 minutes worth of reading per month. I won't transfer your email. No Spam, unsubscribe whenever you want.

As a gift for subscribing, you'll receive an illustrated mini-ebook "How to start a team coding dojo"!