That might work if the "project" is full spec'ed and defined as if it were the output of a Waterfall design process. I can't imagine that most projects are actu

That might work if the "project" is full spec'ed and defined as if it were the output of a Waterfall design process. I can't imagine that most projects are actually like that, though. Having a good PM ensures that when ambiguities arise, they can be solved in a single way to allow those doing the coding to continue on unaffected. Having 10 different people "take ownership" of a single project is itself a recipe for a different type of disaster.