We observe the system we work on every day. We even have many ideas on how the system could or should change for work to flow better, for people to feel better. However, without a form of visualizing the system we work with those are just fuzzy speculative ideas that may or may not matter in the end. Jeff walks us through his version of a Value Stream Map for knowledge work, and how that helps visualize and understand the system we work with. It is only then that we can start changing the system.
About Jeff Campbell
Jeff is an Agile Coach who considers the discovery of Agile and Lean to be one of the most defining moments of his life, and considers helping others to improve their working life not to simply be a job, but a social responsibility. As an Agile Coach, he has worked with driving Agile transformations in organisations both small and large. He is one of the founding members of www.scrumbeers.com and an organiser of www.brewingagile.org in his spare time. He is also the author of an open source book called Actionable Agile Tools, where he explains how he uses 15 of the tools he uses in his daily work as a scrum master and agile coach.
You can link with Jeff Campbell on LinkedIn, and connect with Jeff Campbell on Twitter.
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.
When we introduce visualization methods in an already dysfunctional organization, there’s a tendency to see problems and point at the guilty parts. However, our dysfunctional processes are the result of the system conditions, not the people in the system. Marcus reminds us of that fact and asks us to hate the sin, not the sinner. He also shares a great tip to get started with visualizing the work in progress.
Marcus shared with us a discount code for all that purchase his book until October 14th, 2015. Don’t miss it, purchase the book at http://bit.ly/theKanbanBook, and use the code scrumkan.
Visual management is a key practice for continuous improvement, in this episode Sven explains how he uses visual management practices to help detect, understand and ultimately solve system problems. This is an episode filled with valuable tips for systems thinkers that want to go beyond helping the Scrum team.
About Sven Schnee
Sven started his journey as a developer around the year 2000. He experienced many projects and felt the pain of how traditional approaches to software development failed.
A few years ago he discovered Agile and Lean, and he is not going back.
He is an Agile Coach and Founder of Oikosofy. He wants to bring agile ways of working to a variety of customers from small companies to big enterprises. One of his key strengths is helping teams evolve on their path to self-organization.
You can connect with Sven Schnee on twitter, and link with Sven Schnee on LinkedIn.
You can read Sven Schnee’s blog The Product Owner Toolbox.
Marc explains the story of a team that was starting their Scrum adoption and allowed a project manager to use their tool, the Scrum board, as a tool for micro-management. From that a lot of anti-patterns emerge that Marc struggled with. We also discuss the use of tools for planning vs. using the same tools to generate collaboration and how to switch the focus from planning to collaboration.
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.