[Craig Brass]

 feature_request.gif (6.8K)
Number of downloads: 1

Below is the process we go through when a new feature gets requested.

1. After a new feature has been submitted, one of our software architects checks to see if the feature has already been requested. If so, it is moved to the Duplicate board. They also check to see if it isn't already a feature of the software. If it is, they move it to the Already a Feature board.

After this, the architect decides if it is something that they think should be implemented or not. They may consult with the other software architects and / or the developers at this point. If it is decided it will be implemented, it will be moved to the Pending Implementation board and a feature specification for the developer will be written up so they know exactly how it should work. If they decide not to implement it, it will be moved to the Currently Unviable board. Feature Requests in the Currently Unviable board are regually checked to see if they have become viable to implement.

If the architect needs more information about the requested feature, they will reply to it asking the person submitting it for further details. If the user fails to reply, the request may be moved to the Currently Unviable board anyway.

 down_arrow.gif (997bytes)
Number of downloads: 1

2. The software developers check over the Pending Implementation board regually and when a topic is in here, they work on implementing it as soon as possible. Once they have implemented the feature, it is moved to the Implementation Attempted board.

 down_arrow.gif (997bytes)
Number of downloads: 1

3. The architect that initially accepted the feature request checks the latest build of the software to confirm that the work has been carried out according to the specification. If it has, they will move it to the Implemented board. If it hasn't then it is placed back into Pending Implementation board for further investigation by the developer who attempted implementation.