Pratik Dahule: Helping an Agile team that is stuck in the skill silo, which created chaos at the end of the sprint

Often, developers want to work on their stories until the last day of the sprint. However, that leads to many problems which we explore in this episode. We learn the story of a team that was clearly divided in skill silos, which led to a lot of chaos at the end of the sprint. When faced with this tricky situation, Pratik started to help the team understand the anti-pattern they were in, and using tools like cause-and-effect diagrams (aka Ishikawa Diagrams), he helped the team understand and get out of this anti-pattern.

Featured Book of the Week: Slight Edge by Jeff Olson

In Slight Edge by Jeff Olson, Pratik learned an approach that helps him make daily choices and be consistent in applying what he’s learned in his career. This approach has helped him accept that we must do things over and over again, if we aim to succeed in being a great Scrum Master and other areas of life.

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 Pratik Dahule

Pratik is an Agile Project Manager and Agile enthusiast working in the USA. He leads teams and creates a culture of lifelong learning, constant collaboration and continuous improvement. Pratik has 12 years of experience and is passionate about helping teams in their agile transformation. Outside of work, he has a blogging site where he shares insights on books and exotic places to travel.

You can link with Pratik Dahule on LinkedIn.

Marc Löffler on Causal Loop Diagram and other systems thinking tools

There are many tools that we can use, just like Causal Loop Diagram, to help us understand the deeper dynamics in our organizations. We discuss several of those tools and also how to use them. Finally, Marc introduces his book Retrospektiven in der Praxis: Veränderungsprozesse in IT-Unternehmen effektiv begleiten and why he wrote it. NOTE: the book will be available in English in the near future.
We also mention a systems thinking tool called Current Reality Tree that you can use to investigate the system you work within.

About Marc Löffler

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.

Antti Tevanlinna shares his tools to understand and change the system

Understand and change the system is perhaps one of the major challenges for Scrum Masters all over the world. In this episode Antti shares his favourite tools for that exact task:

  • Measure Lead Time, and how each action affects that metric. Use that metric to detect problems in how the system works at all times.
  • Create causal loop diagrams that help you understand what are the many effects, and causes in play within the organization.
    Both of the tools mentioned are part of an arsenal of tools that you can find when studying Systems Thinking. To get you started, Antti recommends the book The V Discipline by Peter Senge.

About Antti Tevanlinna

scrum_master_toolbox_podcast_Andy_Deighton Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.