Deep Dive Example 3
Last updated
Last updated
Failure
Link
5 Why
Root Cause
Solution
1. Code submitted wasnât a complete solution
1. Why: Why did ticket fail EQB? PCA in code review 2. Why: Why did it fail code review? The solution to other parts of the application as well. 3. Why: Why didnât the IC discover this?
IC did not test his code thoroughly, this is part of the IQB, which it .
4. Why: How did this pass the IQB?
The IQB contains an item: âInvestigated Regressionâ, but the IQB is and is not enforced.
The IQB has to be enforced by the team, also update to require video evidence of the fix made. This could increase ICâs FTAR by
2. Code submitted didnât work
1. Why: Why did ticket fail EQB? PCA in code review
2. Why: Why did it fail code review? The submitted logging code
3. Why: Why didnât the IC discover this? IC did not test his code thoroughly, this is part of the IQB, which it .
4. Why: How did this pass the IQB?
The IQB contains an item that âFunctional tests passâ, but the IQB is and is not enforced.
We can tackle this issue on two levels. The first one is to enforce the QB via the team and the other one is to require the IC to use JaCoCo ( to implementation), to see what lines he covered during his functional testing and record it for the video evidence in the ().
This will help the IC catching these issues before it reaches the QE team (âshift leftâ).
Enforcing the IQB and using this tool could both increase this ICâs FTAR by .
3. PCA made a mistake in JIRA (misclicked and rejected ticket)
1. Why: Why did ticket fail EQB? It failed on . 2. Why: Why did it fail on verification? The functionality delivered . 3. Why: Why didnât the IC discover this? IC did not test his code thoroughly, this is part of the IQB, which it .
4. Why: How did this pass the IQB?
The IQB contains an item that âFunctional tests passâ, but the IQB is and is not enforced.
The IQB has to be enforced by the team, also update to require video evidence of the fix made. This could increase ICâs FTAR