Development teams have rallied around the Scrum process for many years now. Teams self-organise around a common set of goals to achieve outcomes at a pace and agility that often can't be achieved with other development approaches.
However, a common misconception amongst Scrum teams (and in fact business teams in general), is that communication is the be-all and end-all to collaboration and success. When in fact, too much communicate can stifle action, limit scale and increase risk of project failure.
This article introduces some interesting concepts, including ways to decide whether or not a meeting is worth your time based on the number of attendees or the 'pizza-principle'!
Less communication is better. The reason for this is that more communication doesn’t scale while just enough communication is essential for the high performance of a team and particular teams of teams. More meetings and more reports cause higher decision latency, the primary cause of project failure. Projects, where the average time it takes to make a decision is greater than 5 hours, have a success rate of just 18%. If decision times average less than one hour, project success rates rise to 58%
unknownx500
