Defect Management in Business Analysis

Correct Answer: The ratio of defects found in production versus those found during testing

The ratio of defects found in production versus those found during testing is the most crucial metric for measuring defect leakage in BA projects. This metric specifically measures how effective the testing process is by comparing defects that escaped detection during testing and were discovered in production, against those caught during the testing phase. A lower ratio indicates better testing effectiveness and requirements quality. Other answers are incorrect because: The total number of defects across all phases does not specifically measure leakage - it only shows overall defect volume. The percentage of requirements vs technical defects measures defect classification but not leakage effectiveness. The average resolution time multiplied by affected stakeholders measures impact and efficiency of fixing defects, but not the effectiveness of preventing them from reaching production.

Correct Answer: By evaluating the impact on core business functions and user experience

The most effective way to classify defect severity is by evaluating the impact on core business functions and user experience. Here's why: The correct approach focuses on business value and user impact, which are the primary concerns in business analysis. This method considers: - How the defect affects critical business operations - The impact on end-user experience - The potential business losses or risks - Alignment with business objectives Why other approaches are less effective: Measuring time and resources for solutions puts too much emphasis on technical implementation rather than business impact. Calculating users affected × frequency creates an oversimplified metric that may miss critical issues affecting few users but with severe consequences. Assessing technical complexity focuses too much on the solution rather than the business problem and impact. In business analysis, the priority should always be understanding and addressing business impact rather than technical considerations or pure metrics.

Correct Answer: To assess and prioritize reported defects based on business impact and severity

The primary purpose of defect triage is to assess and prioritize reported defects based on their business impact and severity. This is crucial because: - It helps allocate limited resources efficiently - Ensures critical issues are addressed first - Enables better project risk management - Helps maintain business value focus Why other answers are incorrect: Documenting technical details is part of defect reporting, not triage. This is a preparatory step for triage but not its main purpose. Assigning defects to development teams is a follow-up action after triage, not the primary purpose of the triage process itself. Analyzing root causes is typically done during defect resolution or as part of lessons learned, not during the triage process. While important, this is a separate activity that occurs after the initial assessment and prioritization.