 | This article includes a list of general references, but it lacks sufficient corresponding inline citations. (August 2023) |
| Part of a series on |
| Software development |
|---|
.png)
The Personal Software Process (PSP) is a structured software development process that is designed to help software engineers better understand and improve their performance by bringing discipline to the way they develop software and tracking their predicted and actual development of the code. It clearly shows developers how to manage the quality of their products, how to make a sound plan, and how to make commitments. It also offers them the data to justify their plans. They can evaluate their work and suggest improvement direction by analyzing and reviewing development time, defects, and size data. The PSP was created by Watts Humphrey to apply the underlying principles of the Software Engineering Institute's (SEI) Capability Maturity Model (CMM) to the software development practices of a single developer. It claims to give software engineers the process skills necessary to work on a team software process (TSP) team.
"Personal Software Process" and "PSP" are registered service marks of the Carnegie Mellon University.[1][2]
- ^ Cite error: The named reference
:0was invoked but never defined (see the help page). - ^ "Terms of Use". USA: Software Engineering Institute, Carnegie Mellon University. Retrieved 14 January 2013.