Many Scrum Masters have a background in other roles within their teams. Some were developers, others Project Managers, others Testers, etc.
Many of those roles are “doer” roles. Roles that focus more on execution and less on helping others execute.
As Scrum Masters, we must be able to transition from “doer” to “enabler”, and Nedeljko shares his journey with us.
About Nedeljko Damnjanovic
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
Joining a team, it is good to see that they have their tools in order. They can follow-up progress, track what is missing and even leave notes for each other in the items they add to the tool. The problem is when the tool starts to take over the team, instead of the team owning the tool. In this episode, we talk about the tool-Scrum anti-pattern, when the team focuses more on the tool than the things it should enable: communication, collaboration, progress assessment, and metrics.
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
It is one of the mantras in the podcast: “take it to the team”. That mantra helps Scrum Masters focus on helping teams grow and learn from their mistakes. However, there’s a pitfall hiding in that mantra, and that’s when we rely too much on the team. As Scrum Masters we are also the accountability partners for the team. When we don’t pay attention, bad things can happen. In this episode, we discuss the pitfalls of relying too much on the team, and how to avoid this anti-pattern.
About Ajeet Singh
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.
Scrum adoption, just like any other process or framework, is not free from troubles. Especially when organizations are already in the middle of a problematic situation.
In this episode, we review several anti-patterns of Scrum adoption, including hierarchic struggles, abusing the Scrum roles to make them just another set of titles, the extreme attention to the Product Owner role, and many others.
About Tilman Rumland
Tilman Rumland is an agile coach, expert speaker, and productivity enthusiast. He just released his new workshop series: “getting shit done that really matters to you”. As a scrum master, he implemented agile structures to agrilution, a small scale vertical farming startup, ranked on the Forbes TOP 100 innovative German Startups. (www.agrilution.com)
Sometimes team members will speak up. They might even challenge the Scrum Master. At those times is when we must step back, forget about what we “think is right” and let the team members take the lead. That’s the first step in taking responsibility!
Raluca calls herself a recovering Project Manager that discovered Agile and somehow the “good, the bad and the ugly” received distinctive names.
She loves her job and practices Accelerated Learning to achieve her Goals (to become a Scrum Master Trainer for Scrum Alliance, to write a book, acknowledged as an Inventor, share her ideas to the world and with her daughters).
And maybe someday to be a Bonus Podcast guest on the Scrum Master Toolbox Podcast :).
When we get started as Scrum Masters, especially those that have a Project Management or Management background, we tend to “enforce” Scrum. As our understanding progresses though, we start to learn that there’s a lot of value in helping teams learn by themselves, help them feel confident and take over the process.
In this episode, we discuss that change in our approach to the Scrum Master role, and a lot more!
Doug has been an agilist since before it was cool, as his first agility client can attest. He is currently the Director of Agile Development & Coaching at Wisconsin-based Flexion inc., leading agile teams that serve both private and public sector clients. His current hobby is thinking beyond agility, to antifragility.
Let’s say that we are working with a team that is respecting the Scrum rules. They have their Sprint Planning. They hold their Retrospectives. Everyone talks during the stand-up. At first glimpse this team is doing Scrum right. But there’s one thing missing: delivering value to customers early and often!
Preparing to release value is not value delivery. In this episode, we talk about the teams that miss that critical aspect and what we, Scrum Masters, can do about it.
About Anja Bonatto-Minella
Working with agile and scrum only since for a year Anja still considers herself a scrum-beginner. Before starting at her currrent job which brought her into the world of agile, she studied physics and then worked in research for several years.
Jen and Jamie share with us one of the common anti-patterns around the Scrum Master role. Many seem to think that the Scrum Master is an admin person. Setting meetings, ensuring the teams have post-its, etc. But could not be farther from the truth.
In this episode, we discuss how we can avoid the Admin anti-pattern, and how to set the right expectations with teams and the wider organization.
Jen and Jamie (sweet and salty as they call themselves) are passionate about people, relationships, leadership, accountability, common sense, and getting sh*t done! Ultimate dream job would be to coach individuals, teams, and organizations in discovering and cultivating potential and doing things better by identifying people’s strengths, passions, and skill sets, along with effective processes and strategy to build a strong, healthy culture.
When Nisha got started she loved the logical thinking required for programming. However, the role of the Scrum Master was much more than that. On top of that, being a Scrum Master and trying to program at the same time brought some serious problems that Nisha had to face. Listen in to learn how you can survive the dual role of being a programmer and a Scrum Master (or not).
About Nisha Balwatkar
Nisha started her career as a programmer for the love of logical reasoning and technology and soon found herself trapped in the mismanagement of software teams affecting the work and efforts put in by the teams. She always had a feeling she could fix it and eventually moved to be a scrum master. She enjoys helping out teams and see the joy of success by identifying and fixing small things.
Often we mix-up software delivery with project management. Those are different activities. Both necessary, but quite different. When we focus on project management only, we often miss critical work that is necessary to ship software. In this episode, we discuss why that difference matters and how to help teams move from project management focus to project management + software delivery focus.
Eddie is an agile coach who has been working with Agile since 2004 using XP, Scrum, Lean, Kanban & Scaled Agile. He coaches teams, scrum masters, product owners, leaders, coaches, organizations and little humans. He likes teaching agile with Lego & games and is also co-founder of the LeanAgileBrighton conference.