Yeah, I think this is really missing the point of Deming. While statistical quality control was a big part of what he taught, he was almost more interested in t

Yeah, I think this is really missing the point of Deming. While statistical quality control was a big part of what he taught, he was almost more interested in the philosophy of management than process management. Everything you read about him talks about statistical quality control, but nothing ever mentions his Fourteen points, or Seven deadly sins. I read about him as a kid, but alot of it has stuck with me through multiple careers, and his Fourteen principles could easily be applied to most software and engineering teams and companies. Things that are really key to his philosophy (and deeply impressed me) were: * Cease dependence on mass inspections for quality control (Do you rely on manual testing for every release?) * Break down barriers between departments (i.e. devops) * Eliminate slogans and quotas, goals, targets etc. (Maybe try the release train process for shipping software instead?) And my personal favorite: * Eliminate barriers to pride in workmanship, for hourly workers, management and engineers (is part of your team embarrassed by bad UX or known bugs that they can't fix because they are busy with other work?) Deming's philosophy basically wrote an entire ad campaign for Ford, "Where quality is job #1."