++ on the node, and sorry about the project.

I worked on a similar project some years ago, and your ideas are very sound. I would add a couple that I have learned along the way as well. These have been crucial in the joint projects I have worked on. Your mileage may vary:

Assign an Owner

Projects need an Owner, and someone who is, ultimately, responsible for the outcome. Loose groups seldom work unless the group has worked together for some time and knows the others habits and styles. You touch on this in "Who's The Boss" above, but I would advocate that a "Leader" per-say may not be the same as an Owner. With an Owner you have acountability and therein lays one of the secrets. Someone is accountable!

Get buyoff from Management

Present a plan to management, and don't start until you get paper signed buyoff. This can be tricky, and details may change, but getting approval can save headaches later. Your plan should include who will be the Owner of the project and what resources and/or authority the Owner will require. This may not end up being you! But if it is you, present a clear goal to your team, and modify it with their input. Ideally this is done before the buyoff from management.

I hope this gives some input and sheds some light for you. These are a couple things I use to keep my life sane when working on group projects.

"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!

In reply to Re: Failure To Refactor by Rex(Wrecks)
in thread Failure To Refactor by stephen

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":