3.5.5. Frequency

Frequency

While defects may be very severe, they may not happen frequently, while bugs as insignificant as spelling errors may be seen constantly. The frequency at which an error occurs may play a big part in determining when it needs to be fixed. For that reason, AgileTrack allows defects to be classified by frequency and for that to be taken into account when planning iterations.

Constant
Frequent
Sometimes
Infrequent
Rare

It sometimes takes a while to get a feel for the frequency of a defect, but it is often useful in classifying the issue and making good decisions about what is important.

In addition to Importance and Urgency, defects can be classified using the fields Severity and Frequency. The classification fields are imprecise, but allow general ranking and classification of issues. Iterations should be used for fine tuned planning. It is up to your team to decide how valuable are such fields, and how to best classify issues in AgileTrack.

Next Section: 3.6. Assignment


You can add comments in this section, but you must be logged in. If you already have an account, you can login now. If you need to create an account, you may also register now.