What are TSP?

The Team Software Process (TSP) is a structured framework that helps software development teams improve their productivity and software quality through well-defined processes. TSP extends the Personal Software Process (PSP) by focusing on team collaboration, planning, and performance tracking.

Why were these models created, and who developed them?

Origin and Development

Team Software Process (TSP) were developed by Watts S. Humphrey at the Software Engineering Institute (SEI), Carnegie Mellon University, in the 1990s.

Why Were They Created?

• To address low software quality caused by poor planning, lack of structured processes, and undisciplined development practices.
• To provide engineers and teams with structured methods for improving software quality and predictability.
• To help developers teams (TSP) adopt disciplined, data-driven approaches for software development.
• To enhance estimation accuracy, defect management, and productivity through well-defined workflows.

Main Elements

3.1 Team Roles

Each team member has a defined role to ensure responsibilities are distributed efficiently. Some key roles include:

• Team Leader: Coordinates the team, ensures communication, and resolves conflicts.
• Planning Manager: Handles project schedules and work breakdown.
• Process Manager: Monitors process compliance and improvements.
• Quality Manager: Tracks defect data and ensures high-quality code.