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.
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.
In some teams, there are individuals that have a strong influence on the team. As Scrum Masters, we must be aware of that when it happens, and help the team learn to reflect as a group, instead of following the opinion of the strongest influencer in the team. In this episode, we discuss how single-individual influencers can completely derail a team.
Featured Book for the Week: Loving What Is, by Byron Katie
In Loving What Is: Four Questions That Can Change Your Life, by Byron Katie, Ines found a guide to help her understand the things that can be changed, and those that cannot. This realization helped Ines to be a better Scrum Master, and also in her personal life.
About Ines Stuppacher
Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people.
Ben’s career has spanned from working assembly at Ford Motor Co, IT consulting, DSL Internet provider using wireless building-to-building antennas, systems administration and engineering, data center floor work, DevOps, cloud engineering, cloud architecture, scrum master, people-leader, and agile coach.
In Drive by Daniel Pink, Dragana found many insights on motivation and importance of helping teams work on, and define clearly their purpose.
About Dragana Hadzic
Dragana is an agile enthusiast who believes communication is critical for success in everything, including software projects. A Scrum Master and an Agile Coach with broad experience in IT industry and different leadership roles. Passionate about everything that brings positive energy and enables people to achieve great results.
When Isaac joined this team, he encountered a team that had failed to deliver and was low on motivation. Isaac focused on helping the team find their motivation, organized a kick-off to get the team to come together around a goal, and a common vision, only to see management remove people from an already overwhelmed team… What should a Scrum Master do when that happens? We discuss that, and critical lessons learned about what we can influence (or not) as Scrum Masters.
For Isaac, this is a book that teaches important techniques and helps Scrum Masters make a difference in their place of work.
About Isaac Garcia
Isaac is a passionate Agilist who builds teams with heart and walks their journey together. His driving goal in life is to invest in and impact world changers. He has a lot to learn but is enjoying the discovery in the journey.
We often talk about cross-functional teams on the podcast. We talk about the advantages when it comes to flow, and getting things done quicker. However, there are pitfalls we should be aware of. One of the pitfalls is when the team members in a team start to “cluster” and become like sub-teams inside the team. As Scrum Master, we must be aware of this possible anti-pattern and ready to tackle it quickly. Listen in to learn how Gilson detected and countered the sub-team anti-pattern.
Featured Book for the Week: Coaching Agile Teams by Lyssa Adkins
In Coaching Agile Teams by Lyssa Adkins, Gilson found an out-of-the-box explanation for the Scrum Master role that helped him get out of the traditional task-driven, project manager-like role that many Scrum Masters still take.
Gilson has worked with Scrum for over ten years, first as a software engineer, then taking in both roles of Scrum Master and Developer and currently 100% dedicated as Scrum Master. As a Scrum Master, he truly believes in empowered and self-organizing teams and works inside and outside of the team to achieve it.
When everything is going well, and there’s little to no feedback, the experiment Scrum Master should be a skeptic. Feedback is the fuel for great Agile teams. in this episode, we talk about the big problems that can emerge when the team forgets to collect feedback during development.
David Gentry is an Agile Coach and Scrum Master. He has served in a variety of other roles in his career including developer, data analyst, business analyst, quality analyst, and project manager. In his free time, he can be found playing bass guitar and interpreting how groove applies to life and agility.
Although Scrum was developed in a software environment, the fact is that Scrum can be applied to many different types of teams. In this episode, we learn about how Long applied Scrum in a marketing team, and the anti-patterns he had to face in that environment.
Featured Book for the Week: Lean Startup by Eric Ries
If you got started with Scrum and then discovered Lean Startup, you probably found it to be in line with what you had practiced before. However, Long discovered the Lean Startup book by Eric Ries before learning Scrum, and it reshaped his thinking about what is possible.
About Long Suciu
Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.
A common anti-pattern Scrum Masters encounter in their teams is the inability to say “No!” This becomes an especially impactful anti-pattern when the team is unable to say “No!” to the Product Owner. When that happens we run the risk of allowing the team to ver overwhelmed, and eventually decrease the quality of their work.
In this episode, we discuss that anti-pattern and how Scrum Masters can help Product Owners and teams to avoid that from becoming destructive for the team.
Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at:bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
Featured Book for the Week: Scrum: the art of doing twice the work, in half the time by Sutherland & Unmarketing, Scott Stratten
Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.