The general rule also applies when revising project plans from the outset - double the workforce does not necessarily result in double the productivity and in practice the larger the work force the lower the cost efficiency.
Not everything can be time compressed and typically it involves cutting corners to at least some degree - that in turn can result in increased project risk and reduction in quality of output (even when done carefully). If the work force can be split into effective and smaller teams working on independent parts of the product then the productivity impact of a larger work force on a given project can be mitigated to a point.
As a general rule of thumb though double the workforce does not equate to double the productivity, and there are some things that will take at least X time regardless of the number of people you throw at the problem.
And hence the old saying that I trot out the after time with my bosses, "you can't get a baby in one month by making 9 women pregnant". Crude but usually effective. Somethings take time and there's little you can do about it.
Nope, you are wrong - in fact one very vocal KS backer stated that no one from 'those days' still plays
snip
And said vocal KS backer is totally incorrect. I'm still here and still playing.