James Bach started in this business as a programmer. He likes programming, but finds the problems of software quality analysis and improvement more interesting than those of software production. For him, there’s something very compelling about the question “How do I know my work is good?” Indeed, how does he know anything is good? What does good mean? That’s why he got into SQA in 1987.
Today, he works with project teams and individual engineers to help them plan SQA, change control, and testing processes that allow them to understand and control the risks of project failure. He also assists in product risk analysis, test design, and in the design and implementation of computer-supported testing. Most of his experience is with market-driven Silicon Valley software companies like Apple Computer and Borland, so the techniques he’s gathered and developed are designed for use under conditions of compressed schedules, high rates of change, component-based technology and poor specification.