What metrics can you use to evaluate your Scrum Master's performance?

1 Sprint Success Rate

One of the simplest and most obvious metrics to measure your Scrum Master's performance is the sprint success rate. This metric shows how often your team delivers what they committed to in each sprint, according to the definition of done and the acceptance criteria. A high sprint success rate indicates that your Scrum Master is helping your team plan, execute, and review their work effectively, and that they are managing the scope, quality, and risks of each sprint well. A low sprint success rate may suggest that your Scrum Master is not supporting your team enough, or that they are facing challenges with stakeholder expectations, technical issues, or team dynamics.

2 Sprint Burndown Chart

Another useful metric to evaluate your Scrum Master's performance is the sprint burndown chart. This chart shows how much work your team has completed and how much work remains in each sprint, based on the estimated effort and the actual progress. A smooth and consistent burndown chart indicates that your Scrum Master is helping your team break down, prioritize, and estimate their tasks accurately, and that they are tracking and reporting their work regularly. A jagged or flat burndown chart may indicate that your Scrum Master is not facilitating your team's work effectively, or that they are dealing with impediments, changes, or dependencies that affect their work.

3 Team Velocity

Team velocity is a metric that shows how much work your team can deliver in a given time period, usually measured in story points or hours. Team velocity can help you evaluate your Scrum Master's performance by showing how your team's productivity and efficiency change over time. A stable or increasing team velocity indicates that your Scrum Master is helping your team improve their skills, processes, and tools, and that they are adapting to changing requirements and feedback. A decreasing or fluctuating team velocity may indicate that your Scrum Master is not coaching your team enough, or that they are facing issues with quality, motivation, or collaboration.

4 Team Satisfaction

Team satisfaction is a metric that shows how happy and engaged your team members are with their work, their colleagues, and their Scrum Master. Team satisfaction can help you evaluate your Scrum Master's performance by showing how they influence your team's morale, culture, and retention. A high team satisfaction indicates that your Scrum Master is creating a positive and supportive environment for your team, and that they are fostering trust, respect, and empowerment among your team members. A low team satisfaction may indicate that your Scrum Master is not addressing your team's needs, concerns, or conflicts, or that they are not providing enough recognition, feedback, or opportunities for growth.

5 Stakeholder Feedback

Stakeholder feedback is a metric that shows how satisfied and involved your customers, users, and other stakeholders are with your team's work and your Scrum Master's role. Stakeholder feedback can help you evaluate your Scrum Master's performance by showing how they communicate, collaborate, and deliver value to your stakeholders. A positive and consistent stakeholder feedback indicates that your Scrum Master is ensuring that your team understands and meets your stakeholder's expectations, and that they are facilitating regular and constructive interactions between your team and your stakeholders. A negative or irregular stakeholder feedback may indicate that your Scrum Master is not aligning your team's work with your stakeholder's vision, or that they are not managing your stakeholder's feedback, changes, or issues effectively.

6 Scrum Master Self-Assessment

The last metric that can help you evaluate your Scrum Master's performance is their own self-assessment. This metric shows how your Scrum Master reflects on their strengths, weaknesses, and areas for improvement, and how they act on their learnings and feedback. A honest and proactive self-assessment indicates that your Scrum Master is committed to their own professional development, and that they are seeking and applying feedback from their team, their stakeholders, and their peers. A vague or defensive self-assessment may indicate that your Scrum Master is not aware of their impact, or that they are not open to change or growth.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?