Nisha Balwatkar on 2 tools to help measure your Scrum Master success

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.

2 thoughts on “Nisha Balwatkar on 2 tools to help measure your Scrum Master success”

  1. 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?

    1. 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.

Comments are closed.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works