Process Insight Examples
Last updated
Was this helpful?
Last updated
Was this helpful?
“From 33% of failures in T1W were due to ICs using older versions of TE tool, missing recent bug fixes. Asked ICs to update tool. Quality improved from 99.4% to 99.6% and 3 more ICs reached 100% FTAR.” (Example from )
“From I learned that ICs spend 13% of their time on trying to find & assign backlog - there was no auto allocation (Test Rail test-cases in old process and Jira tickets in the new process). Coached the ICs to use only Test Rail for backlog (old process). Productivity increased by 20%.” (Example from )
“BP tries to dig and find solutions and approaches PCA or other resources after 5 to 6 hours. TP raises questions to PCA or other resources as soon as he feels blocked. I coached all ICs that, in case of Environment or Reproduction Issues over an hour, leave a detailed description of the problem faced and ask for help. This saves 4+ hours of redundant troubleshooting that doesn’t result in anything positive. Productivity increased by 8%”
“TP has spent 33 seconds more than the BP in managing the ITR (becoming available and unavailable based on the queue size). It helps him manage his Initial Response Time (IRT) <15 minutes and be focused on assigned tickets without missing the productivity targets. Coached BP to do the same to avoid IRT failures and improve his FTAR from 92% to 100%”
“ICs are wasting ~22 sec per unit to transition through the state in the workflow "In QE Review". With the new , this is a redundant state in the process as the TC needs to be self-reviewed by the IC after Test Writing. This state is being eliminated using the resulting in a 2% productivity gain.”