119 lines
2.6 KiB
Markdown
119 lines
2.6 KiB
Markdown
# root-cause-checklist
|
|
|
|
Systematic checklist for root cause analysis.
|
|
|
|
## Problem Definition
|
|
|
|
- [ ] Problem clearly stated
|
|
- [ ] Symptoms documented
|
|
- [ ] Timeline established
|
|
- [ ] Affected components identified
|
|
- [ ] Impact quantified
|
|
- [ ] Success criteria defined
|
|
|
|
## Fishbone Analysis Categories
|
|
|
|
### People Factors
|
|
|
|
- [ ] Knowledge gaps assessed
|
|
- [ ] Communication issues reviewed
|
|
- [ ] Training needs identified
|
|
- [ ] User behavior analyzed
|
|
- [ ] Team dynamics considered
|
|
|
|
### Process Factors
|
|
|
|
- [ ] Development process reviewed
|
|
- [ ] Deployment procedures checked
|
|
- [ ] Code review practices assessed
|
|
- [ ] Testing processes evaluated
|
|
- [ ] Documentation processes reviewed
|
|
|
|
### Technology Factors
|
|
|
|
- [ ] Framework limitations identified
|
|
- [ ] Library issues checked
|
|
- [ ] Tool configurations reviewed
|
|
- [ ] Infrastructure problems assessed
|
|
- [ ] Integration issues evaluated
|
|
|
|
### Environment Factors
|
|
|
|
- [ ] Environment differences documented
|
|
- [ ] Resource constraints checked
|
|
- [ ] External dependencies reviewed
|
|
- [ ] Network issues assessed
|
|
- [ ] Configuration drift analyzed
|
|
|
|
### Data Factors
|
|
|
|
- [ ] Input validation reviewed
|
|
- [ ] Data integrity checked
|
|
- [ ] State management assessed
|
|
- [ ] Race conditions evaluated
|
|
- [ ] Data flow analyzed
|
|
|
|
### Method Factors
|
|
|
|
- [ ] Algorithm correctness verified
|
|
- [ ] Design patterns reviewed
|
|
- [ ] Architecture decisions assessed
|
|
- [ ] Performance strategies evaluated
|
|
- [ ] Security measures reviewed
|
|
|
|
## 5-Whys Analysis
|
|
|
|
- [ ] Initial problem stated
|
|
- [ ] First why answered
|
|
- [ ] Second why answered
|
|
- [ ] Third why answered
|
|
- [ ] Fourth why answered
|
|
- [ ] Fifth why answered (root cause)
|
|
- [ ] Additional whys if needed
|
|
- [ ] Causation chain documented
|
|
|
|
## Evidence Collection
|
|
|
|
- [ ] Logs collected
|
|
- [ ] Metrics gathered
|
|
- [ ] Code examined
|
|
- [ ] Tests reviewed
|
|
- [ ] Documentation checked
|
|
- [ ] User reports compiled
|
|
- [ ] Monitoring data analyzed
|
|
|
|
## Validation
|
|
|
|
- [ ] Root cause reproducible
|
|
- [ ] Alternative causes eliminated
|
|
- [ ] Evidence supports conclusion
|
|
- [ ] Peer review conducted
|
|
- [ ] Confidence level assessed
|
|
|
|
## Action Planning
|
|
|
|
- [ ] Immediate actions defined
|
|
- [ ] Short-term solutions planned
|
|
- [ ] Long-term prevention designed
|
|
- [ ] Process improvements identified
|
|
- [ ] Responsibilities assigned
|
|
- [ ] Timeline established
|
|
|
|
## Documentation
|
|
|
|
- [ ] Analysis documented
|
|
- [ ] Evidence archived
|
|
- [ ] Recommendations clear
|
|
- [ ] Lessons learned captured
|
|
- [ ] Report generated
|
|
- [ ] Stakeholders informed
|
|
|
|
## Follow-up
|
|
|
|
- [ ] Fix implemented
|
|
- [ ] Effectiveness verified
|
|
- [ ] Monitoring in place
|
|
- [ ] Recurrence prevented
|
|
- [ ] Knowledge transferred
|
|
- [ ] Process updated
|