Two extensive studies have been undertaken by the SEI since the TSP was first introduced
in 1997.
The Team Software
Process (TSP) in Practice: A Summary of Recent Results
Noopur Davis and Julia Mullaney
Technical Report CMU/SEI-2003-TR-014, September 2003
Abstract: Most software organizations are facing critical business needs for
better cost and schedule management, effective quality management, and
cycle-time reduction. The Team Software Process addresses these critical
business needs. This report provides results and implementation data from
projects and individuals that have adopted the TSP. The results show that TSP
teams are delivering essentially defect-free software on schedule, while
improving productivity. These data can be used for benchmarking and planning,
motivation, lessons learned, and other guidance to those currently using the TSP
or considering its use. The report also illustrates adoption experiences of
practitioners in the field, including TSP team members, their managers, and
their coaches and instructors.
Relating the Team
Software Process (TSP) to the Capability Maturity Model®
for Software (SW-CMM®)
Noopur Davis and Jim McHale
Technical Report CMU/SEI-2002-TR-008, March 2003
Organizations using the Capability Maturity Model for Software
(SW-CMM)
to guide their software process improvement efforts often struggle with
implementation details. The Team Software Process
(TSP)
was designed to implement effective, high-maturity processes for project teams.
The TSP contains a framework as well as a set of processes, procedures,
guidelines, and tools for project teams to use in the production of high-quality
software on time and on budget.
Since the SW-CMM describes what an organization at a high
level of process maturity should be doing, and the TSP describes how
high-maturity processes are implemented for project teams, the question arises:
If all projects in an organization were using the TSP, would the organization
exhibit the characteristics of high process maturity, as described in the SWCMM?
To help answer this question, we performed an analysis of the degree to which
the SW-CMM is addressed by the TSP. Each key practice described in the SW-CMM
was classified as having an organizational or project scope, or both. Then each
practice was examined to determine how it was addressed by the TSP. The results
presented in this report show that the TSP implements a majority of the key
practices of the SW-CMM.
The Team
Software Process (TSP): An Overview and Preliminary Results of Using Disciplined
Practices
Donald McAndrews
Technical Report CMU/SEI-2000-TR-015, November 2000
Abstract: This report describes the TSP technology as an implementation strategy
for teams that are attempting to apply disciplined software process methods. It
provides some of the background and rationale for the TSP approach, as well as
an
overview of the technology. Then, the report presents initial results of the use
of the
TSP technology in four different organizational settings. In each of these
organizations, the data show that defect densities found in system-level test
activities and the actual duration of these system-level tests were reduced
significantly with the use of the TSP. In addition, the accuracy of software
estimates
improved, and the variation in estimation accuracy was significantly reduced.
Based
on the analysis of these results, some assertions are made to help organizations
set goals for improvement.
