failure story Archives - Page 2 of 56 - Scrum Master Toolbox Podcast

Tinatin Tabidze: Mastering Agile as a Non-Technical Scrum Master – Insights and Tips for Success

Tinatin, a non-technical scrum master, faced challenges in her role due to unfamiliar terminology and the desire to contribute actively, and from the start. She faced a tough learning curve while implementing an authentication and authorization system for a fintech company. At the same time, her team was unable to deliver at the end of each sprint. For her own learning as well as to help the team, she helped the team create a roadmap with an emphasis on visualization. This roadmap was used by the team to communicate deliveries to stakeholders and understand project delays.

As junior scrum masters, we may face situations like this. Tinatin suggests that, at the start, technical knowledge is not necessary, but over time it is important to be adaptable and participate in technical discussions as scrum masters change from team to team, and participate in different technical domains.

Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story – How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Tinatin Tabidze

Tinatin Tabidze is a Scrum Master currently working in Stuttgart, Germany. Originally she started out as a project manager. She has experience with multiple scrum and kanban teams, working with scaled agile frameworks.

You can link with Tinatin Tabidze on LinkedIn.

Bram De Block: Discover how to break free from the trap of thinking you know it all and bring agile success to your team

In this podcast episode, Bram discusses the topic of thinking that one knows it all, and how this attitude can negatively impact a team’s ability to effectively implement agile methodologies. Bram notes that this mindset can lead to a lack of respect from team members and a tendency to focus solely on following the sprint guide without considering the needs of the team. To combat this, Bram suggests bringing up the sprint goal without mentioning it by name, and focusing on identifying areas where team members can work together effectively. Additionally, Bram advises using curiosity to engage team members and encourage collaboration. Listen to the episode to gain a deeper understanding of how to overcome the challenges of thinking you know it all and bring agile goodness to your team.

About Bram De Block

Bram is not an official trainer, consultant nor freelancer. He is just himself, supporting colleagues in applying and growing their own potential and getting stuff done. Bram started as a software developer for 10 years, then grew into a half-time agile coach, and finally, full-time “Global Agile Lead” at Skyline Communications. Something “special” he learned (even if he wishes it wasn’t special): the meaning and impact of “respect”.

You can link with Bram De Block on LinkedIn, or meet Bram face-to-face at this meetup he hosts in Belgium.

Pino Decandia: A problem we all have with the “traditional” Scrum Master role vision

Pino was just starting his own journey as a Scrum Master. He joined a new team, with a strong passion for helping the team, and protecting them from interference. He saw his role as the “protector of the team”. As he tried to deliver on that Scrum Master role vision, he quickly realized that something was off. There was a part of that protective role that was not right for that situation. In this episode, we explore what was the conflict between his vision for the role, and the reality of software development.

About Pino Decandia

Pino started in software development but realized he was more interested in people than code. With experience, Pino came to believe that people can change; they don’t resist change but offer their own vision, which needs to be met.

Secondly, needs drive behaviors. To provide help, we must allow them to be clearly expressed. To set the example, we need to be ready to be the first to state our needs.

And thirdly, that ideological battles are meaningless.

You can link with Pino Decandia on LinkedIn.

Peter Janssens: Learning to work well with a difficult team member, a critical lesson for Scrum Masters

Peter joined a team, and after a while he found himself not wanting to coach one of the team members. The team member in question was well respected in the team for this technical knowledge, and his “hero” status, but Peter was not able to help him to adapt to the needs for the team. He missed daily meetings on a random basis, and did not accept other ways of working. Over time, Peter and this team member grew apart, and Peter eventually handed the team to another Scrum Master. In this episode, we talk about how to avoid situations like this, and what Peter learned that now helps him deal with even the hardest to coach team members!

About Peter Janssens

Peter built a long career in agile coaching and training, and worked in leadership positions leading a PO team, and recently became CTO in a SAAS product company. Peter loves all conversations on effectiveness of team decisions, but he quickly realized that being responsible is different from being a coach. As a leader there is the challenge of sticking to the same foundations when dealing with delivery pressure.

You can link with Peter Janssens on LinkedIn.

Gert Brits: When “taking it to the team” is the wrong solutions, an unexpected lesson for Scrum Masters

Gert heard his colleagues complain to him about some of the challenges and problems they were facing. Trying to help them, Gert setup a session for the team of Scrum Masters to discuss the problems he had heard. However, there was one problem… Listen in to learn when it is not a good idea to set up a collective retrospective, even if you know there are problems that need to be solved!

About Gert Brits

Gert came from a programming background, and has worked across multiple industries, applying Agile Coaching across diverse and non tech areas. He has a focus on group dynamics blended with systems thinking, and the art of balancing application vs theory.

You can link with Gert Brits on LinkedIn.