What is the PSP?
The Personal Software Process was elaborated by Watts Humphrey, creator of the CMM, and is described in his book "A Discipline for Software Engineering," first published in 1995.
The PSP, as the CMM (Capability Maturity Model), aims at improving the software development processes. The PSP is aimed at an individual performance, while the CMM has a wider range: improving the entire organization's capability to develop applications with a small number of errors.
One of the main goals PSP has is to improve estimates - to ensure projects are carried out, by and large, in the estimated time. the method's objectives also include planning and following up on schedules, as well as increasing the software engineer's personal commitment to quality.
In 1997, a study involving 298 software engineers revealed PSP could allow for a 75% improvement in the effort's acuity and for 150% bettering in size estimate quality. Furthermore, using the method, the number of over- and under-estimates became more balanced.
The Product's quality increased by 2.5 times. Personal productivity increased a lot, not because of the number of code lines the programmer writes, but regarding the product, resulting in a better quality development cycle, fewer errors and, therefore, less time spent correcting mistakes.
The study also shows that by using the PSP method, errors are detected even before the test phase, something that reduces to less than 2% the problems found after the application is implanted.
The PSP, as the CMM (Capability Maturity Model), aims at improving the software development processes. The PSP is aimed at an individual performance, while the CMM has a wider range: improving the entire organization's capability to develop applications with a small number of errors.
One of the main goals PSP has is to improve estimates - to ensure projects are carried out, by and large, in the estimated time. the method's objectives also include planning and following up on schedules, as well as increasing the software engineer's personal commitment to quality.
In 1997, a study involving 298 software engineers revealed PSP could allow for a 75% improvement in the effort's acuity and for 150% bettering in size estimate quality. Furthermore, using the method, the number of over- and under-estimates became more balanced.
The Product's quality increased by 2.5 times. Personal productivity increased a lot, not because of the number of code lines the programmer writes, but regarding the product, resulting in a better quality development cycle, fewer errors and, therefore, less time spent correcting mistakes.
The study also shows that by using the PSP method, errors are detected even before the test phase, something that reduces to less than 2% the problems found after the application is implanted.