Characteristics of High Performing Teams

Alex van der Star Door: Alex van der Star,  14-04-2016
Onderwerp: Agile Management   agile  Agile Coaches  Agile Coach  Agile Teams  Culture  Development Team  High Performing Teams  Scrum  Scrum Teams  Team Happiness  Team morale  What motivates people  zelfsturende teams  

How to create high performing teams

This is the first blogpost in a mini-series of three in which I explore actions that Agile coaches or Agile managers can take to create high performing teams. I focus on high performing teams that consist of knowledge workers creating a software product.

It looks like we are in the middle of a social revolution equal to the scale of the Industrial Revolution of the 18th and 19th century. We’re seeing more and more self-organizing teams that make their own decisions within boundaries set by organisational direction, strategy and/or vision. The benefits seem clear, teams that take ownership simply perform better. But what is exactly the mechanism behind this? Is setting a certain corporate direction and giving freedom to self-organising teams enough to end up with high performing teams?

To answer that question, I embarked on a small journey of research. In that journey, I explored:

  1. the characteristics of high performing teams;
  2. the needs of high performing teams, and;
  3. actions for Agile coaches or managers in Agile environments to achieve high performance in teams.

The characteristics of high performing teams

When embarking on the journey of identifying actionable items for Agile coaches or managers in Agile environments to create high performing teams, I needed a starting point. So, what are high performing teams and what are the characteristics of a high performing team?

A high performing team is first and foremost a team. The characteristics of a team, as opposed to a working group, can be formulated on the following eight topics, according to a Harvard Business Review article of July 2005 by Katzenbach and Smith:

In a team:

  1. leadership is fulfilled by shared leadership roles (in a working group, leadership is strong and clearly focused);
  2. members have individual and mutual accountability (in a working group, accountability is on individual level);
  3. the purpose motive comes from a specific team purpose that the team itself delivers (in a working group, the purpose motive is the same as the broader organizational mission);
  4. people work on individual and collective work products (as opposed to a working group, where members only work on individual work products);
  5. performance is greater than the sum of the individual bests of the team members (in a working group performance is the sum of the individual bests of its members);
  6. the meeting goal is to have open-ended discussion and active problem solving (in a working group it is efficiency);
  7. the focus of the meeting process is on discussion, decisions and real working together (in a working group these are discussion, decisions, and delegation), and;
  8. the measurement of effectiveness is directly done by assessing collective work products (in a working group it is indirectly measured by its influence on others).


After looking at multiple sources (source list included at bottom of blogpost), I identified the following characteristics of high performing teams:

  • The team has a specific team purpose that the team itself created
  • The team takes individual and mutual accountability. Each team member takes responsibility for the result obtained by the team as a whole.
  • The team works result-oriented, it is not the individual work product, but the collective work product that counts.
  • The team has open-ended discussion and decision making. There is real working together. The team vibrates with inter-team communication. Team members give each other constructive feedback on the way they work together and on behaviour. The team members are not afraid of conflicts.
  • All team members have a place where they can add the most value. Each team member aligns personal goals with the team goal.
  • Leadership takes place within the team; there are shared leadership roles. There is autonomy on task and on group-level.
  • The team makes extensive use of metrics, and takes fact-based decisions. Effectiveness is directly measured by assessing the collective work product.
  • The team itself comes up with improvement initiatives continuously. The team is willing to invest to become better.
  • The team itself achieves buy-in for implementation of innovation or maintenance work items. Team members share their ideas actively and the team cares for relationships outside of the team.
  • Team members are prepared to work together. There are healthy attitudes within the team. There are established rules for their way of working and the team has frequent, fun, team building activities.
  • The team manages its performance. Team members are able to identify the weakest link of the team and act on it, whether it be some process that does not work, or a team member who does not perform. The team is able to solve inter-team conflicts.
  • The team has a will to be technically excellent.
  • As times get tough, working together intensifies. Every team member has a strong loyalty towards the team.

Now that it is clear to what my understanding is of a high performing team, I will extract the needs of a high performing team from these characteristics in the next blogpost.


  • Van Amelsvoort en Scholtes Team Model
  • Tuckman 5 Phases of Team Forming
  • John Maxwell - 17 Indisputable Laws of Teamwork
  • The American Society for Quality’s International Team Excellence Criteria
  • J. Richard Hackman – Leading Teams
  • B. Overeem – Characteristics of a great development team
  • P. Lencioni – Five dysfunctions of a team
  • J.R. Katzenbach & D.K. Smith – The Discipline of Teams, HBR July-August 2005
  • What Google learned from its quest to build the perfect team – New York Times, February 28, 2016

The Scrum Master as an Impediment Remover

Barry Overeem Door: Barry Overeem,  07-04-2016

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

In a series of blog posts I will share the different stances I consider to be relevant for the Scrum Master. This blog post is about the Scrum Master as an impediment remover. I'll describe the most common definitions and examples of an impediment, the Scrum Master as an impediment remover and tactics to deal with impediments.

Project Mindset or Product Mindset?

Barry Overeem Door: Barry Overeem,  23-03-2016
Last week I participated in a Product Owner course facilitated by Gunther Verheyen. What triggered me was the part where we discussed the difference between having a project- or product focus. I've seen many organizations, Scrum Teams and especially Product Owners struggle with finding the balance. In this blog posts I'll share my thoughts about the difference between having a project or a product mindset.

The 11 Advantages of Using a Sprint Goal

Barry Overeem Door: Barry Overeem,  06-03-2016

When facilitating a Scrum Master training, the Sprint Goal is a topic that often causes a good discussion. Participants question the background, purpose and advantages of using a Sprint Goal. In this blog post I'll describe the concept in more detail, explain why using a Sprint Goal is important and how to choose an efficient goal.

The 5 Most Common Pitfalls of Every Scrum Event

Barry Overeem Door: Barry Overeem,  28-02-2016
This week I facilitated a Scrum Master training in which we gathered the most common pitfalls of the Scrum events. It resulted in a nice overview with lots of recognizable pitfalls. In this blog post I'll share the results with you, completed with some ideas of my own. As you will see, it's only a brief description of the pitfalls. It doesn't contain detailed advice on how to deal with them. Currently I'm writing a white paper about the Scrum events, and for sure this will contain some practical advise on how to handle these pitfalls!

The Characteristics of a Great Scrum Team

Barry Overeem Door: Barry Overeem,  24-02-2016
Scrum is a framework within which people can address complex problems, and productively and creatively develop products of the highest possible value. It's a tool organizations can use increase their agility.

Within Scrum self-organizing, cross-functional, and highly productive teams do the work: creating valuable releasable increments. Hereby Scrum offers a framework that catalyzes the teams learning through discovery, collaboration and experimentation.

A great Scrum Team consists of a Product Owner that maximizes value, a Scrum Master that enables continuous improvement and a Development Team that focuses on delivering high quality increments.

For sure this sounds great! But what are the characteristics of such a great Scrum team?

Scrum & Business Intelligence

Barry Overeem Door: Barry Overeem,  17-02-2016

A couple of months ago Sander van Schaik and I discussed the idea of writing a series of blog posts about our experiences of Scrum and Business Intelligence. In the end, it resulted in a white paper. It contains 8 actionable insights related to the main question: "How to make Scrum and Business Intelligence a winning combination?" The white paper doesn't contain any in depth BI analysis. We've focused on individuals, collaboration and the process. Not all insights are strictly relevant for BI; we’ve just discovered them within a BI context.

Below you'll find the introduction of the white paper. If you're interested, you can download it via this link.

I hope you'll enjoy it. Questions and feedback are always welcome!

Scrum Webshop