> For the complete documentation index, see [llms.txt](https://remoteu.gitbook.io/manager-remoteu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remoteu.gitbook.io/manager-remoteu/day-3/examples/deep-dive-example-3.md). # Deep Dive Example 3 ### Eng.Maintenance | Failure | Link | 5 Why | Root Cause | Solution | | -------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Code submitted wasn’t a complete solution | [SL-36288](https://drive.google.com/open?id=14RO1jfEFhBL8lEjWIES3YizGI8k0K647) |

1. Why: Why did ticket fail EQB?
PCA rejected in code review
2. Why: Why did it fail code review?
The solution should have been applied 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 passed.

4. Why: How did this pass the IQB?

| The IQB contains an item: “Investigated Regression”, but the IQB is [self-checked](https://drive.google.com/open?id=1jLVkhJCOSAYLBlA8NPC9CJhcRUd2dIPH) and is not enforced. | The IQB has to be enforced by the [Eng.Maintenance.QE](https://docs.google.com/spreadsheets/d/1RjQNNT4ycpSN4dnaRyz435KM__fEdXjY3MACPS9pFfc/edit#gid=447117371\&range=A43) team, also update [Internal Quality Bar](https://drive.google.com/open?id=1lyafeyyGNdmhDXQ0fD2Sivl7fjKHIutc) to require video evidence of the fix made. This could increase IC’s [T8W](https://docs.google.com/spreadsheets/d/1Qp03QZDqtJulc8UNvputALqBKi4iaob5cM-Ln0bLEyk/edit?usp=sharing) FTAR by [17.39% from 82.61% to 100%](https://drive.google.com/open?id=1E1Mn3Bzf6OJGMkIdbobyj28eskh62Y6d) | | 2. Code submitted didn’t work | [SL-31217](https://drive.google.com/open?id=1j0cJA_Ep1Zk1JACAmBDSAhaXjIedF56j) |

1. Why: Why did ticket fail EQB?
PCA rejected in code review

2. Why: Why did it fail code review?
The submitted logging code didn’t work

3. Why: Why didn’t the IC discover this?
IC did not test his code thoroughly, this is part of the IQB, which it passed.

4. Why: How did this pass the IQB?

| The IQB contains an item that “Functional tests pass”, but the IQB is [self-checked](https://drive.google.com/open?id=1jLVkhJCOSAYLBlA8NPC9CJhcRUd2dIPH) and is not enforced. |

We can tackle this issue on two levels. The first one is to enforce the QB via the Eng.Maintenance.QE team and the other one is to require the IC to use JaCoCo (link to implementation), to see what lines he covered during his functional testing and record it for the video evidence in the proposed IQB (PIQB.8).

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 4.35%.

| | 3. PCA made a mistake in JIRA (misclicked and rejected ticket) | [NVPCID-8726](https://drive.google.com/open?id=1JGpXQNr_usJE9gLEPsxPlQj6AyVSq0rQ) |

1. Why: Why did ticket fail EQB?
It failed on verification.
2. Why: Why did it fail on verification?
The functionality delivered did not work.
3. Why: Why didn’t the IC discover this?
IC did not test his code thoroughly, this is part of the IQB, which it passed.

4. Why: How did this pass the IQB?

| The IQB contains an item that “Functional tests pass”, but the IQB is [self-checked](https://drive.google.com/open?id=1jLVkhJCOSAYLBlA8NPC9CJhcRUd2dIPH) and is not enforced. | The IQB has to be enforced by the [Eng.Maintenance.QE](https://docs.google.com/spreadsheets/d/1RjQNNT4ycpSN4dnaRyz435KM__fEdXjY3MACPS9pFfc/edit#gid=447117371\&range=A43) team, also update [Internal Quality Bar](https://drive.google.com/open?id=1lyafeyyGNdmhDXQ0fD2Sivl7fjKHIutc) to require video evidence of the fix made. This could increase IC’s [T8W](https://docs.google.com/spreadsheets/d/1Qp03QZDqtJulc8UNvputALqBKi4iaob5cM-Ln0bLEyk/edit?usp=sharing) FTAR [from 86.05% to 100%](https://drive.google.com/open?id=1E7U0MaIZ3M9JQzDU1reCdbMH2vGfnZXi) |