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.