Member-only story
Bug Prioritization: Thoughts and Ideas for Prioritizing Defects
They are coming for you. You are on a mission and striving to reach the goals for your product, but a plague is brewing. I have seen every single prioritization method known to man. Here are some good ones for dealing with software development defects.
Creepy-crawlers emerge
At the beginning of the year, I started on a new product without any established strategy or backlog for it specifically. The engineers and product designer I’m working with were also new to this part of the customer journey. We were also fortunate enough to have an excellent QA tester on the squad. We identified low-hanging fruit to get started on while also spending time in continuous discovery, research, planning, and refinement. Soon enough, we had a plan for improvements and hypotheses for an entire quarter and maybe even more.
We started with 0 bugs, but our team was relentless in improving our product. The deeper we got into discovery, watching users, and testing our new feature improvements — the more pre-existing defects we’d find. Soon, not a week would go by without uncovering new, shocking secrets.
