Maximilian Dazer: Fighting Conway’s law, an Agile story we all should learn

Max worked with a team that was composed of team members from two previous teams. As he joined in the role of the Scrum Master, he started noticing that the team members did not focus on collaboration, but rather on single, individually assigned tasks (listen in to learn about how you can detect if your team is falling prey to the same anti-pattern). This way of working was causing delays, and slowing down the team because of the many handovers necessary. In this episode, the Scrum Master can help the team understand the anti-pattern, and help teams get out of the silo-thinking. In this episode we refer to Conway’s Law, an empirical observation and statement by Mel Conway that helps us understand why organizations and software end up mirroring each other: “if you have a 3 team compiler organization, you end up with a 3-pass compiler”.

Featured Book of the Week: User Story Mapping by Jeff Patton

User Story Mapping by Jeff Patton helped Max understand many critical aspects of applying Agile to the requirements/definition of the product. He learned about how the Backlog could be different than a simple list of requirements/user stories, and how User Stories are meant to be used. 

Jeff Patton has been a previous guest on the Scrum Master Toolbox Podcast.

How can Angela (the Agile Coach) quickly build healthy relationships with the teams she’s supposed to help? What were the steps she followed to help the Breeze App team fight off the competition? Find out how Angela helped Naomi and the team go from “behind” to being ahead of Intuition Bank, by focusing on the people! Download the first 4 chapters of the BOOK for FREE while it is in Beta!

About Maximilian Dazer

Maximilian’s goal is to drive change from the bottom. For every team he creates a vision and tries to get them on board to pursue the change together. Maximilian wants to free people from the micromanagement-hell version of “scrum”.

You can link with Maximilian Dazer on LinkedIn.

BONUS: How to setup Agile and DevOps teams, Team Topologies interview with Matthew Skelton and Manuel Pais

Setting up teams to work collaboratively is one of the challenges that organizations go through when adopting Agile. The functional team setup (all DBAs, all testers, all windows devs together, etc.) is not acceptable for teams that want to quickly develop and deliver products and services to the market. But neither is it possible to have all possible skills (sometimes 10’s of skills) in one team because organizations simply don’t have that many people with certain skills. 

In this episode, we talk about the possible team topologies, and how each of those affects our ability to deliver in different organizations. 

How we set up teams directly affects the quality of the software teams deliver

Continue reading BONUS: How to setup Agile and DevOps teams, Team Topologies interview with Matthew Skelton and Manuel Pais