Mapping TSP to CMMI
April 2005 • Technical Report
Jim McHale, Daniel S. Wall Contributor Watts S. Humphrey, Michael D. Konrad
This 2005 report provides an essential element to facilitate the adoption of the TSP in organizations using CMMI, namely, a mapping of ideal TSP practices into the specific and generic practices of CMMI.
Software Engineering Institute
CMU/SEI Report Number
Please note that current and future CMMI research, training, and information has been transitioned to the CMMI Institute, a wholly-owned subsidiary of Carnegie Mellon University.
With the advent of CMMI (Capability Maturity Model Integration), development and maintenance organizations are faced with many issues regarding how their current practices, or new practices that they are considering adopting, compare to the new model. The Team Software Process (TSP), including the corequisite Personal Software Process (PSP), defines a set of project practices that has a growing body of evidence showing highly desirable process performance in terms of delivered product quality, schedule performance, and cost performance. TSP also has a history of favorable coverage with respect to the SW-CMM (Capability Maturity Model for Software), a major precursor to CMMI, as well as several real-world implementations that have helped organizations to achieve high maturity levels in a relatively short period of time.
This report provides an essential element to facilitate the adoption of the TSP in organizations using CMMI, namely, a mapping of ideal TSP practices into the specific and generic practices of CMMI. By having such a mapping (also known as a gap analysis), those involved with process improvement and appraisal efforts can more easily determine how well the organization or a particular project is implementing the TSP, how well projects using TSP might rate with respect to CMMI, and where and how to fill any gaps in CMMI coverage. Organizations already following an improvement plan based on CMMI may also determine how TSP adoption might help them to achieve broader, deeper, or higher maturity implementations of CMMI goals and practices.