Managing the software process
A Discipline for Software Engineering
A Discipline for Software Engineering
Using A Defined and Measured Personal Software Process
IEEE Software
The Personal Software Process: A Cautionary Case Study
IEEE Software
The Personal Software Process in Practice: Experience in Two Cases over Five Years
ECSQ '02 Proceedings of the 7th International Conference on Software Quality
IEEE Transactions on Software Engineering
An analysis of developers' tasks using low-level, automatically collected data
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
An analysis of developers' tasks using low-level, automatically collected data
The 6th Joint Meeting on European software engineering conference and the ACM SIGSOFT symposium on the foundations of software engineering: companion papers
Jasmine: a PSP supporting tool
ICSP'07 Proceedings of the 2007 international conference on Software process
Assessing PSP effect in training disciplined software development: A Plan-Track-Review model
Information and Software Technology
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
The Personal Software Process is a process improvement methodology aimed at individual software engineers. It claims to improve software quality (in particular defect content), effort estimation capability, and process adaptation and improvement capabilities. We have tested some of these claims in an experiment comparing the performance of participants who had just previously received a PSP course to a different group of participants who had received other technical training instead. Each participant of both groups performed the same task. We found the following positive effects: The PSP group estimated their productivity (though not their effort) more accurately, made fewer trivial mistakes, and their programs performed more careful error-checking; further, the performance variability was smaller in the PSP group in various respects. However, the improvements are smaller than the PSP proponents usually assume, possibly due to the low actual usage of PSP techniques in the PSP group. We conjecture that PSP training alone does not automatically realize the PSP's potential benefits (as seen in some industrial PSP success stories) when programmers are left alone with motivating themselves to actually use the PSP techniques.