What is a scrum master? Many of us have heard the same definitions…process facilitator, teacher, coach, servant leader. While these are all important aspects of the scrum master job, these attributes fall short of describing what the role really means.

In a nutshell, the scrum master role is focused on cultivating engaged, productive, high performing teams. They influence without authority, lead processes over projects, and guide based on a set of values versus a set of numbers. The scrum master role is not easy, but it is one we need now more than ever.

“We have to stop the churn on our teams.”

At AgilityHealth®, our team has always believed there’s a relationship between qualitative metrics (defined by maturity) and quantitative metrics (defined by performance or flow) for teams. To prove this, a few years ago, we adjusted our Agile team assessments to gather both qualitative and quantitative data. Once we felt we had
sufficient data to explore through our AgilityHealth platform, we partnered with the University of Nebraska’s Center for Applied Psychological Services to undertake a review. The main question we wanted to answer was: What are the top competencies driving teams to higher performance?

At AgilityHealth®, we believe healthy, high-performing teams are the most mature. Healthy teams are those that are sized appropriately with skilled team members who understand their roles and what is expected of them. These teams are able to self-organize around the work and members are T-shaped, which enables each to contribute to the work. 

High-performing teams take these items even further and work together to find creative and innovative solutions while breaking the work down into smaller increments of value they then deliver on schedule. Improving team maturity takes time and it begins with measurement.

There are numerous ways to measure the success of Agile teams within an organization. Some companies rely on metrics tied to the team’s performance, such as how many story points are completed over a sprint or how few escaped defects the team’s work creates. Another way to gauge the success of a team is by looking at their churn rate, or the stability of the team. Still another measure is often focused on feedback from the team’s leadership and internal or external customers.

For organizations implementing or that are already using Agile, assessments focused on asking the right questions provide insights that indicate what is going on within teams, product lines, portfolios or throughout the enterprise, whether team members are in the office or distributed. Agile assessments create transparency for leaders by identifying obstacles to remove and opportunities to grow. As a result, teams can reach their highest potential and organizations thrive in their Agile transformation journey.

At AgilityHealth®, our team has always believed there’s a correlation for teams between qualitative metrics (defined by maturity) and quantitative metrics (defined by performance or flow). A few years ago, we adjusted our Agile team assessments to gather both qualitative and quantitative data. Once we felt we had a sufficient amount to explore, we partnered with the University of Nebraska’s Center for Applied Psychological Services to review the data through our AgilityHealth platform. The main question we wanted to answer was: What are the top competencies driving teams to higher performance?

One of our large financial services clients needed immediate help. The company was struggling to meet customer demands and industry regulations and needed to align business priorities to capacity before it was outplayed by competitors. They thought the answer would be to invest in Agile practices. But so far, that strategy didn’t seem to be paying off.

Measuring the health and performance of just one team to gauge their maturity and help them grow requires many resources including establishing a method of measurement, time for the team to complete the assessment, someone to help the team analyze the results and establish a growth plan to move forward, and much more. Multiplying those efforts across all teams in an organization can seem daunting. But does it have to be?