Generally, for the 3rd question, what are we doing to prevent the problem, we have short and longer term solutions. In the short term, we should add the appropriate test or check that missed the problem in the first place. That is the answer to the specific question for that particular issue.

For the longer term, we collect data about the escaped causes and reasons for escape. We collect that data in the bug tracking system as two fields with categories. When we have enough data, we can examine trends. I usually start with a simple Pareto analysis, showing the top few causes/reasons. Then work with the team to ask how can we improve our processes/practices. Its often useful to filter the Pareto analysis to the most painful bugs (those found by customers, high severity, etc.)

Please drop a comment below and let me know what you do for root cause?

Software Leadership Academy

Are you interested in enhancing your career into a leadership role? Check out the Software Leadership Academy, an online course designed for you. The Software Leadership Academy provides proven lessons to learn the art and science of management - customized for software professionals (dev, test, ops, etc.)