Applying Brooks' Law to Lines of Communication and Team Size
What's the solution when you find yourself heading a team that is falling behind schedule? The answer might not be as obvious as you think.
Join the DZone community and get the full member experience.Join For Free
In a Field Notes post from 2014, LeadingAgile consultant Andrew Fuqua considers Brooks' Law in the context of the Theory of Constraints. Brooks' Law is the adage that adding manpower to a late software project makes it later. Fuqua notes that Brooks observed people "and months are interchangeable commodities only when a task can be partitioned among many workers with no communication among them."
Effective communication is key to any project. When collaborative methods are used, like the methods guided by Agile principles, the level of communication among workers is higher than with traditional methods.
Teams using traditional methods generally have a hierarchical structure. Communication lines tend to be vertical, between the manager or team lead and the team members. Horizontal communication occurs between individual team members when they need to ask each other for help, but on the whole the team depends on indirect communication (such as documents) for the majority of routine communication.
Teams using collaborative methods generally have a peer structure. Documents are used to capture historical information and for static data. The dynamic communication necessary to develop the product is primarily direct, and all team members interact with all other team members throughout the day.
Lines of Communication and Team Size
In the last few years, people have been paying a lot of attention to this aspect of team effectiveness. A Google search for the phrase, lines of communication and team size yields about 412 million results. Here's one illustration (source: Lighthouse):
Most teams in large enterprises have between 10 and 20 members. Even at the low end of that scale, a team has so many lines of communication that progress is bound to be slow.
Predictably Irrational Management
Although Brooks wrote The Mythical Man-Month decades ago and managers have understood this principle for many years, the default response when a team falls behind schedule is to add more people. Why?
Dan Ariely explains why people make seemingly irrational decisions in his popular book, Predictably Irrational: The Hidden Forces that Shape Our Decisions. The phenomenon is familiar to those in the IT field. It's captured in the old saying, "No one has ever been fired for choosing IBM."
A manager won't be fired for adding personnel to a late project. It gives the appearance of "doing something." If the project crashes and burns, the manager can safely state that he/she did "everything possible" to save it, even to the extent of shifting funding and people from other initiatives.
Applying Brooks' Law
Way back in aught-and-six, give or take a season, I was the team lead for a software development project. We were an XP team of eight people. We were falling behind schedule.
My manager kindly explained the consequences of not meeting the date. He asked me how many more people I needed.
I suggested we remove two people from the team. He was surprised. He asked if some of the team members weren't pulling their weight. Was that the reason we were falling behind?
I explained that everyone on the team was doing fine. The problem wasn't that anyone wasn't pulling their weight. The problem was the communication overhead on the team.
As the illustration shows, a team of eight people has 28 lines of communication. A team of six people has 15 lines of communication. Less overhead.
My manager was skeptical. He told me if the idea didn't work, then it was all on me. His warning was not as scary as he may have intended it, because I understood Brooks' Law and (apparently) he didn't. I knew he was familiar with the book, but evidently he didn't believe it.
With a team of six instead of eight, we picked up the pace of delivery without any strain and we were on track to complete the backlog within two iterations.
If an individual manager is predictably irrational, then what happens when you have hundreds of managers, thousands of projects, and tens of thousands of technical workers? Predictably: Utter madness.
Every large IT organization I have seen so far in my career has had large project teams that spend almost all their time engaged in communication overhead of one sort or another. It is no exaggeration to say it takes weeks for such a team to complete a few minutes' worth of real work.
The typical response to slow progress is to add more and more people to the teams. Just recently, a client whose teams were already too large to get very much work done were falling behind schedule. Management urgently requested approval to bring contractors on board to speed things up. Now the teams have even less time to do real work, as they have to help their new colleagues learn the system and the procedures.
There's no chance the teams will meet their due dates. But no worries: The managers won't be punished. After all, they've done "everything possible" to catch up.
Brooks' Law is real. Be unpredictably rational: Use it.
Published at DZone with permission of Dave Nicolette. See the original article here.
Opinions expressed by DZone contributors are their own.
Cucumber Selenium Tutorial: A Comprehensive Guide With Examples and Best Practices
SRE vs. DevOps
5 Key Concepts for MQTT Broker in Sparkplug Specification
A Complete Guide to AWS File Handling and How It Is Revolutionizing Cloud Storage