icon-carat-right menu search cmu-wordmark

Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report

Technical Report
This 2010 report communicates status, progress, lessons learned, and results on a joint collaboration between the SEI and NAVAIR.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2010-TR-008
DOI (Digital Object Identifier)
10.1184/R1/6573734.v1

Abstract

The purpose of this report is to communicate status, progress, lessons learned, and results on a joint collaboration between the Software Engineering Institute (SEI) and Naval Air Systems Command (NAVAIR). The collaboration is referred to as Team Software Process Integration (TSPI). This report describes the progress and performance of extending the Team Software Process (TSP) to systems engineering as a pilot project with the AV8B Systems Engineering Team. Early results of applying TSPI suggest some encouraging trends. The motivation for assembling this report is to share lessons and experiences with other industry and government organizations interested in applying TSP in a non-software setting.  

The TSPI effort leverages the SEI Personal Software Process (PSP) and Team Software Process (TSP) research and body of practice. Projects that have adopted these methods have shown a dramatic increase in product quality as well as increased fidelity to their schedule and effort estimates. The methods are supported by a doctrine that trains and sustains performance and quality improvement in organizations.

Cite This Technical Report

Carleton, A., Over, J., Schwalb, J., Kellogg, D., & Chick, T. (2010, March 1). Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report. (Technical Report CMU/SEI-2010-TR-008). Retrieved October 6, 2024, from https://doi.org/10.1184/R1/6573734.v1.

@techreport{carleton_2010,
author={Carleton, Anita and Over, James and Schwalb, Jeff and Kellogg, Delwyn and Chick, Timothy A.},
title={Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report},
month={Mar},
year={2010},
number={CMU/SEI-2010-TR-008},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6573734.v1},
note={Accessed: 2024-Oct-6}
}

Carleton, Anita, James Over, Jeff Schwalb, Delwyn Kellogg, and Timothy A. Chick. "Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report." (CMU/SEI-2010-TR-008). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, March 1, 2010. https://doi.org/10.1184/R1/6573734.v1.

A. Carleton, J. Over, J. Schwalb, D. Kellogg, and T. Chick, "Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Report CMU/SEI-2010-TR-008, 1-Mar-2010 [Online]. Available: https://doi.org/10.1184/R1/6573734.v1. [Accessed: 6-Oct-2024].

Carleton, Anita, James Over, Jeff Schwalb, Delwyn Kellogg, and Timothy A. Chick. "Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report." (Technical Report CMU/SEI-2010-TR-008). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Mar. 2010. https://doi.org/10.1184/R1/6573734.v1. Accessed 6 Oct. 2024.

Carleton, Anita; Over, James; Schwalb, Jeff; Kellogg, Delwyn; & Chick, Timothy A.. Extending Team Software Process (TSP) to Systems Engineering: A NAVAIR Experience Report. CMU/SEI-2010-TR-008. Software Engineering Institute. 2010. https://doi.org/10.1184/R1/6573734.v1