The Personal Software Process (PSP) is a method of improving your software engineering skills. During the course, there are 10 programs that you write. You record metrics during the development of these programs, and base your size, time, and defect estimates on your past history.
I started to work on the PSP during lunchtime at work in 1996. The company, located in Pittsburgh, later adopted PSP/CMM and went on to send lots of folks to classes, but I had already left the company to move to the south.
I had a keen interest in software process improvement after completing a masters degree in computer information systems, and studying about the Capability Maturity Model in one of the courses on the Software Lifecycle. Since the company was located in Pittsburgh, I attended SEPG meetings that were held monthly at the SEI. Watts came to one of the meetings and did a presentation on PSP shortly after writing the book, and so a work buddy (Jim) bought 2 PSP books (one for him and one for me) at the CMU bookstore. We started doing the excercises together during lunch, and started applying the stuff to my work. Jim got busy with several projects and with having a baby and didn't keep up, but I finished all the excercises. However, Jim later went on to take the course, become a PSP trainer, and went to work for the SEI. In fact, he just presented with Watts at an SEPG conference. He said it was "Sort of like presenting the Bible with God introducing you." Jim also wrote a technical report.
These are the programs I wrote. They are written in ANSI C for an iRMX environment, and should be quite portable, except for the filename/directory convention.
I use Program 3A (function line of code counter) and Program 6A (linear regression estimate) quite a bit for programming that I do on a day to day basis. This also means that they may contain updates to the original code written for the PSP course. I also wrote a small program that counts the number of times a piece of text is found in a file. Count is is useful for taking Visual Source Safe reports created from ShowHistory-Reports-IncludeDifferences-ToFile and looking for lines added "Ins:", deleted "Del:", or modified "To:".
PSP Resources brought to you by www.processimprovement.com.
The Software Process Dashboard Project - an open-source initiative to create a PSP(SM) / TSP(SM) support tool.
An interesting code reuse policy for Arthur Alexander Reyes classes at The University of Texas at Arlington.
Page created by Steve Karg using Intel's aedit, Notepad, or Vim.
Steve's Software Trek
Steve's Home Page