Personal Software Process (PSP)
What is PSP?
The Personal Software Process (PSP) shows engineers how to
- manage the quality of their projects
- make commitments they can meet
- improve estimating and planning
- reduce defects in their products
Because personnel costs constitute 70 percent of the cost of software development, the skills and work habits of engineers largely determine the results of the software development process. Based on practices found in the Capability Maturity Model (CMM), the PSP can be used by engineers as a guide to a disciplined and structured approach to developing software. The PSP is a prerequisite for an organization planning to introduce the TSP.
The PSP can be applied to many parts of the software development process, including
- small-program development
- requirement definition
- document writing
- systems tests
- systems maintenance
- enhancement of large software systems
For More Information
Find out how to Get Started using PSP and learn about current policies and procedures for maintaining an authorization.
For a more detailed description of the PSP and TSP, read the article Pathways to Process Maturity: The Personal Software Process and Team Software Process by Watts Humphrey or watch his QuickTime video, "Competing in the Software Age."
For more information about TSP/PSP, send email to tsp@sei.cmu.edu.