Well he explains pretty well why adding people (any kind of people) won't work. To summarize it in one phrase: communication overhead. You need to educate tech

Well he explains pretty well why adding people (any kind of people) won't work. To summarize it in one phrase: communication overhead. You need to educate technical writers and testers on what the system does, but this is the easy part - you also have to allow for a period of transition of organization to accommodate all the new folks, that means education of the original team who is probably already panicked and stressed out.. There are two ways you can go about it IMHO to prevent total loss - triage the features and roll the thing out ASAP. Or you could try to make the most of situation by indeed adding people - but not in parallel since this will only increase the confusion. I would assign apprentices to the original team and branch off later. In a situation like this you have to accept that you have screwed up and that there are no short term solutions. In longer term you can try to prevent similar mistakes. Once the torpedoes are in water no amount of wishing is going to make them disappear. Time to tie down cargo and brace for impact.