Whereas the first parts of this series introduced some technological aspects of website design, we now try to show some project management steps we should consider. The WSDM defined the mission of the site. The mission is the basis to decide the class of websites we deal with in an actual project. This may be one out of the following (incomplete) list classes:
Small static web presentation
This old school version is good for very small sites, graphically difficult sites with low level information content, mostly hand made graphics, and semi automatic code generation using Dreamweaver or something similar.
Dynamic web sites
This type is good for CMS because of its efficient features to maintain text and graphics, some restrictions in design.
Data base front-ends
They are good for large databases, mostly used for information systems like product catalogs or other searchable databases, low level graphics, high level information support.
Art work
Here, art and graphics design are of highest priority and any information provided is an integral part of the art work that has to be displayed. Such sites are not generated automatically, but normally many tools are used for handmade wonders of creativity.
Web Based Applications
This kind of website is the most functional one. Processes are implemented and data is processed, stored, and presented on a high level. Graphics are important but not a first priority. Presentations are normally done in a separate page that is displayed before entering the web-based application itself.
Community
The creation of a web community is technically not adventurous, but from the social point of view we need to pay close attention to details – miss one and forget the community.
These classes of websites are most common and about 90% of all websites may be covered by these classes. To establish an efficient project management system, we always need to remember that communication is most important for success. Teams for website design projects are normally very heterogeneous. You need to synchronize the creative processes in graphics design with the more concentrated text design. Both have to fit the marketing and psychological needs, have to be pictured by the data and process management structures, and programmers as well as network operators have to enable the technical equipment to support the creative ideas from the artists.
In other software projects this problem is apparently obvious, but there are other quotas. In a normal application development, we need about 5% to 8% for creation and implementation of the concept of usage. When there is a high level of graphics and detailed visual effects like in Mac front-ends, we deal about 12% of the whole implementation process to be used by graphics artists. In website projects the ratio is different. There we deal with about 1/3 of the implementation amount for graphics only. That’s why we need to do different planning, different communication, and different kinds of project structures than in pure software application development. Please keep this in mind when we discuss the different classes of web site projects in little more detail.
To manage such projects, be careful to select the right project management method (PRINCE 2 is very good, PMBOK as well, others are available up to special management methods designed only for web site projects). As important as the right choice of a method may be, we need to use a tool that will be accepted by programmers, designers, project managers, and system operators as well as by the customer. Thus, for website projects we always should think about using a web-based tool with good visuals and a high level of usability and great user support.
