The NetRelations Project Method
This is a popular version of the NetRelations project method. NetRelations have developed this Project Method to serve as support and guideline when planning and implementing website projects. The objective for using the method is to achieve conformity to project steering and documentation, and to fulfil our clients’ quality requirements.
The method described in this document is undergoing continuous enhancement to achieve even higher standards in our deliverables. Our experience is that clients are very satisfied with these work procedures. They can follow what we do and what comes up next. For our partners and project members, the project method makes the interaction with clients easier to understand and helps us deliver excellent websites.
1. Research and Analysis
In order to understand the needs and demands of our clients – and our clients’ clients – a Needs Analysis is required. By making a Needs Analysis we feed the project with vital information regarding the different target groups that shall be served on the future website.
The Needs Analysis forms the platform for personalisation of content towards these groups. It will also set up the framework for the information architecture and architecture. The deliverables in this phase are; Project Plan, Specification of Requirements and Proposed User Scenarios. The analysis also brings realism to the time line.
2. Information Structure
The objectives when creating the Information Structure is that the future visitors easily will find the relevant information. The structure is the basis for the content population of the website and delivers a comprehensive view of all elements and menus. Both the width and the depth of the web site navigation become easier to spot. By elaborating within the areas of subject, category and area, the structure will be subject for ongoing updates during the project.
Creating the Information Structure is an iterative process, where we discuss alternative structure grouping with our clients, and check towards requirements and expectations. The findings from the Research and analysis are matched towards new ideas.
In order to find out how different content are related to each other, sketches and diagrams are used. A good start is to develop a shallow structure, to help users to make fewer clicks to find the sought information.
By using descriptive naming easy to understand for the target group, the structure is set up the right way. Use subjects, areas and categories when dividing content into groups.
3. Conceptual model
This phase contains two serial activities, first the creation of element sketches, presenting page layout without graphical form. Second, creating graphical design to the already signed off element sketches. Finally, designing sketches in Photoshop showing some of the future website templates with dummy content.
Element sketches
The sketches show the most common templates without graphical design. By using this method, the respondents are not distracted by colours or forms, instead they are forced to evaluate the layout of content on selected pages. The sketches can be seen as a sort of flow chart between different levels in the navigation on the site.
Design sketches
These sketches show the graphical form on selected levels in the site and are based on the signed off element sketches.
4. Prototype
One of the most important benefits of using a prototype is that it will be easy to make visual changes for further evaluation. The method also allows a reference person to visualise his own ideas and to give valuable feedback. The prototype can be used later in the project to evaluate added functionality or details in the graphical user interface.
The graphical sketches are transferred into a partly functional HTML-prototype. Three different scenarios are implemented as clickable web pages with temporary content. The client can now see the interaction within selected scenarios and the prototype can be used for internal presentation and support.
5. Quality Assurance
All code is validated to ensure that it follows current web standards and that structure and content is separated from presentation. HTML 4.01 Strict or XHTML 1.0 Strict are used to build the structure and CSS is used for layout and presentation.
We always focus on usability and accessibility. To ensure that there will be no problems using the web site we are making controls towards guidelines in WCAG 1.0 and also, in Sweden, Vägledningen 24-timmarswebben 2.0.
6. Usability Test
Usability tests are carried out to foresee future visitors’ reactions and views on the graphical user interface and its functionality and design. The usability tests are made in the prototype stage, in order to be completely sure that functions and layout is perceived in a way that lead the visitor straight to the sought information. By using the prototype for tests, we save valuable time and money by identifying areas of improvement before the actual programming of functions have started.
One of the project members are appointed as the test leader. The test leader is responsible for the planning and the actual testing, and documents the result in one or several reports, depending on the complexity of the project.
A usability test can be seen as structured interviews focusing on specific properties in a prototype, or in an existing website. The emphasis lies on a series of tasks, which are to be carried out by respondents from the target groups. The findings from the interviews and the scenario based testing, are documented by video. Notes are also taken during the observation. After several tests with test persons, having been led through the scenarios, the most common mistakes, misunderstandings and opinions are analysed and documented. They will be presented to the project team and client, along with recommendations on suggested changes in the prototype before entering the next phase.
7. Implementation
When the project has come this far, the project team is fairly confident they have concluded most areas of enhancements, before entering the programming of the content management tool chosen for the website administration. Preferably, the content management tool itself has been subject for an in depth analysis of its suitability for the specific task in the specific project. In all cases the tool has to be able to deliver validated code continuously. The validated code is the basis for keeping the website content accessible for all visitors.
