The role of Scrum Master is not yet a fully developed and recognized role in the Software industry. This has an impact on how people find (or not) their motivation to excel in that role.
In this episode, we talk about cultures that place a lot of value on the status of a Job Title, and how that affects the motivation of people that take up the Scrum Master role.
About Paulo Rebelo
Paulo Rebelo helps companies to improve using agile and lean principles like Scrum, XP, and Kanban. He currently works at Blackhawk Network in the U.S., helping teams succeed by building great products. His background is a developer, Scrum Master, product owner, project manager, and coach. Paulo is a CSP, CSPO and a CSM from the Scrum Alliance and PMP from the PMI.
In this episode we explore a very specific culture within North America, and how it affects the adoption of Scrum. Listen in to learn how a Nebraska Scrum Master takes advantage of their specific local culture to help her team.
About Elizabeth Christensen
Elizabeth Christensen shares tales from the not-so-cutting-edge, bringing Scrum to Marketing. She is currently developing scrum practices for a marketing team. With a background in business management & team leadership this self-proclaimed scrappy new Scrum Master finds her way in a never-before-experienced opportunity.
In this episode, we reflect on the fit between North American culture and Agile culture. We discuss some of the characteristics that define North American culture, and how that contrasts with other cultures. Specifically, we discuss why Lean, something that came from Japan, might be completely different in the way the individual is part of the approach to work.
Kyle has been programming since ’81. Teaching since ’91. Practicing Agile (Extreme Programming – XP) since 2000. Kyle is always interested first in better ways to understand things and systems. Especially interested in Complex (CAS/VUCA) Systems like building software or the economy at large.
There’s the temptation that people are as easily replaceable as parts in a machine. But is that the case? And if you answer “no”, what does that mean for you as a Scrum Master? In this episode we explore the many reasons why treating people as “resources” causes problems in the long run.
When are we successful as Scrum Masters? We don’t really know until we start observing the patterns of behaviour and communication between the team members and other stakeholders involved. Alberto describes some patterns of behaviors he looks for to assess his success.
About Alberto Brandolini
Alberto looks at himself as sit at the intersection between the Agile/Lean community and the Domain-Driven Design community. Sometimes, he says, the solution is to write better software, sometimes the solution is to take a big modelling surface and see “the problem” in all its magnificence, sometimes the solution is to have a beer.
You can link up with Alberto Brandolini on LinkedIn, or connect with Alberto Brandolini on Twitter.
Amitai tells us the story of a team that was too large, and had an “inner team” that prevented anyone from influencing the larger team. We discuss the meaning, and impact of power structures inside teams that tend to perpetuate self-destructive behaviors.
Today we play one more Agile in 3 Minutes episode that talks about certain topics that are in line with the story Amitai shared with us. Today’s Agile in 3 minutes episode is episode #15, titled “Influence”.
About Amitai Schlair
Amitai is a Software development coach, and legacy code wrestler, non-award-winning musician, award-winning bad poet, and creator of Agile in 3 Minutes, which is a great podcast about what Agile really is about. A must listen for anyone interested in Agile Software Development.
You can link with Amitai Schlair on LinkedIn and connect with Amitai Schlair on Twitter.
Gitte explains why teams sometimes forget to think and they that is a self-destruction pattern. Being agile requires us to be flexible, and when we stop thinking the best we can do is follow orders. Asking questions and being ready to sit back and listen helps us bring the thinking pattern to our team’s day-to-day work.
About Gitte Klitgaard
Gitte is a very pragmatic world-changer. She wants to make the world a better place today, not tomorrow. She’s also very experienced agile coach and regular speaker. But here’s the punch line: she talks about things that no one else talks about. She lives by the mantra “why try to fit in when you were born to stand out?” and she says that her best coaching tools are listening and making people think.
You link with Gitte Klitgaard on LinkedIn, and connect with Gitte Klitgaard on twitter.
Many Scrum Masters start their career as parttime Scrum Masters. A few books read, a course or two attended, and here we go. What could go wrong? In this episode Daniel explains his first project, and the mistakes that come from lack of experience and parttime assignment.
We also discuss the book Product Development Flow by D. Reinertsen in the context of creating the necessary conditions for learning.
About Daniel Hommel
Daniel is a ScrumMaster and Agile Coach with a strong background in Software Engineering. His first touch point with Agility was starting to use the Extreme Programming practices in 2007. After some years of working more on the technical side in recent years his interest has shifted to facilitation, coaching, guiding continuous improvement and working with people in general. You can connect with Daniel Hommel on Twitter.
“Nothing ever changes here” is a team anti-pattern that sometimes takes over and freezes team behavior. Teams experiencing that anti-pattern will often complain, be discouraged, but will not take action to change their situation. How to help teams like that? Antti tells us a story of a team that was in that situation and what he and his colleagues did to change the situation and save the project.
About Antti Tevanlinna
Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.
The worst enemy of this particular team, according to Jeff Kosciejew, was the pattern of avoidance. Avoiding problems is one of the pitfalls that our teams deal with.
Jeff also refers to #MobProgramming, an innovative practice originally promoted by Woody Zuill.
About Jeff Kosciejew
Jeff is a consummate generalist, with experience in a wide variety of industries in a wide variety of roles. Throughout all of his experience, Jeff has had enjoyed success through a single focus on enabling and empowering those he works with, even before being introduced to Agile and Scrum.
You can find Jeff Kosciejew on twitter, and reach Jeff on LinkedIn.