In this episode we review several systems thinking tools with Zach and discuss their applicability to situations we all face as Scrum Masters. We mention Cynefin as one of the models that can help us wrap our heads around the complex environment we work within.
About Zach Bonaker
Zach Bonaker is Benevolent Trouble-Maker from San Diego. He’s an agile coach who specializes in bringing lean thinking to organizations and teams over varying sizes across the country. Zach builds relationships to help transform people, systems, and structures towards safer and faster ways of delivering high quality software. When he isn’t thinking about next-generation agile ideas, Zach can be found enjoying the sunny west coast weather and connecting with people all around the world. Follow Zach Bonaker on Twitter, and connect with Zach Bonaker on Linkedin.
When we start working with a team, we don’t actually work with that team. That team is part of a larger system, and we must understand the system before we can help the team. Amitai uses ideas from Theory of Constraints, and mentions The Goal, by Goldratt as a foundational book in his own journey as a Scrum Master. He also shares with us Schmoz’s theory, a critical insight when we work with and within human systems. Today we play one more Agile in 3 Minutes episode which describes how we can reach freedom in our work. Today’s Agile in 3 minutes episode is episode #12, titled “Free”.
About Amitai Schlair
Amitai is a Software development coach, and legacy code wrestler, non-award-winning musician, award-winning bad poet, and creator of Agile in 3 Minutes, which is a great podcast about what Agile really is about. A must listen for anyone interested in Agile Software Development. You can link with Amitai Schlair on LinkedIn and connect with Amitai Schlair on Twitter.
There are many sources of inspiration that help us understand how to “see” the system. Daniel mentions the Logical Thinking Process by Dettmer, and The Goal by Goldratt as good places to start understanding the system and how to address it. But the real tool we all already use and can have a large impact on our understanding and influence is the Retrospective meeting. Daniel suggest the Circles and Soup Retrospective as a way to help the team understand the system and act on it.
About Daniel Hommel
Daniel is a ScrumMaster and Agile Coach with a strong background in Software Engineering. His first touch point with Agility was starting to use the Extreme Programming practices in 2007. After some years of working more on the technical side in recent years his interest has shifted to facilitation, coaching, guiding continuous improvement and working with people in general. You can connect with Daniel Hommel on Twitter.
Marc’s passion is to help teams implementing agile frameworks like Scrum and XP and to transform our world of work. Marc loves to help teams, that are struggling with agile transitions, to overcome dysfunctional behaviour. He loves to generate new insights by approaching common problems from the other side and trying to deliberately make havoc of the process. You can connect with Marc Löffler on Twitter, and link with Marc Löffler on LinkedIn. He hosts a Blog in English and another blog in German.
Software development is not the same as building a road, or building a house. There’s a key concept called Complexity that explains why many of our assumptions of how software development happens are false. Stefano explains his views of how we can understand the performance of the team in the context of the performance of the whole organization and what to do about it.
In this episode, Stefano refers to Polarity Management, a way of looking at the role of management that can significantly increase the performance of the organization. For more, read this page on Polarity Management.
About Stefano Porro
Stefano is from Turin, Italy. He has worked since 2001 in IT projects and he feels lucky because he does what he loves. He learned about Scrum in 2007 when the company where he was working decided to adopt Scrum. For the first two years he was part of a Scrum team, and he was fascinated from the role of the Scrum Master because he always loved to help team’s members. For him, becoming a Scrum Master, was a natural evolution.