Part of a series on |
Software development |
---|
In combination with the personal software process (PSP), the team software process (TSP) provides a defined operational process framework that is designed to help teams of managers and engineers organize projects and produce software for products that range in size from small projects of several thousand lines of code (KLOC) to very large projects greater than half a million lines of code. The TSP is intended to improve the levels of quality and productivity of a team's software development project, in order to help them better meet the cost and schedule commitments of developing a software system.[1][2][3][4]
The initial version of the TSP was developed and piloted by Watts Humphrey in the late 1990s[5] and the Technical Report[6] for TSP sponsored by the U.S. Department of Defense was published in November 2000. The book by Watts Humphrey,[7] Introduction to the Team Software Process, presents a view of the TSP intended for use in academic settings, that focuses on the process of building a software production team, establishing team goals, distributing team roles, and other teamwork-related activities.
{{cite journal}}
: Cite journal requires |journal=
(help)