QualityPlan

To be able to measure quality, we need to be able to measure it. Sounds simple, but how do we measure user friendlyness for example. This page will form the basis of all quality related information.

What belongs here

Under the heading quality we file the following types of information:

Project Management

Currently, this project is managed using the Prince 2 project management method.

Configuration Management

CVS is the Open Source Software and Digital Creations standard, but we may need to make some things like if and how we use branching explicit. We'll use the ZopeMozilla module. The CVS can be browsed online.

Exceptions procedure

If something really goes wrong, I'll trust that the development team will get notified via IRC or the mailinglist. For now no explicit procedures are necessary. See CommunicationPlan for details on the list and the IRC channel.

Change management

The Tracker will take care of feature requests and prioritizing of those requests. Same for bugs.

Requirements

Using RADAR to collect and prioritize, and Use Cases to capture the user requirements. Non-user requirements, like performance, will be listed and prioritized seperately.