PDA

View Full Version : Maximum Project Resources Question



lamar_air
August 14th, 2007, 04:01 PM
What is the software engineering term used to describe the problem where a limit can be reached of the number of people working on a project and if that limit is reached or exceeded then nothing is gained in terms of increasing the speed a project is progressing? I thought I remembered hearing a term used to describe this problem but I can't think of it...

thanks!

LaRoza
August 14th, 2007, 04:14 PM
What is the software engineering term used to describe the problem where a limit can be reached of the number of people working on a project and if that limit is reached or exceeded then nothing is gained in terms of increasing the speed a project is progressing? I thought I remembered hearing a term used to describe this problem but I can't think of it...

thanks!

Sounds like "Brook's Law", but that may not be what you are looking for.

http://en.wikipedia.org/wiki/Brooks'_law

This was refined in "The Cathedral and the Bazaar" to account for the success of Linux and GNU software. (It took into account communication.)

pmasiar
August 14th, 2007, 04:15 PM
http://en.wikipedia.org/wiki/Diminishing_returns
http://en.wikipedia.org/wiki/Amdahl%27s_law
http://en.wikipedia.org/wiki/Brooks_Law

lamar_air
August 14th, 2007, 04:29 PM
It must be Brook's Law however I thought there was a more general term for it as well.

AlexThomson_NZ
August 14th, 2007, 10:51 PM
A more general term would be the law of diminishing returns, which basically states each time you add a resource, the benfit gets smaller each time.

aks44
August 15th, 2007, 12:48 AM
<Slightly OT>

There's also a related fact to take into account...

Adding a resource at the start of the project will probably enhance productivity, granted.

However adding a resource around the middle/end of a project, hoping that it will enhance productivity, will for sure have the reverse effect. You'll have to teach the new recruit all the whereabouts of the project, which will waste the time of the other experienced people.
Not to mention the potential for introducing bugs due to the new recruit's limited knowledge of the project.