quality-postmortem

To run a blameless postmortem, use 5 Whys analysis to identify systemic root causes behind escaped defects. The process assigns owned action items with due dates to ensure corrective measures are tracked to closure.

Investigate flaky tests by running a quality retrospective that analyzes test suite health and coverage gaps. This approach identifies patterns in flaky tests and generates tracked action items for proactive quality improvement.

Root cause analysis classifies missed test levels by examining how escaped defects bypassed the test suite. It categorizes bugs by systemic root cause and identifies specific prevention opportunities to strengthen test coverage.

Yes, you can aggregate bug patterns from multiple escaped defects to identify systemic quality issues. This Skill groups recurring root causes and test level gaps to reveal broader weaknesses in your test strategy and CI health.

Yes, this approach supports assigning and tracking action items after a 5 Whys analysis by attaching owners and due dates. It ensures that corrective processes identified during the postmortem are tracked to closure and actually implemented.

You need a template-driven incident report when analyzing escaped defects to standardize documentation of root causes and prevention opportunities. This ensures consistent quality retrospectives and blameless RCA across different production incidents.