Avoiding Software Failures Using TSP/PSP and Six Sigma Methods
Today, the competitive marketplace demands the best of everything-the highest quality, lowest costs, and shortest possible schedule. The Team Software Process (TSP) and the Personal Software Process (PSP) shift the focus away from testing and verifying at the back-end to encouraging each engineer and the team as a whole to prevent defects throughout the project lifecycle. Incorporating Six Sigma quality practices with TSP/PSP can improve the quality-cost-schedule relationship even more. Mukesh Jain shares his experiences in implementing TSP/PSP and Six Sigma at Microsoft. He offers examples of how their teams have obtained a better work-life balance while still delivering very high quality products (67% totally defect free), on schedule (94% on time), and within budget. Mukesh highlights some common pitfalls to avoid when using TSP/PSP and Six Sigma.
- An introduction to Team Software Process (TSP) and Personal Software Process (PSP)
- Six Sigma quality practices for software development
- A case study at Microsoft