Information Technology Reference
In-Depth Information
Resource adjustment should not be required as the intent is to do
utmost with the resource allocated.
Disposition
indicates the timing of the fix:
Patch
. This should be assigned to Immediate or High priority
problems only. All immediate priority problems must be addressed
in a patch prior to any High priority problems.
Service pack
. This should be assigned to High, Medium, and Low
priority problems. Additional data associated with this disposition
should be the major or minor release on which the service pack
will be made available. All High priority pr oblems must be
addressed in a service pack prior to any Medium or Low priority
problems, and Medium priority problems in a service pack prior
to Low priority problems.
Minor release
. This should be assigned to High, Medium, and Low
priority problems. Additional data associated with this disposition
should be the targeted date, month, or quarter for the release.
Major release
. This should be assigned to Medium and Low priority
problems.
On hold
. This should be assigned if there is a lack of clarity and
agreement on severity or priority. Urgent action should be taken
to change this disposition, especially if it is suspected that the
severity could be Showstopper, Critical, or Serious, or the priority
could be Immediate or High.
Deferred
. This should be assigned to Medium and Low priority
problems only. This implies that there are no definite plans as of
now to fix the problem. The disposition will be reviewed period-
ically and changed as appropriate.
No plans to fix
. This should be assigned to Medium and Low priority
problems only, and more likely for Low priority. This implies that
there is a definite plan to never fix the problem.
Not a problem
. This will typically be a reassignment of an earlier
disposition that, a result of finding that something once considered
to be a problem, is actually not a problem.
Understanding Bug Discovery
The “engineering code complete” stage is considered the point at which
the development team has finished all coding (based on functional specs)
and has handed over the code to QA after finishing their preliminary unit
or developer testing.
