Investigating data quality problems in the PSP
SIGSOFT '98/FSE-6 Proceedings of the 6th ACM SIGSOFT international symposium on Foundations of software engineering
Project LEAP: personal process improvement for the differently disciplined
Proceedings of the 21st international conference on Software engineering
Introduction to the team software process
Introduction to the team software process
A Discipline for Software Engineering
A Discipline for Software Engineering
Using A Defined and Measured Personal Software Process
IEEE Software
IEEE Software
Implementing concepts from the Personal Software Process in an industrial setting
ICSP '96 Proceedings of the Fourth International Conference on the Software Process (ICSP '96)
| Hi-index | 0.00 |
Every so often, a new methodology is launched onto the software engineering landscape with all the force of a religious crusade. From its humble beginnings Software Process Improvement (SPI) has spread its wings into virtually every sector of the software engineering community and in the process has transformed itself from a bag of tools and techniques, into a serious set of methodologies for enhancing organisational effectiveness and competitive success. In the latter half of the 1990's, individual SPI methodologies such as PSP [1] and PIPSI [2] were promulgated as approaches to make the individual a better software engineer.Surveys of European software organisations [3] have shown support for SPI. In Europe to date, SPI programmes have concentrated at the organisational level, with less adoption at the level of the individual. This paper explores the role of individual-level methodologies in a European context and details the results of a series of experiments conducted by the authors.