classroom.tripod.com was a major interface project that launched in conjunction with lycos' kid zone.
Of course, our product was better. Think Nickelodean. I really like this site, it's solid, easy to use, and useful too! wow! imagine that hugh? It's also the last project that had a good process which i'm outlining below (props to sean coon and jay patrikios for this --)
our process: this was the first time that we attempted our new process. it needed to happen at some point, but time was so short that it was hard. there are a lot of steps, but in a nutshell, this is the way should work:
1) the information architect (IA) is in the planning meetings and taking notes.
2) the IA would work with the producer to get a full list of what needs to be created.
3) the IA creates a sitemap of all the top level pages and gets sign off from the core team on it.
4) the IA and the user interface (UI) designer sketch out rough schematics of which content goes on which page.
5) the IA and UI designer polish up the schematics and present to the core team.
6) sign off on schematics.
7) from here, the UI designer works with a visual designer to get a look and feel to the site and make sure that the pages are usable, readable, concise, understandable and just make sense. engineering starts to code the back end and quality assurance (QA) writes their test plan for the site.
8) production engineers code a skeleton of the front end so that engineering can wire the back end to the front end.
9) visual design takes over design and runs with it, building photoshop mockups.
10) sign off on visual mockups.
11) final mockups go to the production engineers for coding.
12) the pages come back to the UI and visual designer for final tweaks.
13) hand off to QA.
14) QA tests the site for bugs/inconsistencies. if any are found, the problems get reported to the appropriate people (engineers/designers) for correction.
15) QA approves the product and it gets sent live.
|