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'!