Zach Bonaker on discusses his views on some Systems Thinking tools

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.

Zach Bonaker on the 3 successful outcomes for Scrum Masters

In this episode, Zach Bonaker explains the three outcomes he thinks are critical for Scrum Masters.

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.

Zach Bonaker explains the role of narrative in change management

There are many tools that can help us in a process of change. The book Lean Change Management by Jason Little lists many of those in the context of a real story about change. In this episode Zach describes some of those tools and how to use then in our roles as Scrum Masters. We also mention the book Nonviolent Communication by Rosenberg.

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.

Zach Bonaker on how pressure to perform can destroy a team

We all want to be successful, to have an impact in the lives of the people around us. Teams have the same needs. However, when we increase the pressure on a team that is in trouble we create the conditions that may lead to that team’s implosion.

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.

Zach Bonaker on Apprenticeship for Scrum Masters

Zach shares his journey as a Scrum Master and how important it is to get a pair in your own journey. Apprenticeship for Scrum Masters is not a new idea, but it is an important part in our toolbox for learning as Scrum Masters.

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.

Dennis Mansell talks about two important parts of the system – System Health and System Productivity

In this episode Dennis explains the difference between two tools that he uses at the organizations he works with. He explains how he uses these tools to measure System Health and System Productivity.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell explains how happiness index can be a useful measure to define Scrum Master success

Dennis tells us how he uses a technique known by Henrik Kniberg – happiness index in his daily work. He also explains how important it is to understand what people inside of the team say; he believes that part of a Scrum Master role is to create a good environment within the team. If there are many things being said in a negative way the Scrum Master has a lot of things to do in order to improve the team performance.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell talks how it is important for a Scrum Master to create an environment where change happens even without the presence of the Scrum Master

Dennis tells us a very interesting story from his sailing activities. He explains to our audience how it is important to build an environment of collaboration and most importantly an environment where “things” happen even if the most important persons in the team are not present.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell talks how a semi destructive team is even worse than a complete destructive team

Dennis discusses that most of the times when we start to work as a team, we simply put people together expecting that everything will work. We even forget to ask if people do actually want to work together. In this episode he explains how that can go wrong.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell tells us how you can be fired for not spending all the project budget

Dennis explains us how most of his learnings came from failures. In his story he explains how he lost a project because he spent only 10% of the total budget. As an outcome, spending just this small part of the budget led Dennis to loose his job.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.