Gemba Walk Example 2

Example 2

Insight

Action

Link

1. Top performers take time to perform a Self-Review to scrutinize their changes. They use various Diff tools extensively (although this is not true for all) which help identify any mistakes. This aligns with the TMS study which shows top performers spending 8 times more time on Self-Review.

1) Mandate a structured Self-Review to be done on all tickets through the use of Calendars. This should improve Internal QA FTAR.

2) Define a standard toolchain, including code-block diff and train low performers how to use it.

Link

2. Experienced ICs use informal channels to influence the work of the HUT team, prioritizing UT writing for their tickets, which allows them to solely focus on Code Cleanup. This increases the load on lower performers who are more prone to introduce quality faults.

1) Eliminate informal communication that influences the output of the HUT team in favor of any ICs. An exchange between two assembly lines should be guided only by quality bars and process.

2) Enforce an Input Quality Bar to require all incoming tickets to have 80% UT coverage. "let the process break where it's broken" (i.e. at the HUT assembly line).

Link

3. ICs are having a difficult time setting up builds for new projects which forces them to interleave that effort with working on other tickets to keep their performance metric. This results in multi-tasking and violates the principles of Deep Work causing mistakes and Quality Failures.

1) Make a packaged Build Environment (similarly to the Skyvera and EPM Live projects but using DevSpaces) be a part of the Input Quality Bar for the Code Cleanup order from the PCA.

Link