Scrum Masters must pay attention to how Scrum teams adhere to the Sprint Goal, how they collaborate with the Product Owner and other aspects that help teams perform.
In this episode, we talk about 5 different success metrics for Scrum Masters.
Featured Retrospective Format for the Week: The Sailboat Retrospective Format
Scrum Masters usually have multiple retrospective formats in their “back-pocket”. The Sailboat Retrospective format is one that is easy to setup (a flipchart and markers/post-its are enough), and can engage the team in a creative assessment of their ways of working.
About Nedeljko Damnjanovic
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
For Scrum Masters, success must include the team’s success. In this episode, we talk about the metrics and the type of feedback we must help teams collect, and how to use that to measure our Scrum Master success as well.
Featured Retrospective Format for the Week: I Like / I Wish and other games
Sometimes Scrum Masters must focus on helping teams feel at home, so that team members can discuss the issues that bother them. In this episode, we talk about how a CEO/CTO can derail a retrospective and what kind of games we can use to help teams focus on improving, even when managers are present in the retrospectives. The retrospective format we talk about is “I Like / I Wish”.
In this segment, we refer to Retromat, a service that helps you choose games/activities and plan your retrospective.
About Henrique Centieiro
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
I am a big believer in continuous improvement, weather that be in the form of Retrospectives, a Kaizen approach, or something else that helps the team reflect regularly. But for the earlier years of my career as a Scrum Master I found myself frustrated by a lack of improvement despite all this reflection (retrospectives that have no impact…).
Often,what I was seeing was that we talked about the problems the team was facing, and then didn’t follow-through with the actions we agreed to take.
When we tried to change our behavior. We might have succeeded for a day or two and then would forget about it. This isn’t continuous improvement this is just continuous discussion!
We need a good way to make sure we are actually making the change we set out to make!
Ajeet has come to value 4 specific ways to measure his impact as a Scrum Master. In this episode, we review these 4 benchmarks and how he uses them regularly to improve his approach.
Featured Retrospective Format of the Week: Well/Stop/Start retrospective format
In the Well/Stop/Start retrospective format (see a facilitation guide here), we have a simple format that can trigger important conversations. Especially when team members see each other’s contribution to those 3 categories.
This is a format that suits very well teams that are action-oriented, and have a high degress of collaboration already.
About Ajeet Singh
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.