Little more complex than just throwing more man power at a project. Actually throwing more people on a job tends to slow things down more often than speeding it up. Assuming the project wasn't horribly understaffed to begin with.
Getting a large number of people working effectively on a project is a monumental task. After all, if you get too many people working in a small area then you face a range of risks: Health and safety, accidents are easier to occur. Wasted time, people spend more and more time waiting for others to get out of the way so they can do their job.
(On a related note is the issue of the mythical man month. The commonly accepted myth that adding more people to a project that is falling behind helps. Most common in software, you throw new people at a project, and they don't know what is going on, they have to be trained, they're not in sync with the rest of the team, etc. In the end, you waste tons of money and you don't get any closer to your deadline.)
Being able to divide tasks up into parallel jobs, and timing their completions is a really cool and complex tasks.
If you're interested, read up on Just In Time processes. Very cool.
Originally Posted by Lrrpie-CT
I destroy drives for clients all the time. Sometimes, intentionally.