In this episode, Pieter shares a story that, as he points out, could be an exam question for a Scrum Master certification exam: what should a Scrum Master do when a team member does not collaborate well with others?
We discuss what options Scrum Masters have when this happens, and also what did not work for Pieter in that situation.
About Pieter Verbaarschott
Pieter is a hands-on generalist with a background in software development. A passion for helping teams work together better. Agile aficionado since his first endeavors in Extreme Programming. Happened to be among Agile Manifesto authors when the discussion was hot. And he refuses to work the traditional way.
Rachel started with a manufacturing background, which naturally left her with questions about how to apply her craft to a different industry. However, as she started in her Scrum Master role, she learned how to ask questions in order to enable the team to understand and solve their own obstacles.
Rachel is passionate about individual and team growth. She has fostered an environment of collaboration and continuous improvement in the manufacturing, biotech, and software industries. Currently, Rachel is focused on the power of an individual and recently acquired her Leadership and Performance Coaching certification.
When working with a team in a startup, Simon focused on helping the team develop the product. However, the customers weren’t there yet, and at some point the product was there, but there was no income.
Even when the product finally launched, and a customer had been found, Simon’s job was abruptly ended and he left the company. This gave Simon one of the most important lessons you can learn as a Scrum Master… Listen in to learn what that lesson was, and how Simon brings that lesson with him every day.
About Simon Flossmann
Simon helps teams effectively use Scrum and an agile mindset to deliver products and services that matter! As a Scrum Master and Professional Scrum Trainer, licensed by Scrum.org, he supports teams and organizations of varying sizes in a wide range of business domains, like automotive, home appliance, energy sector, federal government agency, and insurance.
As developers, who move to a Scrum Master position, we usually face some conflicts between how we used to work, and what the Scrum Master role demands from us.
In this episode, we talk about the transformation that Paddy went through from a developer to a Scrum Master. As he puts it: “At some point, you need to decide: you can either make great things or you can make things great”.
About Paddy Corry
Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset.
This week’s guest – Julio de Lima – is a quality and testing engineer that shares his views on Agile teams. The testing/quality perspective is critical for Scrum teams. In this episode, we talk about how test engineers can sometimes try to do everything themselves and prevent the team from taking ownership of the quality work. Julio shares his lessons learned and how he learned to help the whole team feel responsible for the quality of their work.
Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner.
Sometimes companies want to adopt Scrum, only to disguise their Project Management traditional ways of managing. In this episode, we talk about a company that had hired Scrum Masters but really wanted them to act as Project Managers. We then discuss how Scrum Masters can work with Project Managers to change their perspective by showing how to create value in a very short time. This can be a transformational moment for your company and your Project Manager.
About Sjoerd Nijland
Sjoerd is a founder of Serious Scrum, and creator of the Road to Mastery co-creative online training. Previously E-commerce manager at Bugaboo, and then Manager of Operations at Digital Agency Triggerfish.
As Scrum Masters, we often want to help the PO, or other stakeholders that ask us questions. This wish to please can sometimes lead to the Scrum Master becoming a “status chaser” for the remote or otherwise absent stakeholder. In this episode, we talk about the dangers of becoming a “status chaser” as a Scrum Master, and how to help the team take ownership of the communication with the PO.
About Oskar Collin
Oskar is a former software developer who became a passionate agile coach and Scrum master. He did so mainly because he was better at helping teams working together than building software. He loves experiments and questioning the status quo. He is passionate about helping teams build digital products and deliver value continuously.
Growing teams over time mean that we help them find their path to ownership and self-organization. In this episode, we talk about creating a roadmap to self-organization, and helping teams take steps towards owning their work, and putting self-organization in practice.
About Stefania Marinelli
Stefania is an Agile Manager @Hotels.com (Expedia group) former Scrum Master, former team leader/project manager, former developer. Stefania is fascinated by people dynamics and works every day to create a collaborative and safe environment. NVC practitioner.
When we enter a new organization as consultants or employees, how do we get a new team started? In this episode, we explore the difficult task of the Scrum Master as a team builder and catalyst.
About Anubhuti Agarwal
Anu is a software tester turned Scrum master. She worked as Software QA in India for 6 years and then moved to Berlin to complete her Masters in Business Administration. She has been working as a Scrum Master for 3 years in an agency and has learned, first hand, the challenges of working with Agile in an agency.
Thomas, a game 3d artist turned Scrum Master, got started in his journey thanks to a mentor who was a Scrum Master in his team. As he started his own journey he fell into the trap of focusing only on questions, which was important, but led teams to dwell on the problem for too long. Invariably the retrospectives turned into a complain fest, and there was little time to focus on solutions. It was then that he learned about “problem-focused” cultures and what to do about it. Listen in to learn how Thomas got his teams from problem-centric to solution-centric.