Personal Software Process (PSP)

Abstract

AbstractThe Personal Software Process (PSP)SM(Personal Software Process and PSP are service marks of Carnegie Mellon University.) provides engineers 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. It is introduced with a textbook and a course that are designed for both industrial and academic use. The PSP is designed for use with any programming language or design methodology, and it can be used for most aspects of software work, including writing requirements, running tests, defining processes, and repairing defects. When engineers use the PSP, the recommended process goal is to produce zero‐defect products on schedule and within planned costs. When used with the Team Software Process (TSP)SM, (Team Software Process and TSP are service marks of Carnegie Mellon University.) the PSP has been effective in helping engineers achieve these objectives.This article describes in detail what the PSP is and how it works. Starting with a brief discussion of the relationship of the PSP to general quality principles, the article describes how the PSP was developed, its principles, and its methods. A summary of the PSP courses, the strategy used for teaching the PSP, selected data on PSP experience, PSP adoption in university curricula, and the status of PSP introduction into industry is given. The article concludes with comments on likely future trends involving the PSP.