Dimitri is a Scrum Master, Agile Coach, but Dimitri Favre is also the author of a book about #NoProjects, an approach that removes many of the problems that projects bring to software projects. In this first episode with Dimitri, we talk about one of the possible consequences of having a project mindset: wanting to follow the plan no matter the consequences.
We discuss why it is problematic for teams and Product Owners to focus on the Features in the Backlog, and how to get out of the “solution space” to better understand the impact the product should have in the market and our customer’s lives.
Dimitri is a business, transformation, and agile coach and a repented project manager. Dimitri works side by side with executives, managers, and teams to uncover better ways of developing software and delighting customers.
The transition from Waterfall to Agile is always a difficult one. In this episode, we explore a transformation story with Saritha and learn about the different anti-patterns we can expect when we face a similar story ourselves. We also dive into why retrospectives are so important in similar transformations.
About Saritha Rai
Saritha has been working in the IT industry for 13+ years and is an adaptable and constant learner. She has over a decade of experience in software development and is passionate about training, guiding and coaching people to have a good working environment which will result in high-quality deliverables.
When George joined this company, he was told that they were already “pretty agile”. This is usually a sign that somethings are not really working well, and this was no exception. When he joined, George found out this was a project manager-driven organization, where project managers tried to get the work done but wanted to reduce the budget at the same time. The anti-patterns followed, and George learned a few important lessons about being a Scrum Master in a project-driven organization.
George Mathews is a Scrum Master at SentryOne for two fully remote teams. Prior to that, he had experience as a Customer Service Representative, Operations Analyst and Finance Technical Analyst allowing him to employ a broad practical point of view as he coaches Agile teams at SentryOne.
Teams need a great Product Owner to be able to exploit their potential. When Scrum Masters work with teams that have a great PO, they learn the impact that the PO role can have. However, when a great PO leaves the team, what should the Scrum Master do? In this episode, we learn about Mandy’s attempt to help the team by replacing the PO, and why it is so critical to avoid that anti-pattern. Listen in to learn what to do when a great PO leaves.
About Mandy Sunner
Mandy calls herself the Angel of Agile as she guards her team and stakeholders from attacks and compromises which are forthcoming in an era of uncertainty. Her Agile approaches are thought through by virtue of being a systematic thinker and keeping the customers at the forefront of development. A problem solver with many years of practical experience.
When Tony heard he would be facilitating a large event (250 people) he thought immediately about using an approach that he had good results with. But as we learn in this episode, that’s not always a good idea. Learn about what Tony failed to consider, and get some critical tips on how to prepare for such events.
Tony coaches Agile teams across the UK and currently serves as program advisor to the Scrum Alliance. His most recent client is applying Scrum and Kanban in the engineering and production of physical goods.
Tony is also in the organizer team for the Scrum Gathering in sunny Lisbon this year, and he’s busy working with a great team of volunteers to review and build a program of great talks and workshops.
As Scrum Masters, we cringe when we see an incoming problem which we know will hit the team and we have to stand back and let the team learn from that experience. In this episode, we talk about one such story, and why it is critical for Scrum Masters to let the teams experience failure, first hand. Be ready to help when that happens, listen in to learn how.
About Olsen Turan
Olsen is an experienced Agile Coach and Scrum Master with a mix of Servant Leadership skills and technical knowledge acquired over his decade-long career. His background includes Ph.D. studies in Organizational Leadership, Agile Transformation and Coaching, Project Management, and Scrum Master duties.
When leadership in an organization changes, they bring their own practices and habits with them. In this episode, we explore what happened in an organization when new leadership stopped some of the practices that were working for that organization. A good reminder that the role of the Scrum Master also includes developing the process for the organization. Listen in to learn how Sami took responsibility and helped the organization improve.
In this episode, we also talk about how we can improve as Scrum Masters by participating in our local communities. We refer to meetup.com as a place to find your local community and start taking part in their events.
About Sami Prentice
Sami is a Scrum Master in Denver, Colorado. She used to work in the beer industry before making the switch to Scrum Master and she is passionate about facilitating awesome meetings that don’t suck.
Many of us start our Agile journeys with Scrum. It is only later that we start putting Scrum in the Agile context, and there’s much to learn and change when we do. In this episode, we talk about what changes when we focus on enabling our teams to be Agile, and not only follow Scrum.
As our workforce changes rapidly, Tom suggests it is going to be more and more challenging to attract and keep talent and knowledge, and that’s why we need a healthy and sustainable working environment. Tom is passionate about improving the industry for his children and their generations.
We’re often faced with daily meetings that constantly try to run over. Team members have topics they want to discuss, and it is enough for one of those topics to surface in the daily meeting for the meeting to risk running too long. Now imagine that several team members also have topics they want to discuss? How do you keep a daily meeting in time? And when is it necessary to break the 15-minute rule? We discuss the many tricky aspects of facilitating one of the most important sessions in Scrum: the Daily Meeting.
About Thomas von Busse
Thomas is a Scrum Master since 2013. After his Bachelors’s Degree in Software Engineering, he gained experience as a Programmer and uses this deep understanding of how to build software systems to help his Teams get better with each iteration.
Many Scrum Masters will be incredibly motivated to adopt and apply Scrum when they start. We often start because we want to help teams, and want to improve how they work. This motivation can be a huge resource, but can also be a problem. In this episode, we explore what happens when our motivation takes the better of us, and makes us forget simple rules like “always get buy-in before any change”. Listen in to hear about what Bola tried, and what he changed in his approach to the Scrum Master role as a result of that experience.
About Bola Adesope
Bola is an experienced Business and Agile Transformation Consultant, Speaker and Coach with in-depth knowledge and experience working with businesses in implementing best practice frameworks, driving changes and solving complex business problems. Bola has worked on several transformation initiatives, coached teams and Scrum Masters. He’s an Agile Coach based in Toronto.