Something that never ceases to humor me is how managers still believe that scaling people on a project will increase the productivity by an equal proportion. We all know the old saying, “You can’t make a baby in a month by getting nine women pregnant”, but the question is why do we still practice this bad habit? Is it because we do not recognize the the law of diminishing returns when it occurs?

I have talked about Brook’s Law before and that adding people to a late project makes it later, so as not to repeat myself I want to look at this from a different perspective and instead of telling how to avoid it, ask the question why this phenomenon slows efficiency and creates a Claustrophobic Team.

Claustrophobic people show anxiety and panic when they fell they are being locked in or their personal space is encroached; however, this encroachment can happen at many different levels on an overly staffed team:

Intellectual Space Encroachment

The DBA doesn’t want anyone else to touch the database without 7 written forms of consent because that is his job and space. The project manager who wants you to call every time you need to use the restroom. The client who does not want to be told a more productive process work flow.

We have all been on a team where people like to protect their intellectual sandbox. We fence these spaces primarily out of:

• Fear of not being needed or under utilized
• Ego and the need to be important
• Self esteem and the need to be appreciated

Everyone wants to stay busy and when people stack up on each other intellectual boundaries tend to be less respected and therefore encroached. As long as the work is getting completed in any one sphere attempt to respect the roles of individuals even if they do create a slight inefficiency as the inefficiency of having them work against you is greater.

Virtual Work Space Encroachment

For the software developer, you can read – code.

I have always had the belief that collective code ownership is just as a dangerous extreme as team silos. There is always some level of expertise in particular areas of the application and thus pseudo ownership, buy anyways I digress…

To many people working in the same area of the application can create a huge amount of churn. This overhead can be as simple as extra communication or complex as continuous code merging. Two people working in the same class file is a headache, three people working in the same file is just mayhem.

Especially in environments where intellectual thought is being transcribed, people need a few degrees of freedom in which to explore and modify. Unless you are pair programming, having more than one person work at a time on the same section of an application may start to become disastrous.

Physical Space Encroachment

Whether you realize it or not physical space encroachment happens a lot in claustrophobic teams. Just because you still have your desk and the office hasn’t become “standing room only”, does not mean that you aren’t feeling the pressures of encroached personal space:

• Increased communication means more people interrupting you whether through email or a face-to-face chat
• Kanban boards (and online issue trackers alike) become overloaded, hard to navigate, and harder to interrupt visibility
• Offices can become more densely populated when consultants or other workers come in to aid.

So what is the answer to all of this? Well, I am going to be very cliche and say – it depends.

Different businesses, teams, and people all have different thresholds of team claustrophobia and need to be dealt with accordingly. However, it is the responsibility of the team lead to recognize the symptoms of an overly staffed team and realign project expectations while not moving more people.

If a man is offered a fact which goes against his instincts, he will scrutinize it closely, and unless the evidence is overwhelming, he will refuse to believe it. If, on the other hand, he is offered something which affords a reason for acting in accordance to his instincts, he will accept it even on the slightest evidence. The origin of myths is explained in this way. – Bertrand Russell

When applied to business, this quote shines so much light on why there can be a resistance to change. Attempting to make company changes with a push mentality rarely works and really requires the pull model of a crafty salesman.

Just remember that when trying to pull people into your way of thinking, you need to be selling them solutions to their problems and not yours.

1. When Chuck Norris throws exceptions, it’s across the room.
2. All arrays Chuck Norris declares are of infinite size, because Chuck Norris knows no bounds.
3. Chuck Norris doesn’t have disk latency because the hard drive knows to hurry the hell up.
4. Chuck Norris writes code that optimizes itself.
5. Chuck Norris can’t test for equality because he has no equal.
6. Chuck Norris doesn’t need garbage collection because he doesn’t call .Dispose(), he calls .DropKick().
7. Chuck Norris’s first program was kill -9.
8. Chuck Norris burst the dot com bubble.
9. All browsers support the hex definitions #chuck and #norris for the colors black and blue.
10. MySpace actually isn’t your space, it’s Chuck’s (he just lets you use it).
11. Chuck Norris can write infinite recursion functions…and have them return.
12. Chuck Norris can solve the Towers of Hanoi in one move.
13. The only pattern Chuck Norris knows is God Object.
14. Chuck Norris finished World of Warcraft.
15. Project managers never ask Chuck Norris for estimations…ever.
16. Chuck Norris doesn’t use web standards as the web will conform to him.
17. “It works on my machine” always holds true for Chuck Norris.
18. Whiteboards are white because Chuck Norris scared them that way.
19. Chuck Norris doesn’t do Burn Down charts, he does Smack Down charts.
20. Chuck Norris can delete the Recycling Bin.
21. Chuck Norris’s beard can type 140 wpm.
22. Chuck Norris can unit test entire applications with a single assert.
23. Chuck Norris doesn’t bug hunt as that signifies a probability of failure, he goes bug killing.
24. Chuck Norris’s keyboard doesn’t have a Ctrl key because nothing controls Chuck Norris.
25. When Chuck Norris is web surfing websites get the message “Warning: Internet Explorer has deemed this user to be malicious or dangerous. Proceed?”.

Got any more? Comment them below…