« Notes on GameCity | Main | Embarrassed of "Games" »

November 27, 2006

Comments

Paul Sinnett

What you've found backs up the existing evidence about pair programming. (A closer fit might be slightly more than half the time but with less mistakes along the way; perhaps correcting mistakes is quicker with crosswords.) This doesn't exactly contradict Brooks' law, as I understand it, because that came from large projects with many programmers.

Unfortunately the pair programming experiments I've seen focus on comparing pairs working together vs pairs working apart. Perhaps a more interest test would be teams of 6 pairs vs teams of 12 individuals?

Or maybe you could see how long it would take if you had n people trying to fill the crossword together? Is the relationship linear (t/n) or something else?

Idea for a game experiment: "Collaborword." You play through the web and fill answers against the clock. When all the answers are in it tells you how many words are wrong (but not which ones.) Any size of team can compete on one puzzle.

Rob Drimmie

An important element of Brooks' Law is that the additional manpower you're adding are to a late project.

To use the cryptic crossword example, if you had completed 80% of a puzzle and your wife came in, at that point would you finish it any faster than if you'd just kept going yourself? Or would the time it would take to get your wife up to speed on the particulars of that puzzle take more time?

An implicit assumption to Brooks' Law is that the project is properly staffed to begin with. It is ultimately an argument in favour of proper planning and scope assessment, not one for starving a project of necessary resources.

eh

You don't seem to understand Brook's law. A crossword puzzle is not a late software project. Brook's law does not say more people always work less efficiently.

Jamie Fristrom

Okay, so forget about Brooks' law, which is "Adding programmers to a late software project makes it later" - which isn't even true (which Fred Brooks himself admits) - I've added programmers to projects that seemed late and brought them in on time.

Let's go with another law, which you'll find in most management books, I reckon, but I can't attach a name to it - "Adding more manpower to a team makes it less efficient." I'm just pointing out a couple exceptions to that law - mostly for my own benefit, because I tend to forget there are exceptions.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Your Information

(Name is required. Email address will not be displayed with the comment.)

Jamie's Bragging Rights

  • Spider-Man 2
    The best superhero games of all time Game Informer
    Top five games of all time Yahtzee Croshaw
    Top five superhero games of all time MSNBC
    Top 100 PS2 games of all time Official Playstation 2 Magazine
    1001 Games You Must Play Before You Die Nomination for Excellence in Gameplay Engineering Academy of Interactive Arts & Sciences
  • Schizoid
    Penny Arcade PAX 10 Award
    Nominated for XBLA Best Original Game
    Nominated for XBLA Best Co-Op Game