Emma's workflow
Emma is a total nerd! She's designed her own workflow model!
Yeah, that was me writing in third person again. Here's a breakdown of how my model works:
1. Client interview/questionnaire
I get together with the client at the start of the project and discuss in detail exactly what they need.
2. Planning
Using the information I've collected, I create a set of planning documents:
- project plan
- scope document
- work breakdown structure
- schedule
- list of required resources
These documents are presented to the client for approval and revision.
3. Design
The design phase is broken down into the following sections:
- requirements definition: current and future requirements of the project
- user experience: target audience, usage scenarios and competitor analysis
- site content: content grouping and functional requirements
- site structure: site structure listing, architectural blueprint, and navigation systems
- visual layout: wireframes, design sketches and page mockups
These sections are developed and discussed with the client, then combined into a design document which is submitted for final approval.
4. Development
Depending on the size of the project, development may be completed in one or two sections.
For small projects, the development phase will consist of the following steps:
- development of a site template and prototype
- addition of content to the template
For larger projects, the development phase will consist of the following steps:
- development of a site template
- development of a site prototype
- development of the final version of the site
For all projects, the client must approve each step before development can continue.
5. Testing
Testing of Siasan projects will be done in either three or four stages. The stages will be scheduled to fall at the conclusion of each development phase.
Design testing will take place after the Planning and Design phases of development. During this testing period the proposed interface and the project documentation will be scrutinised. Testers will supply criticism and general comments as well as identifying any changes that need to be made.
Development I testing is an optional phase to be used in larger projects where a prototype is created. In this phase, testers work through a small set of scenarios that cover navigation and flow of information. They also comment on the usability of the interface. In smaller projects, these issued will be identified informally by ongoing consultation with the client.
Development II testing is the final test before the project goes live. It tests almost the full range of functionality, with the only omissions being areas that are dependent on the live environment. Testers work through a list of scenarios as well as attempting to break the project, identifying procedures that cause an error.
Live testing repeats the Development II tests with the addition of scenarios that rely on the live environment. It identifies issues caused by migration to the live environment as well as testing any new functionality.
6. Client handover/going live
At the conclusion of development, the site will be uploaded to a testing server (usually http://www.siasan.com/testingcentre). The site will be thoroughly tested, then transferred to the client’s server. After this there will be a short period (negotiated for each project) where the Siasan development team is available for support and bug fixes.