Quote:
Originally Posted by davidthefat
"adding manpower to a late software project makes it later" -http://en.wikipedia.org/wiki/Brooks%27s_law
"If anything can go wrong, it will." - http://en.wikipedia.org/wiki/Murphy%27s_Law
Remember those: too much people = bad.
It can be even thought of as a
People vs Work done chart.
It would be a parabola, you need to find the balance |
Murphy doesn't have a manpower bias, though; he doesn't really play into absolute team size. So it's true, "too" much of anything is bad. That doesn't mean a conventionally (or even arbitrarily) "large" number of students is bad. The key is to have something productive and engaging for them to do, and the infrastructure (mentorship, equipment, communication) for them to do it.
As to the OP, I'd say if you've got the mentors--both in number and in dedication--give it a shot. Consider what everyone wants to and can do and decide your concentrations (animation, Chairman's, etc). Run mock sessions. Try to develop and practice with the system before kickoff. (Actually, try to do everything before kickoff. That's not illegal, of course.) It is a manpower-work balance, but the number of people isn't the only independent variable.
Also, this may be obvious, but 80 students means you'll want parents involved. And don't underestimate the need or value of NEMS.
