Managing the software process
Orthogonal Defect Classification-A Concept for In-Process Measurements
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Object-oriented system development
Object-oriented system development
Improving Software Maintenance at Martin Marietta
IEEE Software
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Introduction to the personal software process
Introduction to the personal software process
A Discipline for Software Engineering
A Discipline for Software Engineering
Software Engineering Economics
Software Engineering Economics
What do we know about programming?
ESP '97 Papers presented at the seventh workshop on Empirical studies of programmers
Investigating data quality problems in the PSP
SIGSOFT '98/FSE-6 Proceedings of the 6th ACM SIGSOFT international symposium on Foundations of software engineering
Applying the personal software process (PSP) with Ada
Proceedings of the 1998 annual ACM SIGAda international conference on Ada
Some observations on software quality
ACM-SE 37 Proceedings of the 37th annual Southeast regional conference (CD-ROM)
Why don’t they practice what we preach?
Annals of Software Engineering - Special issue on software engineering education
An Experiment Measuring the Effects of Personal Software Process (PSP) Training
IEEE Transactions on Software Engineering
Strategies for personal process improvement a comparison
Proceedings of the 2002 ACM symposium on Applied computing
Software – A performing science?
Annals of Software Engineering
A Critical Analysis of PSP Data Quality: Results from aCase Study
Empirical Software Engineering
A Replicated Empirical Study of the Impact of the Methodsin the PSP on Individual Engineers
Empirical Software Engineering
Software Engineering Education: A Modest Proposal
IEEE Software
Tailoring Cleanroom for Industrial Use
IEEE Software
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
Designing process-based software curriculum
CSEET '97 Proceedings of the 10th Conference on Software Engineering Education and Training
Panel Chair: Tom Hilburn, Software Engineering Institute
CSEET '97 Proceedings of the 10th Conference on Software Engineering Education and Training
Quality management metrics for software development
Information and Management
Empirical Software Engineering
Reliability Improvement of Web-Based Software Applications
QSIC '04 Proceedings of the Quality Software, Fourth International Conference
Encyclopedia of Computer Science
Towards a flexible tool for supporting data collection & analysis in personal software process (PSP)
WSEAS Transactions on Information Science and Applications
An experimental investigation of personality types impact on pair effectiveness in pair programming
Empirical Software Engineering
Evaluation of the capability of personal software process based on data envelopment analysis
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Improving PSP education by pairing: an empirical study
Proceedings of the 34th International Conference on Software Engineering
| Hi-index | 0.00 |
The PSP is a defined family of processes that engineers can use to write module-sized programs. It is introduced with a one-semester graduate-level course where engineers develop ten programs and write five analysis reports. They practice various methods, obtain measurements, and analyze these measurements to help them understand and improve the way they work. This course has been taught in several universities and is being introduced in a number of industrial software organizations. While individual performance varies widely, data on 104 students and engineers show reductions of 58.0% in the average number of defects found per 1000 lines of code (KLOC) and reductions of 71.9% in the average number of defects per KLOC found in test. Estimating and planning accuracy are also improved while the average percentage improvement in lines of code developed per hour was 20.8%.