Document the tool and process used to record and track defects. List any reports to be produced and include recipients, frequencies, delivery mechanisms and examples. Identify team resources involved in the defect tracking process.

  • Describe any ratings, categories or classifications used to identify or prioritize defects. Following are sample categories for prioritizing defects:
    • High - System had an outage or significant parts of the system were inoperable as a result of executing the test. There is no workaround. Severity level 1 issues must be addressed before the software exits any Test Phase.
    • Serious - One of more primary business requirements could not be met with the system. There might be a temporary workaround but no easily apparent or readily acceptable viable workarounds are in place. Performance, functionality, or usability is seriously degraded. At times, a problem is raised to this severity level - from a lower severity - due to the customer's expressed importance to have the issue resolved in the current release. The goal is to have all severity 2 issues resolved before exiting a specific Test Phase but must be resolved before entering Production.
    • Moderate - Business requirements can be met with the system. Any needed workarounds are apparent. Performance, functionality, or usability is not seriously degraded. Level 3 severity defects may, or may not, be fixed in the current release - this is decided by the 8.9 technical and management team.
    • Minor - These issues are very minor in nature, yet still are valid problems. An example would be a typo in the documentation or an irregularity in the user interface. These problems usually do not affect overall release accuracy or usability in any significant way. Level 4 severity defects are less likely to be fixed in the current release and are usually deferred to a later release.
    • Enhancement - Issue is an enhancement and not a bug. Usually this issue addresses items outside of the scope of present business requirements. This is usually fixed in a future software release.
  • No labels