Does your team GET collaboration?

A successful Groove project is about "collaboration". If one team member is dead set against collaboration then Groove may not be right for your team! A reason why Groove projects do not work is that a minority of the team do not "get", or even want to get collaboration.

The benefits of collaboration include:
- speeding up of the processes by
- removal of bottlenecks
- greater personal satisfaction to all players
- greater feelings of being part of a team
- better focus on the goal

If one or more team players (cough!) only play lip service to working in "a team" then Groove as a solution will not work. If a team player is not really a team player then they may need specific training. And if that fails you may need a replacement team member!

I often think that job interviews for team players ought to include "the Groove test". If an interviewee fails the Groove test then, by definition, they are not a team player. Certainly if your team is committed to Groove then there is no point having someone join the team who does not get it. If you have someone working in your project team who does not sign up to Groove then they can demoralise the whole team.

You need 100% support. 90% support does not mean 90% success, it means 100% failure. You need 100% support.

Groove is peer-to-peer at a technology level, but that is not all: it is is also peer-to-peer at a human level. Make sure your team can repeat that kind of thought as the team mantra.