Bug prioritization framework/process

User: "Nick Maugeri"
Updated by Nick Maugeri
Hi everyone!

We're revamping our bug prioritization framework/process at the moment but have been struggling with a few key areas. Some of the specific question marks we have are:
  • How do you flag bugs and track the number of occurrences?
    • Does CS or eng own the "number of users" impacted?
  • How do you communicate with the product team as bugs are resolved or being worked on?
  • What do you use as the various tiers of bugs? We currently are looking at % of users impacted but the numbers seem really high (i.e. 50-90% users impacted is currently the middle tier in terms of priority). 
    • Are there ways you tie the bug to current and future revenue?
  • What resolution times benchmarks do you use?
  • Do you have any shareable resources around how your org defines 'bugs'?
Would love to hear how others approach this and work with their eng teams to resolve issues!


Find more posts tagged with