Who to involve when evaluating our success as Scrum Masters? In this episode, we review the critical stakeholders, and how to involve them in our own self-evaluation.
In this episode, we refer to the Niko-Niko Calendar and the Happiness timeline, two of the tools you can you to evaluate your success as a Scrum Master.
Featured Retrospective format for the Week: What was good / bad and what actions should we take?
The Good/Bad/Actions format is a simple, yet effective format. Nisha explains how to facilitate this format in a short time frame and how Scrum Masters can prepare to host the retrospective.
About Nisha Balwatkar
Nisha started her career as a programmer for the love of logical reasoning and technology and soon found herself trapped in the mismanagement of software teams affecting the work and efforts put in by the teams. She always had a feeling she could fix it and eventually moved to be a scrum master. She enjoys helping out teams and see the joy of success by identifying and fixing small things.
You can link with Nisha Balwatkar on LinkedIn and connect with Nisha Balwatkar on Twitter.
There may be cultural differences at play here but I was under the impression (here in the UK) that using what was BAD encourages blame and finger pointing. If something was bad why did person A do it?
I always use the What Went Well, What Did Not Go So Well, What Changes We Want To Make format. This way we can identify things we do not like, did not work or want to change without any blame being involved.
Something being bad, does this not have a stigma attached where you are?
Good point Malcolm. You should always adapt the formats to your local culture. However, in some cultures, it is ok to talk about what went “wrong” or “bad”. Maybe this could be a good conversation to have with the team, so that we directly address the possible “blaming” behaviors and identify those clearly. When we are aware of the possibility of blaming, we are more likely to avoid those behaviors.