You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Integration: why splitting a project between more people is work too

Brooks's law: why adding people makes a late project later

Brooks's law: why adding people to a late project makes it later

It sounds wrong to most bosses: a late software project, more skilled people, and a later finish. Fred Brooks put it in one sentence in 1975, and he called it far too simple himself.

  1. 1 Your boss counts seven skilled people, where there were three, and race day has not moved. To your boss, that means the app will be early.Seven people!We'll finish early.race dayyour boss

    Your boss counts seven skilled people, where there were three, and race day has not moved. To your boss, that means the app will be early.

  2. 2 You are less sure. The new people bring help, and they bring costs too. On a late project, what matters is which of the two comes first.race dayHelp, yes.But when?you

    You are less sure. The new people bring help, and they bring costs too. On a late project, what matters is which of the two comes first.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode When adding people to a project does help

Share this comic

More comics