Information Technology Reference
In-Depth Information
Normal
implies missing functionality, loss of functionality, or a
usability problem that does not render the solution useless for the
customer. They can continue to use the solution for all practical
purposes even if an acceptable workaround does not exist for the
particular bug or enhancement.
Low
typically implies missing functionality, loss of functionality, or
a usability problem that has low impact on a customer's ability to
use the solution (a fix would be welcome but very little is lost in
the customer's ability to derive value from the solution).
Priority
indicates the priority with which the bug or enhancement
request will be taken up by the development team. Priority is assigned
based on the
severity
of the bug or enhancement, other commitments of
the development team, and available resources. There is often confusion
between
severity
and
priority
. The difference is analogous to Important
versus Urgent in a list of action items.
Immediate
. This is typically a priority assigned for Showstopper
and Critical severity problems. This means a quick patch must be
issued. All Immediate Priority problems must receive attention
before those of any other type. It might also mean more resources
are applied to the problem, typically because resources are busy
with other Immediate Priority problems or more resources can do
a better job of meeting customer need for a quick fix.
High
. This is typically assigned for Serious severity problems. High
Priority problems receive attention as long as there are no imme-
diate priority problems waiting for attention. Fixes should be made
available at the next convenient patch or service pack (maintenance
release).
Medium
. This is typically assigned for Normal severity problems.
Medium Priority problems receive attention only if all Immediate
and High Priority problems have appropriate attention and
resources applied to them. Fixes must be made available in one
of the next convenient service packs (maintenance releases) or
minor or major releases. A Normal severity must not be assigned
priority higher than Medium. Resource adjustment should not be
required as the intent is to do the most with the resource allocated.
Low
. This is typically assigned for Low severity problems. Low
Priority problems must get attention only if all other priority prob-
lems have appropriate attention and resources applied to them.
Fixes must be made available in one of the next convenient service
packs (maintenance releases) or minor or major releases. A Low
severity problem should be assigned priority lower than Medium.
