How can we detect the system conditions that affect our teams? Daniel has a method, that he explains in this episode. This includes writing down keywords you listen during the day, and looking for patterns in those keywords. Daniel also suggests that you look at the Agile Fluency model to look for indicators that your team is evolving, or not.
Special call to all Dubai agilists: Daniel is relocating to Dubai and is looking to connect to local agilists. If you fit the bill, then reach out to him on twitter: Daniel Nielsen on Twitter.
About Daniel Nielsen
Daniel is a developer turned Scrum Master turned Agile Coach, with an increasing focus on the coach part. Over the last 10+ years, his interest in how teams work and how we interact as individuals has only grown. He has worked in both small and large companies and tried to cope with the complexities in both worlds.
You can reach out to Daniel Nielsen on Twitter, and link with Daniel Nielsen on LinkedIn.
You can also read his blog in Danish at QED.dk
Steve Holyer serves as advocate, trainer and mentor for companies looking for a better ways of working, using Agile practices in a productive, fulfilling, and fun way.
He learned his craft serving as a Scrum Master with multiple teams and organisations, so he knows how to change an organisation from the inside. Steve now serves as an indie-label Agile Coach-for-Hire. He’s passion lies with coaching managers and teams to find ways to do software better.
You can contact Steve Hoyler on twitter, and find Steve Hoyler on LinkedIn. For more, check his Lift Off workshop.