Project Specification Development, Prototyping

The project specification is the planning team's concise statement of core goals, values, and intent, to provide the ultimate policy direction for everything that comes next.

Designing a substantial Web project is a costly and time-consuming process. When you're up to your neck in the daily challenges of the project, it can be surprisingly easy to forget why you are doing what you are, to lose sight of your original priorities, and to not know on any given day whether the detailed decisions you are making actually support those overall goals and objectives.

A well-written project specification provides the team with a compass to keep the development process focused on the ultimate purposes of the project. As such, it quickly becomes a daily reference point to settle disputes, to judge the potential utility of new ideas as they arise, to measure progress, and to keep the development team focused on the ultimate goals.

Businesses that need custom Internet applications use our web development solutions.

Clear ask

Developer knows exactly what is expected from them and so can quote accurately.

Happy clients

Client knows what they are getting for their money.

True basis

Forms the basis for a contract so that client gets what they pay for, and developer is covered for project scope.

Smoother process

Smoother process – both client and developer can plan and schedule accordingly.

At minimum, a good project specification should define the content scope, budget, schedule, and technical aspects of the Web project. The best project specifications are very short and to the point, and are often just outlines or bullet lists of the major design or technical features planned. The finished project specification should contain the goals statement from the planning phase, as well as the structural details of the project.

Common Elements for a Project specifications:

The following are often included in project specifications:

  • Introduction - description of project
  • Project Objectives
  • Functional Requirements Per User Role
  • Design Specifications - how things should look and feel visually, Wireframes for each page, PSD designs for each page
  • Flow or Logic Diagrams - for non-trivial processes like checkout or applications
  • Success Criteria - how to know if your website is doing its job
  • Detailed site map - the architechture, often in outline form, of the site content
  • Content Plan - type of content, and where content will come fro
  • Marketing Plan - how will the site make money
  • Site Maintenance - who will maintain the site
  • Project Timeline - desired timeline for completion (may be in phases for large projects)
  • Budget - how much your organization has set aside for the project