Kyle’s background as a developer has informed his view of how teams can achieve the level of collaboration needed to be successful in an Agile environment. Having read Kent Beck’s Extreme Programming Explained book, he started to work with developers, helping them improve their ways of working. But that wasn’t enough. In this episode, we explore what is beyond the team that can make or break an Agile transition.
About Kyle Aretae
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.
“We don’t leave our human-selves at the door once we come into work!” – this is how Faye starts this episode. The question is: as a Scrum Master, what does it mean for me? Faye’s journey to the Scrum Master role gives us some insights into the wide-spread consequences of that phrase. It also links directly to the story of failure that Faye has to share with us. It is a story of how a team member started bullying other team members. Listen in to learn to detect bullying signs early on.
About Faye Thompson
Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.
Management was micro-managing the team. Ilya, the Scrum Master, tried to protect the team. The stress levels were high… This is a very common story in the software industry. When deadlines loom, the whole dynamic changes. As Scrum Masters, we must be ready for that moment. Listen in to learn about how Ilya handled the situation, and what you can apply in your own situation when the time comes.
Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.
As we work with multiple teams, it is inevitable that we will meet a team member that is against Scrum in all possible ways. They’ll ask: why do we need to have a Sprint Review? Why do we need to have a retrospective every Sprint? How do we, as Scrum Masters, deal with such team members? Listen in as Peter shares his experience with such a team member, and how he focused on helping the team, despite the negative comments from one team member.
About Peter Zylka
Peter is a freelancing Scrum Master who really loves what he does.
Peter is passionate about Agility and loves supporting teams and organizations on their way into the agile world. As a Scrum Master his goal is to enable each individual in the team to perform the best possible way and to actually understand what a team really is all about.
He starts every day with the goal to make the people around him better.
Rewards are an easy tool to use. But does it work as intended? Do rewards really help teams and people perform better? In this episode, we explore one story where Paulo tried to use rewards to help a team, and what happened once the rewards became an expectation from the team.
About Paulo Rodriguez
Paulo has worked in the IT industry for 15 years. He started as a web developer for a local bank. His Agile journey began in 2015 and he’s been a Scrum Master for 3 years. Paulo is also a Certified Professional Scrum Master from Scrum.org (PSM I).
You’d think that a team of Agile Coaches understands the importance of facilitation. However, that’s not always the case. In this episode we explore how a team of Agile Coaches went through the process many teams go through: from no facilitator, to an external Scrum Master and …
Listen it to learn what happened next.
About Claudia Toscano
Claudia is an Agile Coach and Scrum Master since 2014, she in charge of the Agile Transformation at EPM with a team of 5 other people. Agile and being Mom are the things she enjoys the most.
As more traditional companies adopt Scrum, we – the Scrum Masters – are in a particularly tough position. We need to bridge the old world, and the new reality of Scrum. In the old world (PRINCE2, PMI, IPMA Project management, etc.) there were reports. And lots of them. In Agile we believe that the only measure of progress is “running, tested software”. How do we combine the two?
In this episode we talk about how Darryl faced, and ultimately adapted to that reality.
Darryl is an IT professional specialising in Kaizen (continuous improvement), Agile delivery and coaching, Lean Thinking implementations and more recently applications of DevOps and Data Science. Darryl can also be found singing in rock/pop choirs, and watching or reading anything in the realm of Sci-Fi / Marvel.
When the deadlines approach, there’s a lot of pressure on the teams. It’s understandable that there is pressure, but why does that happen when the software the team produces often waits for weeks before being put in production or released?
What is a Scrum Master to do in these situations? Listen in while we discuss the pressures teams suffer, and what are the alternatives we have to help organizations and teams through that easy temptation to pile on more pressure
About Joanna Koprowicz
Joanna is an Agile Enthusiast with a burning passion to help organizations work smart not hard. She is one of the co-organizers of Agile-Lean Ireland Community. Currently she works as a ScrumMaster in Dublin.
Max’s first Retrospective was an exercise in the limits of planning. He shares with us how he prepared for that, and ultimate how it all failed. From that failure, however, came an important lesson that he still applies today.
Listen in to learn what Max learned about effective retrospectives after the failure despite the detailed plan for his first retrospective.
About Maximilian Fritzsche
Maximilian worked as a Scrum Master for several years and believes that the way to look at the role is to always have in mind the following quote: “Keep moving forward” – his favorite quote, and what he tries to do every day. “One step at a time!”
The way we reward people for the work they do, directly impacts how they act. In this episode we explore the impact of an individual reward system on how Abbas acted, and what he learned from that situation.
We explore motivation, relationships and most of all, the systemic impact of the reward systems we create in corporate environments.
About Abbas Ghahremani
Abbas is a Scrum Master who enjoys coaching individuals and teams who are on a journey of developing an agile mindset, focusing on values and principles which will make them work lean, collaborate and generally enjoy work more!
He calls himself an agile and product person focusing on delivering value early and often to customers.