conway's law Archives - Scrum Master Toolbox Podcast

BONUS: From Waterfall to Flow—Rethinking Mental Models in Software Delivery With Henrik Mårtensson

In this BONUS episode, we explore the origins and persistence of waterfall methodology in software development with management consultant Henrik Mårtensson. Based on an article where he details the history of Waterfall, Henrik explains the historical context of waterfall, challenges the mental models that keep it alive in modern organizations, and offers insights into how systems thinking can transform our approach to software delivery. This conversation is essential for anyone looking to understand why outdated methodologies persist and how to move toward more effective approaches to software development.

The True Origins of Waterfall

“Waterfall came from the SAGE project, the first large software project in history, where they came up with a methodology based on an economic analysis.”

Henrik takes us on a fascinating historical journey to uncover the true origins of waterfall methodology. Contrary to popular belief, the waterfall approach wasn’t invented by Winston Royce but emerged from the SAGE project in the 1950s. Bennington published the original paper outlining this approach, while it was Bell and Tayer who later named it “waterfall” when referencing Royce’s work. Henrik explains how gated process models eventually led to the formalized waterfall methodology and points out that an entire generation of methods existed between waterfall and modern Agile approaches that are often overlooked in the conversation.

In this segment we refer to:

- The paper titled “Production of Large Computer Programs” by Herbert D. Benington (direct PDF link) Updated and re-published in 1983 in Annals of the History of Computing ( Volume: 5, Issue: 4, Oct.-Dec. 1983)
- Winston Royce’s paper from 1970 that erroneously is given the source of the waterfall term. Direct PDF Link.
- Bell and Thayer’s paper “Software Requirements: Are They Really A Problem?”, that finally “baptized” the waterfall process. Direct PDF link

Mental Models That Keep Us Stuck

“Fredrik Taylor’s model of work missed the concept of a system, leading us to equate busyness with productivity.”

Continue reading BONUS: From Waterfall to Flow—Rethinking Mental Models in Software Delivery With Henrik Mårtensson

BONUS: Maria Chec Explores the Divide Between Agile Leaders and Practitioners

In this BONUS episode, we explore Agile leadership with Maria Chec, author and host of Agile State of Mind. Maria shares insights from her analysis of Miro’s Agile Survey, revealing a concerning disconnect between how Agile leaders and practitioners experience agile methodologies. We explore the roots of this divide, discuss practical approaches to bridging the gap, and consider the implications of recent industry developments like the PMI-Agile Alliance merger. Maria offers valuable perspectives on creating truly collaborative environments where frameworks serve the teams, not the other way around.

The Disconnect Between Leaders and Practitioners

“Practitioners feel pressured to comply with agile practices when they don’t seem to add value.”

Maria highlights a stark divide revealed in Miro’s survey of 1,200 agile practitioners and leaders. When asked if agile is living up to its original values, leaders and practitioners gave drastically different responses. For example, 69% of practitioners felt processes and tools overshadow individuals in their organizations, while only 43% of leaders shared this view. Similarly, 58% of practitioners believed documentation was prioritized over delivering final products, compared to just 39% of leaders. These disparities point to a fundamental disconnect in how agile is experienced at different organizational levels, with practitioners often feeling frameworks are imposed rather than collaboratively implemented.

When Frameworks Become the Problem

“The framework is too rigid… The framework is too complex… We have to change too much to use the framework.” Continue reading BONUS: Maria Chec Explores the Divide Between Agile Leaders and Practitioners

Mateusz Komander: Scaling with Purpose, Managing Agile Team Growth While Avoiding Conway’s Law Pitfalls

Mateusz shares a compelling story about scaling an application development team that started small but grew rapidly. The team implemented a Flight Levels system, breaking into smaller groups of four people maximum to maintain focus and efficiency.

While this approach initially showed promising results, it eventually led to unexpected challenges as teams began forming silos around architectural layers, exemplifying Conway’s Law in action. This experience highlighted the importance of carefully managing team identities and considering platform team approaches when scaling.

Self-reflection Question: How can you maintain cross-functional collaboration when scaling teams while preventing natural tendencies toward technical silos?

The Scrum Master Toolbox Podcast Recommends…

🔥 In the ruthless world of fintech, success isn’t just about innovation—it’s about coaching! 🔥

Angela thought she was just there to coach a team. But now, she’s caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn’t just about the product—it’s about the people.

🚨 Will Angela’s coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

The Scrum Master Toolbox Podcast Recommends…

About Mateusz Komander

Mateusz, is a Scrum Master at Heineken, and brings expertise from biotech and airline industries, excelling in Agile delivery and transformations. Skilled in Management 3.0, he fosters self-managed, innovative teams. Mateusz just launched a podcast on organizational transformation, Mateusz highlights how understanding team dynamics beyond the Scrum framework enhances collaboration and effectiveness.

You can link with Mateusz Komander on LinkedIn.

BONUS: Rediscovering Agile’s Roots, What We Can Learn From Lean Manufacturing with Doug Rabow

In this BONUS episode, we reconnect with Doug Rabow, a previous guest and an expert in Lean-Agile strategic management known for his dedication to fostering empowered teams and enhancing processes through Lean principles. This discussion dives into the foundations of Lean, its evolution from manufacturing, and how software development can benefit from these time-tested methodologies. Join us as we uncover how adopting Lean can transform software practices and culture to align more closely with the true spirit of Agile.

Introduction to Lean and the Toyota Production System (TPS)

“Lean isn’t just a methodology; it’s an ongoing journey of learning and problem-solving.”

Doug begins by mapping out the origins of Lean and its cornerstone, the Toyota Production System (TPS) (Wikipedia article on TPS). Initially crafted to solve operational challenges in manufacturing, TPS introduced principles aimed at efficiency and continual improvement. Doug underscores that while Agile has gained broader recognition, Lean provides an essential, often overlooked foundation that extends beyond frameworks like Lean Six Sigma or isolated process improvements.

“Lean isn’t a set-and-forget solution; it’s about cultivating an evolving culture of problem-solving.”

Cultural Foundations of Lean: Adapting for Software Teams

Continue reading BONUS: Rediscovering Agile’s Roots, What We Can Learn From Lean Manufacturing with Doug Rabow

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.