Teams

[Troy Rollins]

On Thursday, August 7, 2003, at 12:09  AM, SimPLsol at aol.com wrote:

> I have managed projects with up to 30 people spread over half the 
> globe. It is never easy but some things help:
> 1. Define the overall project thoroughly at the beginning! This is the 
> most important thing but often overlooked. The last thing you need is 
> for creative people to improvise as they go along.
> 2. Divide the work into well-defined elements, one per person.
> 3. Allow only one editor.
> 4. Set scheduling expectancies.
> 5. Use the phone (even calls to New Zealand cost less than rework).

No doubt. Though there is a huge benefit if the authoring system 
actively supports team development - especially if project managers do 
not wish to have project management be 100% of their job.

Synchronization of updates is one specific area that suffers without a 
server based and modular solution.

The stack model for development is an obstacle to such modularity, and 
best suited to developers who work alone or in projects which have a 
more linear timeline of development, it seems.

--
Troy
RPSystems, Ltd.
http://www.rpsystems.net