Izis Filipaldi: The new role of leaders in Agile teams

In Agile teams, Leadership has a different role. In this episode, we talk about the traditional approach to leadership in teams. From the technical lead to the line manager, and how those roles should change to enable Agile teams. 

Featured Book for the Week: How to Win Friends and Influence People, by Dale Carnegie

In How to Win Friends and Influence People, by Dale Carnegie, Izis found a set of tools that help her in her daily work as a Scrum Master. The book was written in the 1930’s, on the back of the Great Depression, and shares some of the techniques that successful people used to achieve in their lives. Dale goes through many of those techniques and outlines simple approaches that can help Scrum Masters also achieve their goals and help their teams. 

About Izis Filipaldi

Izis’ mission is to help people to improve their knowledge and professional value inside organizations, applying the agile way of working. She has been working as an Agile Coach for more than 7 years, helping people to deliver products, developing an environment free of judgments where they can fail fast and learn faster. Continuous improvement of: people knowledge, product delivery, and work environment, are her 3 main focus on work. And she loves what she does!

You can link with Izis Filipaldi on LinkedIn and connect with Izis Filipaldi on Twitter.

Nick Stewart: Why the Definition of Done is critical for Scrum teams wanting to be more predictable

This team that Nick was working with had trouble delivering on time. When Nick looked into it, he discovered that the team did not take into account all the work necessary to adhere to the Definition of Done. Once he found that, however, he had to work with the team to help them realize what was going on, and how they could become more predictable by simply taking into account what they had committed to: the Definition of Done criteria.

Featured Book of the Week: The Goal by Elyahu Goldratt

When reading The Goal by Goldratt, Nick had a lightbulb moment. In that book, the author describes the impact that one single aspect of work can have: throughput. 

The book describes how not paying attention to that aspect may destroy the ability to deliver value. 

In this episode, we also discuss The Phoenix Project by Gene Kim et al

About Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter

Sebastian Reverso: The Treasure Island Retrospective as a way to help team members empathize

As Sebastian started to work with multiple teams, he started to note some patterns of behavior that might cause problems. In this episode, we focus on the “professional jealousy” that some team members showed towards each other. We discuss how to detect it, and what the possible consequences of that behavior might be. Learn to detect it, and listen in to learn how Sebastian helped the team move forward.

In this episode, we refer to the Agile retrospective format: The Treasure Island, and to Solution Focused Coaching

Featured Book for the Week: Por Un Scrum Popular: Notas para una Revolución Ágile (Spanish Edition)

Por Un Scrum Popular by Mayer and Cyment is the Spanish edition of the popular: The People’s Scrum by Tobias Mayer

Sebastian found especially informative the aspects of the day-to-day Scrum that the authors go through, and how they compare what work looks like when using Scrum and when not using Scrum. 

In this segment, we also refer to the Scrum Master Toolbox Podcast episode with Claudia Toscano where the book “Por un Scrum Popular” is discussed in more depth.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Jaime Bartol: How Scrum teams quickly spiral into conflict when the pressure is high, and what to do about it

In this episode, Jaime introduces a project that started off on the wrong foot. The team was 15 people, including some new people. Quickly the team entered the “crunch mode” to try an meet an ambitious schedule. That’s where our story starts, but there’s a lot more to share. From the small impediments to the behaviors the team developed that ultimately led to bigger problems. This is a tale about a team that was doomed for failure until we step in. We discuss some of the steps you can take if you face a similar situation as a Scrum Master.

Featured Book for the Week: Agile Coaching 

In Agile Coaching by Rachel Davies and Liz Sedley, Jaime found important tips to help her learn the role of Agile Coach. The book is practical, and has chapters on how to introduce certain practices to the teams we work with. From tips that push us outside “the box” to the simple tips that help us define where to start before taking on more complex and ambitious practices in the team. The book is a complete guide for Scrum Masters that want to learn how coach their teams.

About Jaime Bartol

Jaime has been a ScrumMaster/Agile Coach for 6 years with experience in large organizations as well as startup teams! She has worked with frontend and data engineering teams and even brought Agile to awesome marketing teams! Jaime’s passion is about teams and using Agile/Scrum fundamentals to elevate efficiency, productivity, and joy!

You can link with Jaime Bartol on LinkedIn.

Rachel Martz on how to help Scrum teams in a crisis of trust

When Rachel worked with this team, it had been banned from releasing to production. Never a good sign. But she quickly learned that the situation was even worse: the team members were distrustful of each other, people avoided each other and closed the dialogue quickly. What should a Scrum Master do in this extreme situation? We discuss this, and other insights that can help you work with teams that have lost trust in each other.

Featured Book of the Week: The Power of Spirit: How Organizations Transform

In The Power of Spirit: How Organizations Transform by Harrison Owen, Rachel found a new metaphor for organizational change. She also learned how important it is to invest in learning the history of why people do what they do in the organizations we work for.

About Rachel Martz

Rachel has been in digital product development for over 20 years, having performed every role imaginable. She entered the agile space 13 years ago, doing hands-on product strategy and development modernization. 

Rachel is in the data and analytics industry at the moment and loves being a Scrum Master because it’s the most impactful role she can have for helping improve people’s lives.

You can link with Rachel Martz on LinkedIn.

Angeliki Hertzfeldt: How to help a Scrum team survive an overbearing team member

When certain behaviors emerge in a team, the consequences can be catastrophic. In this episode, we talk about what happens when one of the team members tries to constantly push their perspective. We discuss what were the consequences for this specific team, and how we can ensure that the team does not fall into a negative spiral of conflict, rumors, and disengagement.

Featured Book for the Week: The Scrum Guide

Although The Scrum Guide is not a book, it is a reference document for everyone wanting to practice Scrum at work. While the rules in the guide are simple, the more we read them, the more insights we get into the heart of Agile and Scrum.

About Angeliki Hertzfeldt

Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.

You can link with Angeliki Hertzfeldt on LinkedIn and connect with Angeliki Hertzfeldt on Twitter.

Joost Mulders: How to work with Scrum teams that lost motivation due to command&control management

This team that Joost was working with was confronted with top-down decisions over which the team had no control. As an example, Architects would tell the team what to do, and how to do it, but would not listen to the team’s perspective. Slowly the team lost motivation, and the bad results quickly followed. In this segment, we reflect on the impact that the environment had on the team, and what Scrum Masters can do to work with teams in that situation.

Featured Book of the Week: Management 3.0 by Jurgen Appelo

In Management 3.0 by Jurgen Appelo, Joost found the inspiration he needed to focus on the overall organization, as opposed to focusing only on the team. We discuss the example of Delegation Poker from Management 3.0, which shows that delegation is not a binary game, but can have many levels and approaches.

About Joost Mulders

Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.

You can link with Joost Mulders on LinkedIn and connect with Joost Mulders on Twitter.

Remy Fletcher: How Scrum Masters can work with authoritarian managers and survive

In some teams, the role of the leader or manager can be a blocker to the team’s adoption of Agile and ownership of the product and process. However, those same managers usually develop their command and control approach due to past successes. As Scrum Masters, we must learn to work with those teams, starting by creating a close relationship with the team members. 

Featured Book of the Week: The Advantage: Why Organizational Health Trumps Everything Else In Business

In The Advantage by Patrick Lencioni, Remy learned about the concept of an executive team that he could apply to his own product when his team was struggling with direction. 

In this segment, we also refer to Start with Why, by Simon Sinek, a book that helped him understand the importance of communicating the rationale behind the decisions and involving the team in owning those decisions.

About Remy Fletcher

Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.

You can link with Remy Fletcher on LinkedIn and connect with Remy Fletcher on Twitter

Micah Stamper: The type of execution focus that leads Scrum teams astray

The focus that some teams have on “execution” can be a great resource. It helps teams get into the details, and push forward even when finding the inevitable setbacks. However, when teams are completely focused on execution there are other aspects that lose focus, and that can derail the team. In this episode, we talk about how the execution focus that some teams have lead them astray from certain critical aspects of the software development process.

Featured Book for the Week: The art of doing twice the work in half the time, Jeff Sutherland

In The art of doing twice the work in half the time by Jeff Sutherland, Micah found a great reminder and introduction to the Lean principles he now applies in his own work. He also found a great reminder that software development has its own context, that needs to be taken into account in the work Scrum Masters do with software teams.

About Micah Stamper

Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master.

You can link with Micah Stamper on LinkedIn and connect with Micah Stamper on Twitter.

Rahul Bhattacharya: the dangers of specialized Scrum teams

When Rahul started to work with a team that was new to Scrum and Agile, he noticed that the team members were very focused on their individual part of the product. Front-end developers only worked and worried about the front-end, and back-end developers focused on the back-end functionality. In the Sprint reviews, team members focused on their individual contribution, and the inevitable synchronization and coordination problems followed.

In this episode, we talk about the risks of highly specialized teams and how to tackle those in your role as a Scrum Master.

Featured Book for the Week: The 4-hour workweek by Tim Ferriss

In The 4-hour workweek by Tim Ferriss, Rahul found an inspiring story about the choices we make in our daily lives. He learned about “time” as a spendable resource, and how to create more options for yourself as you seek a better life situation. In this segment, we also refer to the Tim Ferriss podcast.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback.

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.