the development process      |     scoping and pricing a project

After 10 years of interactive development work, I've boiled down the Best Practices of the project development. I've worked with many different types of clients and in many different environments, and after all the different METHODOLOGIES that have been preached, here are the basic steps a potential client should expect:

When a client and I agree to work on a project, the following processes will occur:
(the steps may vary depending on the nature of the project)

Consultation
I start by acquiring as much knowledge and input up front as possible: I need to hear your insights and ideas, and understand your long-term goals. This is where STRATEGY and BRAINSTORMING come in strong.

Project Scope

After the Consultation, I work with the client to prioritize the features and functions of the project. From this, I clearly define the Project Scope (via a Project Scope Document) that will outline all specific design, technical, and administrative needs for the project. This will also allow me to refine the estimated budget for the project.
When the Project Scope is approved by the client, the next process may begin.

Architecture

I create visual schematics (Site Maps, Storyboards, etc) to illustrate project flow, scope, or functionality. This step more clearly defines exactly what CONTENT will occur and when. When approved by the client, the next process may begin.

Initial Delivery

The client provides me with all needed CORE assets of text, images, or other media for the site design process (logos or other specific elements the client may require).

Visual Design

I present to the client one or two "mockups" of proposed designs. These designs are then discussed with the client, and usually undergo a process of 1 to 2 revision-stages until the design is finalized.

Full Content Delivery

By this time, all other CONTENT required and outlined from the Architecture Process must be delivered to me by the client so development can begin. When completed by the client, the next process may begin.

"Alpha" Development

I develop the project according to the established design standards and Project Scope. This "alpha" site is presented to the client for revision, testing, and review. When all the feedback is given by the client, the next process may begin.

Site Revision and "Beta" Launch

I perform the project revisions, and then present the "Beta" site for FINAL review, and prepare for site launch.

Site Launch

When the last changes are made and the client gives the "thumbs up," we let the site or project go LIVE.


Assumptions
All the steps of the production process are dependant on the clients' approval. The Production Schedule and/or Budget may be adversely affected if:

  • the client is late or incomplete in their feedback
  • the client changes previously agreed-upon specifications (i.e. If the client and I agreed they want an animated product demo with sound and pictures, but then LATER asks for 3-D modelling and character animation, then the Project Scope has been changed, thus the Schedule and Budget may be affected.)

Fortunately, this has been a VERY rare occurrance, and I like to believe that effective client-communications have alleviated much of this potential problem.

Denny Juge       /       Interactive Development        /       New Orleans        /       dj@dennyjuge.com