There are many paths to starting our journey as a Scrum Master. Zuzi started as a line manager, but she soon learned the key differences between being a team leader and being a Scrum Master. She also explains why some companies still fail to improve, even when using Scrum.
About Zuzi Sochova
Zuzi help companies and individuals to be more successful. She teaches teams and their managers how to be more efficient, how to provide better quality and how to communicate and organize teams so that people have fun, they are motivated and have high commitment. Zuzi helps teams and managers find out how to handle customer relationship to help them improve customer satisfaction.
You can visit Zuzi’s website at: http://sochova.cz/, and link with Zuzi Sochova on LinkedIn, or connect with Zuzi Sochova on twitter, or your favorite conferece.
There are many learnings we collect along our journey as Scrum Masters. However, transformative lessons are not that common, except for Jeff in this particular job. Listen how he learned 2 lessons that totally changed how he looks at his job as a Scrum Master.
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.
To define success for us as Scrum Masters we need to define also what it means not to succeed. Dennis defines what is failure, and uses 2 concrete tools to check the situation all the time. The tools are 5 Why’s and a simple powerful question: “how are we succeeding?”
Each of these tools tackles a different purpose that Dennis explains in this episode.
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.
Sometimes it is hard to focus on what to improve. Juha tells us: when you can’t do what you want, do something else instead. You can only teach people what they are ready to learn, and you cannot force anyone to learn anything.
We also discuss the lessons from Dale Carnegie’s How to Win Friends and Influence People, a must-read for all Scrum Masters.
About Juha Heimonen
Juha is a entrepreneur, programmer, kanbanista and a unicorn. He calls Software a garden, and says that he tries to be a gardener tending the soil as well as the specific plants.
He is active in the local agile community in Jyväskylä, Finland and also quite active on twitter.
You can link up with Juha Heimonen on LinkedIn and connect with Juha Heimonen on twitter.
You can find out more about his thoughts on Fellowship and how he applies that in his own business at Flowa’s website and blog.
Working with a well-versed distributed team is not an easy task for a Scrum Master, but transitioning a team from co-located to distributed? That’s even harder. Daniel explains what he learned as a Scrum Master when he was faced with just that situation.
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
There are many failures in the career of all successful Scrum Masters, and Sebastian shares with us 4 major failures that helped him develop his craft as a Scrum Master.
Being a Scrum Master is a discipline in itself, and we must learn that discipline by focusing on the contribution of that discipline to the team and the organization.
About Sebastian Schürmann
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.
How can we help teams learn as Scrum Masters? What fails when they don’t? And what is the role of ceremonies like the retrospectives in Scrum? These and other questions are tackled in this episode. Stephen also discusses how the search for control can actually have a negative impact on the success of the team.
About Stephen Thomas
Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.
Product Owners are often given that role because of what they know, but Scrum requires that Product Owners be available to the team. If they are not available that will create problems for the team.
Assigning a Business Analyst as a Product Owner may not be the right choice, especially if that Business Analyst is used to writing requirements “the old way”.
Listen to the podcast for Peter’s experience and insights on the problem.
About Peter Hilton
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.