HHome.gif (952 bytes)ProcImp.gif (1034 bytes)Training.gif (968 bytes)SatCust.gif (1033 bytes)CmpProf.gif (1007 bytes)RelDoc.gif (1033 bytes)RelSite.gif (998 bytes)

IHome.gif (7547 bytes)

PSP for Engineers I: Planning

PSP for Engineers II: Quality

TSP Executive Seminar

Managing TSP Teams


Contact Us

img0.gif (1463 bytes)


About PSPSM for engineers
The Personal Software Process (PSPSM) was  developed by SEI Fellow Watts Humphrey as a follow-on to his groundbreaking work in organizational software processes. The PSP scales down software processes to a level suitable for individual use. It uses principles of time and quality management to provide a step-by-step framework for improving software development methods. The PSP introduces the discipline of engineering to a process that is often ad hoc. It teaches software practitioners how to plan, monitor, measure, analyze, and improve their work. Practitioners use their own data to convince themselves of the effectiveness of the PSP.

PSP student data shows that, on average, PSP training reduces estimation errors by 40 percent, test defects by 73 percent, and test time by 43% (reduced test time indicates a higher quality product being submitted for testing).  All this is accomplished with a 21% average increase in productivity.

Data from early adopters in industry show products developed using the PSP had near zero defects reported after several months of use. Organizations that train their developers in the use of the PSP can expect significant reduction in defects, improvements in schedule estimating, improvements in productivity, and overall reduction of cycle time.

Complete training in PSP for engineers is comprised of the following two five day courses:

2007 Davis Systems
(SM) PSP, Personal Software Process, TSP, and Team Software Process are service marks of Carnegie Mellon University