The Process
The Personal Software process (PSP) was created by Watts Humphrey [5] to address the need for individual software engineers to acquire a disciplined and effective approach to writing programs. The philosophy behind the PSP is that an organization's ability to build largescale software systems is dependent upon the ability of its individual software engineers to develop high quality smallscale programs in a disciplined, effective manner. The PSP is designed to help engineers organize and plan their work, track their performance, manage software defects, and analyze and improve their personal process. Since 1995, we have used [6] Watts Humphrey's Introduction to the Personal Software Process [7] to teach the material in our undergraduate curriculum starting at freshman year. During the sophomore year, students are required to take the first software engineering class, were they are introduced to the concept of Team Software Process (TSP). TSP is created by Watts Humphrey [8], and is aimed at teams of individuals who have already been PSP trained. The TSP provides a wellstructured process for developing software, using teams in multiple builds. Students in the senior project were required to follow PSP and TSP concepts for their product development.