New answers tagged

0

This greatly depends per domain, in some domains defects are easy to record and easy to fix. In some it maybe extremely complex and time consuming to even describe the reproduction steps of a defect... The best way to find out is to measure with a defect tracker (like Jira) where you can also log the amount of time spend on a issue. Then after a year you ...


3

There is no such thing as an average bug. Every bug is - by definition - an exception. Furthermore: Each industry segment has different expectations of quality. The expected standard for software powering medical devices is very different than the expected standard for casual game, to give just one example. Within an industry, each organization has ...


0

Although we're able to help in how to provide an estimate for time/cost and give some pointers as to what can affect this, it'll be close to impossible to an accurate estimate specifically for your scenario. Not because we don't want to, but because there are so many variables at play. On top of what everyone else has said: An 'average' defect is different ...


0

This apparently looks like a case study to analyze things. Lets take both questions one by one. How long does it take an average user to report an average bug? Well, the straight forward bugs that are very apparent won't take a lot of time. It hardly takes any time to figure out if the home page of a website isn't opening. The bugs that take time and have ...



Top 50 recent answers are included