Several weeks ago, I wrote about what to look for in a good Scrum Master, and today, I’d like to have a similar discussion about the team. More specifically, let’s talk about what makes for a high-performing team. It’s a common term, and it conjures up different images for different people. If someone were to join a team meeting, what would he or she see? What behaviors does a high-performing team demonstrate? Here’s how I answer those questions.
- Do we contribute at team meetings equally? Do we have the floor in roughly equal amounts? In other words, in a 60 minute meeting, does the six team member talk about ten minutes each? Try this. At sprint planning or grooming, listen for Product Owner. Is the PO explaining every story? Let’s hope not. Instead, our team members should feel equally invested and able to explain items from the backlog.
- What happens when consensus isn’t reached? Consensus isn’t necessary on a high-performing team. We trust our team members and value their opinions. Even if we decide to go in a different direction, that’s okay. Why?