Bringing in all of these new outside resources is only going to slow this down too. There is a well known software management law known as Brook's law that identified this from work done at IBM.
[quote]Brooks's law: Adding manpower to a late software project makes it later. A man-month is a concept of a unit of work proportional to the number of people working multiplied by the time that they work; Brooks's law says that this relation is a myth, and is hence the centerpiece of the book.
Complex programming projects cannot be perfectly partitioned into discrete tasks that can be worked on without communication between the workers and without establishing a set of complex interrelationships between tasks and the workers performing them.
Therefore, assigning more programmers to a project running behind schedule will make it even later. This is because the time required for the new programmers to learn about the project and the increased communication overhead will consume an ever increasing quantity of the calendar time available. When n people have to communicate among themselves, as n increases, their output decreases and when it becomes negative the project is delayed further with every person added.
•Group intercommunication formula: n(n - 1) / 2
•Example: 50 developers give 50 · (50 – 1) / 2 = 1225 channels of communication.
This post was edited on 10/24 at 9:55 am