You found a bug and the Developer you are working with does not want to fix it—you think it is important. What do you do?

I think one of the very best ways I can report a bug is by showing it to the Developer. I will stand them in front of my computer, fire up their software, and demonstrate the thing that goes wrong. Once they can see the problem happening, they can usually take it from there and start trying to fix it.

And, I will clarify “Customer impact descriptions” for the bug and send it to Developer and stakeholders with the bug to discuss whether we should fix it or not. Also the Customer impact descriptions include how the bug affects the user and how the problem will affect customer scenarios and requirements. Items to consider when writing a customer impact description include the following:

· Determine the customer scenarios and requirements that the bug affects.

· Determine the frequency or likelihood of the customer encountering the issue.