Managing Software Quality with the Team Software ProcessJames W. Over
About the Topic
Software is the only modern technology that relies on testing to find and fix defects. With this "test-in" quality strategy, many software defects are found during testing, or later, when costs are higher and methods are less effective. This approach increases rework and software development costs, and leads to "buggy" products. A far better strategy is to manage quality throughout the software project, not just in QA. To do this, software teams must also focus on quality, with developers working with QA to put much higher quality products into test. But training and motivating software teams to work this way has been challenging. SEI's Team Software Process (TSP) was designed to build teams that manage software quality, delivering software with four to five times fewer defects while also reducing development costs and schedule by 25% or more. This presentation will describe the TSP quality strategy, illustrated with results from software teams at Adobe, Intuit, Microsoft, Oracle and other organizations.
About the Speaker
James W. Over, who has been with the Software Engineering Institute (SEI) Carnegie Mellon since 1987, is manager of the TSP and is a senior member of the technical staff for the Software Engineering Process Management Program. Over has led SEI's TSP Initiative since its inception, transitioning the TSP into organizations in the United States and abroad. He received an award from Boeing Corporation for innovation and leadership in software process improvement. He has more than 35 years of technical and management experience in the software engineering industry. Over is the co-author of several SEI publications on software process definition and improvement.
