Source: http://en.wikipedia.org/wiki/Brooks_Law
Brooks's law is a principle in software development which says that "adding manpower to a late software project makes it later".[1] It was coined by Fred Brooks in his 1975 book The Mythical Man-Month.
Determine if the project is really late, or if the schedu le was originally overly optimistic
Correcting the schedule is the best way to have a meaningful and reliable time frame for the project's completion.
The quantity, quality and role of the people added to the project also must be taken into consideration.
Good programmers or specialists can be added with less overhead for training
People can be added to do other tasks related with the project
Reduce the inter-developer communication overhead
New tools for software development and documentation also help to minimize the ramp up time
Design patterns simplify the distribution of work
good segmentation helps by minimizing the communication overhead between team members