Isnât the equivalent of the tennis coach playing tennis a quality coach doing engineering, process, product, system management with a focus on quality?
A quality coach, whoâs a coach in quality behaviors and practices within the software domain in the areas of engineering, processes, product and systems should have the knowledge and expertise to do some of the things heâs trying to change or improve, be it testing, deployments and releases, environment and systems setup, coding and solution design, and others.
love that analogy so I continue with this one:
Saying a Quality Coach shouldnât do hands-on testing is like saying a music conductor shouldnât play an instrument.
Just as a conductor stays connected to the nuances of sound and rhythm by practicing an instrument, a Quality Coach sharpens their expertise and credibility by engaging directly with testing. If they never touch the tools or face real-world challenges, how can they mentor others effectively?
As a quality coach myself, I do think it is good to get hands on at times and do some testing. However I think it is important that I am not âthe testerâ.
With the tennis analogy - definitely the coach should actively play, learn more and develop their own skillset. But for the tennis club to succeed, the focus of the coach has to be on helping those they coach to play tennis. Sure, the player may learn from watching their coach play in a tournament and the maybe club could get some short term benefit from any success, but for the club to succeed it will need its players to able to compete.