A common answer to the success question on the podcast is “when I’m no longer needed”, but that isn’t a great career advancing answer. So we explore what happens after “I’m no longer needed”.
About Matthew Heusser
Matthew Heusser is the co-author of Save our Scrum, co-chair of the enterprise track at Agile2015, And he is also an author at CIO.com. Matt Software is a delivery consultant/writer and Collaborative software geek since before it was cool.
You can find Matthew Heusser on LinkedIn, and connect with Matthew Heusser on Twitter.
Strategy Maps: A diagram that creates clarity on what are the defined, but also real goals for an organization.
Design your coaching alliance: A method to help you, as a Scrum Master, understand what are the goals for your work with the teams, and to anchor your work on a clear vision and outcome.
Impact Mapping: a method to help you discover and understand what are the high-value work items (User Stories or Features) for your teams to work on. This tool alone will have a great impact on your work with Product Owners.
Value Stream Mapping: A way to analyse how the work is completed in an organization. Following the work from start to completion and creating a Value Stream Map of that work will give you insights into what are the impediments to value creation in your organization.
About Steve Hoyler
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.
If you are to help change it, you must reveal the system to the system itself. Dominic explains his approach to uncover the system conditions that block the team’s progress, as well as what he’s learned about how to create the right conditions for the teams to grow within their environment.
About Dominic Krimmer
Dominic has worked as a Software Developer since 2001, being a Scrum Master since 2009. He has collected many cool experiences in agile methods in different companies like CHIP, Sixt, mydriver.com and HolidayCheck. And has a small Kanban implementation at a manufacturing site in Latin America is also under his belt! 🙂 You can connect with Dominic Krimmer on twitter and visit Dominic Krimmer’s blog.