According to Brooks Law all projects reach a point where adding man power, for a variety of reasons, is actually detrimental to the project itself. This same principal is true during IT "emergencies". During emergencies there are those that are handling the problem and those that aren't. Usually those that aren't are on other projects or are tied into meetings.
When these people finally leave meetings, or decide to get involved, they often attempt to direct others on what needs to be done, not realizing that the situation is already under control. The resultant cross talk, catching up and general chaos exacerbates problems.
During physical fires in the real world, late arriving firemen and their chiefs don't rush into the situation and start directing others. Doing so can cost lives.
Late arriving personnel will follow the direction of those already present until such a time as they can take appropriate command. Doing so saves lives.
IT personnel could could be well served to learn to handle their "emergencies" by watching members of emergency services deal with actual emergencies.
- ThatGuy
Monday, April 12, 2010
Monday, April 5, 2010
First Post
The purpose of this page is so that I can post Rants about 3 things:
- Crappy code I have found / run in to
- Awesome code I've seen or written
- Unique issues I've experienced myself (with hopeful solutions)
With this, I am sure there will be some great references to sites, and other things I find. Hopefully you enjoy it :D
-Henry
-Henry
Subscribe to:
Posts (Atom)