The PSP and TSP both use proven techniques to improve individual performance and team in software development. Used together they help reduce costs, produce defect-free and inside deadline by empowering development teams.These technologies are based on the premise that a defined and structured process can improve individual work quality and efficiency.
PSP focus is on individuals and TSP focus is on teams.
The Personal Software Process (PSP) provides engineers with a disciplined personal framework for doing software work. The PSP process consists of a set of methods, forms, and scripts that show software engineers how to plan, measure, and manage their work.
The PSP is a disciplined and structured approach to developing software that was developed in 1993 by Watts S. Humphrey. By using the PSP concepts and methods in their work, individuals in almost any technical field can improve their estimating and planning skills, make commitments that they can meet, manage the quality of their work, and reduce the number of defects in their products.
The Team Software Process (TSP) guides engineering teams that are developing software-intensive products. Using TSP helps organizations establish a mature and disciplined engineering practice that produces secure, reliable software in less time and at lower costs.
The TSP was introduced in 1998, and builds upon the foundation of PSP to enable engineering teams to build software-intensive products more predictably and effectively.
Strongstep provides the SEI official training course for PSP called PSP Fundamentals.
Strongstep provides the SEI official training course for TSP called TSP Executive Strategy Seminar.