Please enable JavaScript.
Coggle requires JavaScript to display documents.
Defect Life Cycle Management - Coggle Diagram
Defect Life Cycle Management
If actual not equal expected
Dangerous of bug
cause huge financial / human lose
Transaction failure
Aeroplan crash: Air China Flight Crash 1994 - killed 264 passengers
Cause: Malfunction of autopilot system
What is defect management
Discover
What is the problem
Categorize
Resolution
Verification
Closure
Reporting
Defect Categorization
Priority/ Severity
Critical
Need to be fixed immediately
Click login button and crash/ cannot login
High
impacts the product main feature
Can login but cannot print because signal not receive by printer
Medium
Cause minimal deviation from product requirement
Transaction number not seen by the time the money transfer cause panic, but restored after re-login
Low
very minor affect product operation
All text shown to user are normal/ no highlight
Risk vs Impact
Asses Risk
Design Risk Matrix
Decide Test Target
Expand Test Coverage
Trade off
Time,
Cost,
Resources
Innovate
performance testing
Learn from mistake
Reasons for Defects
Unfinished requirement
Requirement not detail enough
Requirement unclear/ multiple meaning
Logic error in design documents
Coding error
not sufficient testing
misunderstanding of user needs
lack of documentation
Benefits
Increase visibility of development process
Release planning
know the issue to be fixed
Resource scheduling
Prioritization
improve control of a project
information consolidation
Improve the quality of the software
Cost impact (80/20 rule)
Defect management technique
prevent the defects
found as quick as possible
The process should be risk driven
priorities, resources should be based on which risk can possibly be resuce
The bugs measurement should be integral part of sd process & used by project team to improve the process
The process of reporting & analyzing the bug-related info should be automated as much as possible
QA best practice
Keep an eye on bigger picture
what the user trying to achieve
Adopt technical mindset with business value
build credibility with business stakeholder
never assume, ask questions
Test often, early
Keep learning
