When mistakes happen, the natural tendency in many organizations is to find the ones “to blame”. However, that’s not how you create a high-performing culture. Understanding this, helps us work as Scrum Masters to direct people’s energy and attention to the next step: “how do we make sure similar problems don’t happen, what change do we need?” In this episode, Chris shares one story where an organization was able to go beyond the blame game and create a culture of achievement that helped everyone feel supported and accountable. Listen in to learn what tools helped create that culture.
About Chris Stone
Chris is The Virtual Agile coach, a #PeopleFirst champion, and an Agile Evangelist / Agile Transformation Lead / Scrum Master possessing over 8 years of experience within the IT industry.
As Scrum Masters, we will sometimes face an impossible situation. Or at least, it will seem that way. In this episode, Adrienne tells the story of a team that was set up for failure, and we explore what Scrum Masters can do in those situations.
About Adrienne Rinaldi
Adrienne Rinaldi is an Agile Transformation Coach and co-founder with PinnacleTek Consulting. She has a passion for topics such as emotional intelligence in agile leadership, cultural transformations and breaking the norms in hierarchical organizations. She has enabled value-based strategy and business agility at many levels of client organizations: teams, programs and portfolios. When not being an agilist, Adrienne’s activities a published book (about beer and yoga!), mountaineering, hiking (Colorado 14er finisher), kayaking and spending time with friends/family.
From his early days as a Project Manager adopting Agile, Arjay was hooked. He saw how Agile could help him and the teams he worked with. However, when he tried to apply Agile outside the software industry, he discovered how the industry context had a direct impact on the applicability of some of the Agile ideas he had learned to love. Arjay shares what he learned about how to adapt Agile ideas to any industry.
About Arjay Hinek
Arjay has been an Agilist for over a decade. In the last few years, he’s focused on Agile and “product development” for non-software applications. A considers himself a teacher at heart, he uses metaphors and story-telling to help others see their challenges from a different perspective and overcome them.
This episode starts with a story of a team that was asked to “improve their velocity”. It’s a cautionary tale about what happens when Scrum is used as a method to get the teams to “go faster” without thinking about the larger consequences of Agile adoption.
In this episode, we talk about the Rational Unified Process, a process developed in the 90’s that ultimately re-enforced the waterfall anti-patterns in organizations.
Leland is a SAFe Release Train Engineer and servant leader who is passionate about helping improve the work environment and helping teams uncover better ways to development software. He focuses on collaboration, shortening feedback loops, improving the flow of work through the system and increasing the team’s adaptability so they can quickly respond to changes and satisfy customers through early and continuous delivery of valuable software.
To try and help a team solve some of the issues they were already privately complaining about, Ronny organized an open space session. Unfortunately, the team did not bring up the issues they were facing. This led to Ronny realizing that it was not enough to have a space to talk about problems, there were other things missing for that team to be able to talk, and solve the problems they were facing. Listen in to learn about what Ronny tried next, and how well that worked.
About Ronny Deicke
Ronny is a Scrum Master and Agile coach with a developer and team lead background. Currently working as a part-time Scrum Master and in the rest of the time giving (agile) workshops, supporting people as a coach and Agile Coach. Video game enthusiast and Indie developer on the side.
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.