When looking at the systemic causes for problems we see in the team, we need to take into account many aspects: trust, metrics, conversations, relationships. Where to start? Richard suggests that we look at the Comparative Agile diagnostic and the Agile Fluency model and diagnostic. But of course, those are just starting points. A lot of the work needed to identify systemic problems is to listen to the conversations happening in the team, and with stakeholders. In this episode, Richard describes the process he uses to observe and analyze the conversations happening in the team, so that he can pinpoint systemic problems.
About Richard Kasperowski
Richard is a speaker, trainer, coach, and author focused on high-performance teams. Richard is the author of The Core Protocols: A Guide to Greatness. He leads clients in building great teams that get great results using the Core Protocols, Agile, and Open Space Technology. Richard created and teaches the class Agile Software Development at Harvard University. Learn more and subscribe to Richard’s newsletter at www.kasperowski.com.
You can link with Richard Kasperowski on LinkedIn and connect with Richard Kasperowski on Twitter.