What exactly is in a process, methodology, or life cycle? A lot when you're talking about managing a Web project. Whether it's a small Web site or a large e-commerce site, without a process, you're very likely to run into trouble. It is rare to find two projects that are exactly alike. Yet, when closely analyzed the process is almost always the same.

I've worked as a Web project manager, or Producer, as we're sometimes called, for the past several years. I've been involved with projects that have had a variety of methodologies and processes.

One of my most memorable projects was one that I inherited from a coworker. It was a Macromedia Flash site for the Intranet. It was supposed to be simple and straight-forward. Yet, no one seemed to know exactly what the site was to do. Apparently, because the project was so small, no one bothered to gather the requirements. This was the first time that it dawned on me how important the life cycle process really is and how it affects a successful project.

Web project management doesn't have to be complex. Like other forms of project management (i.e. advertising or software), there are steps you need to take to bring the project in on time and on budget. There will always be issues that arise unexpectedly. It's the ones that you can anticipate that you need to plan for. In the long-run, planning (and good project management software) will improve your chances of delivering a successful product to your client.

Here is the simple, yet standard process of a Web development project.

Phase I - Requirements - Gathering requirements, or defining your project, is the first thing you should do. This is one of the most crucial phases. The following key questions should be answered: What is the objective of this project and who will be the audience? At the end of this stage, everyone involved with the project should have a clear understanding of what is being developed, for whom it is being developed and why. You should always get your client's approval before moving on.

Phase II - Design - Once you have determined the site's requirements, it's time to move on to the design phase. The architecture is developed during this time. There are two sides to this phase: the creative side and the technical side.  The developers will design the back-end applications needed for the site while the creative designers will work on the look and feel (also known as the user interface). Security issues, content planning and navigation are all determined during this phase. Once again, it's imperative that you get the client's approval before moving on to the development phase.

 Phase III - Development - Finally, the phase that you've been waiting for! It's time to begin building the site. If you've done a thorough job in the first two phases, you already know what the site will do, what it will look like, and how it will work. Everything comes together during now. It is definitely a milestone in the project. 

Phase IV - Testing/Maintenance - The site is tested for glitches or "bugs" during this phase. A Quality Assurance (QA) team usually does this. The team should be checking for the specifications or requirements that were outlined in the requirement phase. This includes back-end functionality, navigation, and site performance. After the site has been thoroughly tested and approved (usually by the QA manager), it is ready to go "live". This is just the process of transferring the site to the production server. 

By now, you have a well-developed site on the World Wide Web. This doesn't mean that your job is over. Maintaining a Web site is a never-ending job. You must keep your content fresh to keep your visitors coming back.

 As for the Macromedia Flash site that I mentioned earlier, we were able to get it under control. In the end, the client was happy and I never attempted to take on a project that didn't have a process. With that I mind, I must say that the old adage still applies when developing Web sites: communication, communication, communication. The key to successful Web project management is making sure that everyone knows what is going on at all times.  You must communicate with your team and client(s). Your project (and your sanity) depends on it!

Stacey Williams was a Web project manager at Morgan Stanley until earlier this year. She is currently a freelance Web designer and the co-founder of CyberOptima, a software development start-up company. She can be reached via email at Stacywillia@cs.com.

Do you have comments or suggestions or other ideas in this field? Give us your feedback.