image: Web project management

Regular Communication

"Projects can go awry for many reasons, but most often it is because of a lack of communication or misunderstanding. The fickle and changing nature of the Web, as well as the complex browser / platform issues, can confuse and frustrate anyone. Sometimes it can be as simple as misunderstanding a term, like template or design spec.

The producers (in this case a project manager) should speak with the client in person at least twice a week. In every conversation, review what you've completed, what you're working on now, and what's coming up in the schedule. Radio silence is a definite warning sign. Get them involved - discuss their level of satisfaction and comfort with the process. Have the client repeat the action items back to you. If they can clearly express what you've discussed, they've definitely understood you."

—Christina Cheney

"Programming requires the utmost concentration, which has ramifications for how the project is managed. It is beneficial to physically separate programmers from the rest of the development team - each in an individual office, if possible. The efficiency of a programmer who is subjected to frequent and uncontrolled visits by other team members will suffer greatly. Programmers must also be protected, to some extent, from the administrative and managerial demands of the project because these also represent significant distractions. This does to mean that programmers should be treated either like prima donnas or "techno-slaves," but, merely that it is wise to keep distractions to a minimum to allow them the needed concentration, so they can meet their deadlines and avoid making costly mistakes."

—Developing Effective websites: A Project Manager's Guide, Roy Strauss & Patrick Hogan