Personal software process: Difference between revisions

Revision as of 02:23, 9 December 2018

Revision as of 08:11, 24 December 2018

Line 1:

{{Software development process}}

The '''Personal Software Process''' ('''PSP''') is a structured [[software development]] process that is intended (planned) to help [[software engineer]]s 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 ommitmentscommitments. 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 mark]]s of the [[Carnegie Mellon University]].<ref>{{cite web| url=http://www.sei.cmu.edu/legal/ | title=Terms of Use | publisher=[[Software Engineering Institute]], [[Carnegie Mellon University]] | ___location=USA | accessdate=14 January 2013 }}</ref>