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.