you can find this page online at www.knectar.com/page.html
skip to content
Call us today:
413-587-3900
Featured Project
Knectar Blog Posts 
Knectar on Twitter:
Custom Search
SEO and PPC New York,
New Jersey, Philadelphia
Knectar Design and Development Process
A discussion of key, high-level processes in web-based media production, specifically as it relates to the agency-vendor relationship, with references to some case examples.
The stages outlined here correspond roughly, despite widely acknowledged limitations, to the "waterfall" model of project management, but applied specifically to "web development" of the kind that Knectar routinely engages in with its strategic partners.
Overview of the typical project stages
Stage 1. Proposal lead-up, scope definition, estimation
The challenge with estimation, is that most projects don't have the luxury of knowledge of 2. Detailed specification (below).
This makes estimation a challenge, because it puts us in the position of making an estimate on unknowns.
Our best strategy is to take as much time as is practical (given the likelihood of the sale), and to research related historical projects, review earlier actual projects costs, unanticipated incidents of scope-creep, and under-estimations. This matures the sales process as project experience accumulates.
Key elements to consider during the early stages of a project:
- As much as possible, consult with development partner (vendor) during the scope defining process
- Loop partner in during the creative briefing phase (sometimes earlier if consultation is needed)
-
Work with partner to define hurdles, dependencies and risks before project starts
- Schedule
- Technology
- Clear role definition prior to project start
- Main point of contact
Stage 2. Detailed specification
The more complex the software, the more challenging detailed specification can become.
What comprises a complete set of documentation?
For typical projects, there are three parts:
a. Specification or requirements document.
This general guideline is a resource that will be frequently referred to by the designer, and later on the programmer.
It includes the logic, content types defined, forms to be used, user roles defined (admin, end-user, customer, etc), and in general, describes all of the functionality of the site.
SIGN OFF: This document should be signed off by the client as a formal approval.
b. Site map / Wire-frames / Prototype
An abstracted visual representation of the specifications that prototypes the data, content types, key interface elements and user flow between views.
IA example which shows fairly complete user-flow: http://knectar.com/1/bizlink/wire/
or http://knectar.com/1/shmefty/wire/
SIGN OFF: The wire-frame, or site map should be signed off by the client as a formal approval.
c. Physical designs
(PSD's, AI files, etc). All views need to be represented with final, signed-off graphics.
SIGN OFF: The physical designs, mock-ups, or Photoshop files should be signed off by the client as a formal approval.
Stage 3. Production
- If the spec's (a), site map or wires (b), and designs (c) above are all ready and signed-off, the production can begin.
Stage 4: QA and Launch
- QA is typically done by the vendor, but a second round of QA is provided by the agency.
- QA includes functional testing and browser testing of the site.
Stage 5: Maintenance
- Open or closed-source software applications will always require some degree of routine maintenance due to variables such as
- server environment dynamics (e.g. upgrades to server)
- security updates (e.g. http://drupal.org/security)
- Such maintenance should be expected, and accommodated in the estimation stage in terms of budgeting.
