Team Software Process (TSP)
What is TSP?
The Team Software Process (TSP), along with the Personal Software Process, helps the high-performance engineer to
- ensure quality software products
- create secure software products
- improve process management in an organization
Engineering groups use the TSP to apply integrated team concepts to the development of software-intensive systems. A four-day launch process walks teams and their managers through
- establishing goals
- defining team roles
- assessing risks
- producing a team plan
After the launch, the TSP provides a defined process framework for managing, tracking and reporting the team's progress.
Using TSP, an organization can build self-directed teams that plan and track their work, establish goals, and own their processes and plans. These can be pure software teams or integrated product teams of 3 to 20 engineers.
TSP will help your organization establish a mature and disciplined engineering practice that produces secure, reliable software. Find out how you can use TSP to strengthen your security practices.
TSP is also being used as the basis for a new measurement framework for software acquirers and developers. This effort is the Integrated Software Acquisition Metrics (ISAM) Project.
For More Information
Find out how to Get Started using TSP and learn about current policies and procedures for maintaining an authorization.
For a more detailed description of the PSP and TSP, read the article Pathways to Process Maturity: The Personal Software Process and Team Software Process by Watts Humphrey, and watch his QuickTime video, "Competing in the Software Age."
The TSP Symposium meets annually to share ideas and experiences.
For more information about TSP, send email to tsp@sei.cmu.edu.
return to top | TSP/PSP main page