homepage > process |
|
A process
for successful web based solutions
|
Over the
years we have developed a simple but powerful framework for
ensuring the successful implementation of your online project.
We like to think of this process as a flexible tool which
can be molded to fit the particular deliverables and scope
of your project.
|
|
DISCOVER
|
Determining the
basic purpose and structure of the online project. ›
BRAINSTORMING SESSIONS. Develop client questionnaire.
Identify project direction and develop concepts that promote
this. › DECISION
MAKING. Preliminary meetings produce 'requirements document'
that outlines the scope of the project and basic feature sets.
› RESEARCH. Competition
analysis. Programming feasibility. Audience analysis. Interface
design scenarios. Rough schematics.
|
| PLAN |
Its all about
the detail. Establish every element of every stage. ›
SCHEDULING. Begin scheduling and budgeting using
information from 'requirements document' research results,
tech and user interface › LAUNCH
DATE. Only rule is to never plan a site around a launch party.
› COMMUNICATION.
Establish a system of communication with stakeholders. Utilise
everything from a dedicated Intranet to e-mail. Establish
a culture of checking for updates, schedules and documentation.
Create a reliable server space for the project. Establish
passwords and permissions. ›
SITE MAP. Establish site structure. Sketching a
diagram forces stakeholders to consider issues prior to building.
› SCHEMATICS. After
client signs off on Site Map, create a simple visualisation
that describes how each page functions. Add details about
server, security, site structure etc. This document may need
to be reviewed several times with the client.›
DESIGN TREATMENT. Use the functional Specs and
Schematics as a guide for designing the pages. Include final
text, other content and initial comps. Ask client for feedback.
› STYLE GUIDE. The
guide details colour, fonts, size, graphic motifs and naming
conventions etc.
|
| INTEGRATE |
This is when
the bulk of the development is undertaken. ›
DOCUMENTATION. Successfully integrating the major
elements of the project depends on the documentation developed
during the Planning Stage. ›
TEAM. Make sure they stick to the plan. Ensure
the functional specs and style guide are being used. Also
consider proper use of naming conventions, version controls
and file backup.
|
| TEST |
Implement a simple
QA matrix describing the elements to be tested for. ›
Double Check. If changes are made check that new
problems have not come out of those revisions. ›
REVIEW. Meet with the team and the client. Find
out what worked and what didn't. ›
HAVE A PARTY.
|
 |
|
113A
ROKEBY ROAD. SUBIACO
