In combination with the Personal Software Process (PSP), the so-called Team Software Process (TSP) provides a defined process framework that is designed to help teams of managers and engineers organize and produce large software projects. scale, which have sizes greater than several thousand lines of code. The objective of the TSP is to improve the quality and productivity levels of a software development project of a team, in order to help them reach the cost and time agreements in said development.
The initial version of the TSP was developed by Watts Humphrey in 1996, and the first Technical Report for TSP was published in 2000, sponsored by the United States Department of Defense. Watts Humphrey's book called "Introduction to the Team Software Process" (Addison Wesley Professional, Massachusetts, 1999), presents the TSP in detail and focuses on the process of building a software producing team, establishing team objectives, distributing roles, and other teamwork activities.
TSP operationBefore software engineers can participate in the TSP, it is required that they have already learned about the Personal Software Process, in such a way that the TSP can function properly. The TSP begins with a four-day process called takeoff. The takeoff is designed to begin the team building process and during this time, the teams and their managers set goals, define roles, evaluate risks and produce a team plan. The takeoff is usually done with a specifically trained coach, or with a leader who has already managed several projects that have used TSP for their development. Publications
wiki
