the development process      |     scoping and pricing a project

SCOPING a project (determining what exactly needs to be done/built) begins with STRATEGY...

What must the site do? How will we determine if it is successful?

In this discussion and exploration, MANY options and ideas can be brainstormed, but we are always limited by 3 factors, of which one can only pick two:

        1. High-Quality / Production Value
        2. Rapid Turnaround
        3. Low Budget

When we know what 2 factors limit the production, we can then set our eyes on the list of FEATURES and IDEAS brainstormed for the project and begin to prioritize them. One way of approaching this (that I picked up from the "agency" world) is to identify where the proposed features lie on a "Prioritization Matrix" like the one below:

Prioritization Matrix
Low Hanging Fruit: these initiatives are high priority and should be started immediately, as they are easy to implement and deliver the greatest value.
Differentiators: these initiatives will set your company’s Web presence apart from your competitors as they deliver the highest value. They are, however, the most complex to implement and therefore require long-term planning.

Building Blocks: these initiatives are easy to implement, yet give low value. As with differentiators, initiatives in this group must be chosen carefully to ensure they support long-term goals.
Dogs: these initiatives should not be developed. They deliver low value and are difficult to implement.

The FINAL SCOPE of the project defined is followed by a WRITTEN DESCRIPTION of the FUNCTIONALITIES as well as a SITE MAP, if appropriate.

It's a process that involves the client closely to ensure that the PROJECT: is what they want and need and within their MEANS. It is important to me that my clients and I both know exactly what we expect from each other so the development process is both a successful and positive experience.

A cashed check gets spent quickly, but a good client relationship can be mutually-beneficial for many years.

Payment Schedule

Upon agreement to work on a project, I usually require from 1/2 to 1/3 the Total Estimated Project Cost for initial payment to begin work. The balance of the Total Project Cost is usually due 10 days after the Beta Launch. This is also a practice that is open to discussion for clients with particular needs and limitations.


Denny Juge       /       Interactive Development        /       New Orleans        /       [email protected]