How to categorize defects?



  • Many project managers and other non-tester roles search for proper categorization according to severity (A-B-C) of the defects and they search for description how to distinguish between each category.

    What are best practices? What is the Ideal description of categories?



  • There is no one "right" answer. The number and type of categories of defects that would be appropriate to your context depend upon several factors, including:

    • Type of application
    • Your team size
    • The level and frequency of "in the hallways" conversations between people on the team
    • The number of bugs you have "hanging around" waiting to be taken care of
    • etc.

    Having said that, one of the most important considerations you have to make involve: - Should we have two main categories or one per bug? - The "two main categories for each bug" approach often has, e.g., specific comments about 'what percentage of users will see this?' and 'how large is the impact?' - A "one main category for each bug" could be a blend of those two items (e.g., Sev 1, Sev 2, Sev 3) as described in Ivor McCormack's approach shown below.

    Personally, I would consider Ivor McCormack's approach as a possible starting point, discuss options with your stakeholders, and adjust as necessary for your context.

    enter image description here



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2