March, 2001

This month's presentation was titled "Introduction to PSP and TSP" and was written by Steve Janiszewski while he was with Honeywell International. The full 56-page presentation, chocked full of facts, figures, charts, and graphs, is available at (From the main screen, click on the "References" button and scroll down to the "Experiences with Six Sigma Software at Honeywell" category.)

Quick Notes:
The Personal Software Process (PSP) is a level 5 process designed for cost effective individual use. It applies to most structured personal tasks, such as developing program modules, defining requirements or processes, conducting reviews or tests, writing documentation, etc. PSP-augmented TSP can support the development of large-scale software systems and can be used to accelerate an organization from level 2 to level 5.
There only three basic metrics in PSP:
1. Effort, measured in minutes;
2. Defects found in the product (fix time, type, injection phase, removal phase, description);
3. Product size, measured in lines of code (LOC).

The Team Software Process (TSP) adds a project management layer to the PSP, and addresses performing software development and maintenance using high performance inter-disciplinary work teams. It is a level 5 process for managing project teams of 5-10 engineers and can be extended to larger projects. The bottom line for TSP is...
Five people working for 4 days will generate a far higher fidelity plan than one person working alone for 20 days.
They will do it faster than single person.
They will own it.
They will use it.

1. CMM builds organizational capability;
2. TSP builds quality products on cost and schedule;
3. PSP builds individual skill and discipline.