Using PSP/TSP in a Performance Review
November 2014 • Presentation
This TSP Symposium 2014 presentation explores the use of PSP/TSP data in the developers' and testers' performance reviews on two TSP projects and results to date.
This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.
Beckman Coulter has been using Team Software Process (TSP) since 2009, and today we have multiple TSP projects. This TSP Symposium 2014 presentation explores the use of Personal Software Process (PSP)/TSP data in the developers’ and testers’ performance reviews on two TSP projects. These two projects include 15 developers and 7 testers total. The projects include both new and maintenance development. Beckman Coulter uses a typical performance review process with goal setting in Q1 of the year, midterm reviews with managers, and final reviews with ratings at year’s end. Goals are weighted and ratings are 1 through 5, with 5 being the highest rating. The use of PSP/TSP in performance reviews for the two projects started informally in 2013 by holding developers and testers responsible for their schedule planning and general use of PSP data. There were no specific performance goals, however, and individuals were rated with subjective input from their functional manager. It was decided to be more formal for the 2014 performance year, and the manager developed specific goals based on the data and objectives of PSP/TSP. Individuals were brought into the process for goal setting, resulting in goals that strategically focused on both individual and team improvements. The 2014 performance goal objectives are reviewed and discussed along with the results to date.