Every engagement begins with a written proposal, or "Determination of Mission Need." This document clearly describes our understanding of what you wish to accomplish. Upon Acceptance, we enter project development.

Our Web project development uses the Unified Process method of project development. This is an iterative approach to application development. This process is used whether you want a single HTML page developed, or a large multi-page site. Only the amount of time and degree of documentation varies with the size of the project. The detailed planning and execution is always the same.

Every project has at least four phases. These phases are Conception, Demonstration, Construction, and Production as depicted in the following table.

Each phase strives to achieve specific goals with a measurable Milestone:

Conception Phase - We call this Phase 0 because it is, after all, ground zero for this effort. A shared vision of the project is developed with the client. This phase produces a vision statement, a risk assessment, a project structure document, or a conceptual model. This project phase culminates in the Demonstration Approval Milestone.

Demonstration Phase - Phase I is responsible for developing the baseline architecture. This phase produces a detailed Project Plan that can range from a multi-page document or a simple prototype of the finished product. This project phase includes testing and client acceptance. This project phase culminates in the Development Approval Milestone.

Construction Phase - Phase II has a focus on creating the product with incremental releases, if appropriate, of products and features of the engagement. This project phase culminates in the Production Approval Milestone.

Production Phase - Phase III ensures that the product or feature is ready for release to the user or web site. This project phase culminates in the final product. Occasionally, once the product is ready for release modifications may be requested such as fancier graphics, or breaking a page into two or more linked pages. This produces an additional Milestone of Modification Approval.

Some projects may require that we remain involved into a Phase IV involving internal operation and staff support for the project.

The important thing to note about the Milestones described above is that they are meant to serve as an efficient communications tool to the client. In this context, a Milestone (or deliverable) does not necessarily result in a paper artifact. A milestone deliverable can take whatever form is appropriate (a document, a diagram, an application, a screen-shot, email, etc.) so long as it facilitates communication so that there is a clear understanding between the client and the project manager on the status of their engagement project.

To learn more about what we can do for you, also visit our Consultation and Pricing areas.