Dynamics
Quality Policy $Revision: 1.3 $ State approved
Date 02-Nov-1998 Author Jari Hautio
Review date 04-Nov-1998 Reviewed by Jouni Malinen
Approval date 04-Nov-1998 Approved by Jouni Malinen 
$Id: quality.html,v 1.3 1998/11/04 19:01:53 jkmaline Exp $

Introduction

This document specifies guidelines for the methods, processes and standards which are used to achieve high quality results in this project.

Inspections

Inspections are initiated by Author when a document suitable for inspection is complete. A copy of the document will be sent to two members and a inspection session will be reserved. In the inspection session, one of the inspectors is selected to work as Moderator while Author records the defects. Moderator's responsibility is to keep discussion in finding defects and keep timetable. Finally Moderator determines if document passes the inspection or assigns a deadline for the revised document.  An inspection report will be created including persons attending the inspection, inspected document, found defects, date of the inspection. Moderator confirms that the found errors are corrected in the revised document.

With the most important documents more inspectors may be used.

To enhance effectiveness, one of the reviewers will be responsible for spell checking. Minor errors such as mispellings and use of wrong words will be corrected directly to the document and revised document will be returned to the Author.

Documents

The inspections are the main means of assuring the quality of documents. However, due to limited resources all the documents cannot be inspected. So only the most important parts, such as documents returned as course deliverables or documents presented to the client as well as main design specifications, kernel code and API interface will be selected for inspection. Other permanent documents will still be inspected with non formal way, where someone else reads the document through and gives his approval.

General guidelines to ensure high quality documents

Guidelines for coding

Meetings

To keep the whole team working together,  the team will have regular meetings once a week in Spektri Kvintti. To ensure that meetings will be efficient the following preparations must be done. In the meeting the project manager acts as chair and following list is used as basis for meeting.
  1. Selection of the secretary
  2. Quick view to the state of the project
  3. The agenda
  4. Discussion
After the meeting

Client Satisfaction

To assure that the client gets what he wants, regular meetings with the client are held. The meetings will take place in Spektri Kvintti and possibly include demos. At least one meeting per project phase will be held, in addition to phase reviews.