As Scrum Masters we are intimately familiar with Retrospectives. We plan, organize and facilitate retrospectives for our team members and even larger chunks of the organization. But when was the last time you did your own personal retrospective? Leading by example is a concrete path for success so do the same things you ask the team to do. In this episode we discuss concrete examples of “leading by example” with Joe Anderson.
Ask the team to think of a movie that illustrates what happened in the previous sprint
Ask each team member to review the Sprint as if it was a movie
List down the “ups” and “downs” with the team member speaking
Dot-vote to select the concrete focus for the next Sprint
Help the team decide on a concrete action to tackle the key topic they identified in the retrospective
About Joe Anderson
Joe is a Scrum Master at a small travel technology company with a passion for bringing out the best in people and building deep relationships. He works hard to foster an environment of safety, fun and learning with a focus on relentless improvement.
We want to help teams and organizations succeed. This is the focus of our work as Scrum Masters. But here’s the thing, sometimes the team needs to risk failure to go beyond the established patterns of behavior. In this episode, Arif explains the role of discomfort in the growth of the team and the Scrum Master, as well how to avoid going beyond the breaking point.
In this episode, we discuss the technique of “Role Playing” as a method to help the team understand their own behaviors.
About Arif Bobat
Arif is an experienced Scrum Master with a passion for enabling teams to achieve their potential, Arif loves challenging situations. In the last 5 years, he has been made redundant twice and fired twice. He is not afraid of speaking up when he sees anti-patterns and/or a lack of willingness to change behaviors.
For more than 10 years, Don has been a scrum master and coach working in different sectors in London and across the UK as an independent consultant.
With a background of 10+ years in several development roles for web and finance systems, Donald has a good technical knowledge of modern development techniques, and can quickly build rapport and respect with development teams, understanding their issues and helping them to find the right solutions.
Scrum Masters are seen as problem solvers. But is it really what they are there to do? Venetia challenges us to think about how we can help the teams take over the problem solving process themselves. How can we do it? How can we motivate teams to “own” the solving of their problems?
These are some of the questions we tackle on this episode where we share many tools for you to help your team own their problem solving process!
About Venetia Foo
Venetia has been on her agile journey since 2007 and has been a witness to the best and to the worst of it. She is passionate about learning and continuous improvement. She uses a variety of skills to empower and enable teams to perform at their best.
Jac starts by sharing his value that orients the definition of success: People over Metrics. That is, while metrics are important, we must always consider the people first, not the metrics. Jac describes some of the symptoms of a successful outcome from our Scrum Master work and shares with us some of the tools he uses to help him get to that successful outcome.
About Jac Hughes
Jac is a scrum master who has a passion to help teams become empowered, autonomous but most importantly productive. Jac has served 7 years in the Royal Navy before moving into the world of IT.
When we define success for ourselves we are affecting how we see the work we do. Balazs challenges us to take things step-by-step and define success at the daily level. And only then move on to the work the team does and we do. Finally we should focus on how the team themselves succeed at achieving their goals. Success has many different layers and all of those have a daily implication. Listen in to hear the examples that Balazs shares about how he takes higher level definitions of success to the daily level in the work he does with teams.
About Balazs Tatár
Balazs is a technical project manager, working for the European Commission in Brussels, Belgium. Currently he plays the Scrum Master role in a support team of one of the biggest web project at the European Commission. He is a former technical lead and fan of open source technologies.
When it comes to defining success, Samantha shares with us a moving story that starts with a piece of feedback she once received from one of her team members. That’s what success looks like. But how do we get there? Samantha shares how she uses the retrospectives as the engine of learning for teams. And as a tool to help ground the teams in the core ideas of their agile journey, so that they can get back to basics when necessary.
Samantha is a Scrum Master based in London where she works with clients in a number of different industries. In her spare time she is a game writer and designer and uses Scrum to work on game projects.
What is the value the Scrum Masters are bringing in to the organization? Of course the investors and management are going to ask this question. I would too if it were my company. So we need to be able to show how we are helping the teams and the organization grow and become better. How do we do that? We measure the impact of our work, and Karthik shares with us some of the metrics we can use to show the stakeholders around us what it is that we are contributing to.
In this episode we discuss experimentation and evolutionary change using Popcorn Flow, a continuous improvement approach developed by Claudio Perrone.
About Karthik Nagarajan
Karthik has worked as a Product Manager, Scrum Master and QA Manager across a variety of domains, including: Fintech, Travel, Human Capital Management, CRM, Recruitment, Insurance, Banking and Financial Services. He loves tackling complex business challenges and being a positive bridge between Product, Design, Engineering, Quality Assurance, Customers and Business Teams.
All the teams we work with are doing their best. We believe so. And we also believe that certain mental models and practices are keeping them from doing much better, while still trying their best. In this episode we talk about the critical different developing software and releasing software. Releasing is a completely different problem. We discuss that and how to help teams get to the point where they can release software all the time, anytime something is ready.
A Scrum Master who specialises in Mobile and User Centred Design based approaches, Adrian comes from a testing background and he still finds that he champions making testing easier for the teams he works with. Due to that Adrian is also a strong advocate of XP practices (and, from that, BDD)
Jacopo describes in this episode 2 patterns that may lead to success, and can help you define your own success as a Scrum Master. In the scope of those 2 patterns we also discuss multiple metrics that could be useful in navigating our own evolution and growth as Scrum Masters.
About Jacopo Romei
Agile practitioner since 2003, entrepreneur more than once, he has been agile coach in eBay Italia, co-founder of the ALE Network and a former member in Cocoon Projects, an open governance based company. His main focus now are contracts and lean-thinking-compatible agreements.