Natalie explains her approach to understanding and visualizing the system conditions that affect the teams she works with:
Start by asking “how are the tools, practices and policies affecting the team’s I work with?”
Then take a pen and draw the links between the different observations, do this with the whole team. Expect to hear many different perspectives, and help the team make sense of those different views.
Use also metrics, but not just one. Look at several metrics and ask people to look beyond a single metric, and beyond the metrics. What do these metrics tell us?
Identify possible underlying conditions that affect the team.
Always keep in mind, that this process will be different for every team you work with, each team is different.
About Natalie Warnert
As a developer turned Agile coach, Natalie Warnert understands and embraces what it takes to build great products. Natalie focuses teams on embracing Agile values to build the right product and build the product right. Natalie is currently coaching the Cart/Checkout teams for Best Buy Dotcom and recently earned her Master of Arts degree in Organizational Leadership and Strategic Management.
You can link with Natalie Warnert on LinkedIn, connect with Natalie Warnert on Twitter, read her blog at nataliewarnert.com, and visit her project page Women in Agile.
Understanding the system we work within is a detailed and painstaking process of collecting and processing information. There are many questions we must ask as we collect that information. Gil shares with us the questions he asks to collect the right information about the system, and map the system conditions that affect the team.
In this episode we discuss Theory of Constraints, a body of knowledge that every Scrum Master should be aware of.
About Gil Zilberfeld
For over 20 years, Gil has developed, tested, managed and designed software products. He’s gone through failures and successes, in different types of projects and companies.
He has trained and coached developers how to write tests for their untestable code. He has worked with testers on complex applications and with very tight deadlines. He’s helped release products that fit customer needs, by testing the waters, and getting their feedback integrated. He has implemented agile, kanban and lean principles and adapted them to fit teams better.
You can link up with Gil Zilberfeld on LinkedIn, or find Gil Zilberfeld on Twitter. Gil is writing a book on Unit Testing. Check it out.
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
Whether you use the Lean Waste approach, Dan Pink’s autonomy-mastery-purpose or any other model what is important is that you use some models to understand the system that affects the team’s performance. Sebastian shares several models that you can use to assess and measure those system conditions that many of us forget to take into account. This episode also includes a long reading list:
Sebastian has an extremely strong work ethic, a great passion to his work, unwavering desire for excellence, and unabated willingness to share his rich knowledge.
Driven by his strong work ethic, he takes several key roles: as scrum master, agile coach, mentor, as protector of the young development teams, after all, a humble leader who takes risks and responsibilities at extremely critical moments, creates a vision which the other follow by heart – with excellent outcome.
You can find Sebastian Schürmann on twitter, and link with Sebastian Schürmann on LinkedIn.
You can find Sebastian Schürmann’s website, and his blog.
Wayde has worked with many teams, and in this episode he describes the aspects of the system conditions that affect team’s performance. Those system conditions are not the ones you would expect to hear about. The fact is that we work with people, and people make up the system we are part of, in the end it is all much more touchy feely than we would like to accept.
Peter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.