Dennis Wagner maps the system, by mapping the stakeholders and their expectations

How do we get started mapping the system conditions we must face every day? Dennis suggests that you understand the stakeholders that the team needs to interact with. By understanding the map of the system you can then dig deeper with Expectation Mapping to understand what the team is expected to deliver to all those stakeholders. This will help you map the key system conditions. Use also visualization to understand how those other stakeholders interact among themselves and use Circles of Influence to understand what the team can affect on its own, and what they need help with.

About Dennis Wagner

Dennis is an Agile Coach with a lot of experience in the technical side of software development. Dennis has worked with teams in different industries, is thinking of writing a book about continuous delivery (bug him if you want to know more), and he loves, really loves his work.
You can connect with Dennis Wagner on LinkedIn and XING, and you can connect with Dennis Wagner on Twitter.

Dennis Wagner: Sometimes the Scrum Master is the Impediment

We become Scrum Masters because we want to help teams, organizations, and ourselves to make a difference in the world, to create better working places. However, sometimes we want that too much. Dennis explains one such case and a key lesson he learned.
We also refer to Don Reinertsen’s book The Principles of Product Development Flow: Second Generation Lean Product Development. We discuss a tool that you can use to manage expectations with the teams you work with: Expectation Mapping.

About Dennis Wagner

Dennis is an Agile Coach with a lot of experience in the technical side of software development. Dennis has worked with teams in different industries, is thinking of writing a book about continuous delivery (bug him if you want to know more), and he loves, really loves his work.
You can connect with Dennis Wagner on LinkedIn and XING, and you can connect with Dennis Wagner on Twitter.