Team software process

from Wikipedia, the free encyclopedia

The Team Software Process ( TSP ) is a method for software development teams to optimize themselves .

It was developed by Watts S. Humphrey at the Software Engineering Institute (SEI) at Carnegie Mellon University / Pittsburgh in order to give software developers a method with which they can actually implement the requirements of the Capability Maturity Model (CMM) can.

The Personal Software Process (PSP) was developed for individual developers.

Objectives

The use of TSP is intended to achieve the following goals:

  • Better and more precise planning (thus better fulfillment of planned dates)
  • Improve the quality of the product
  • Lower costs of projects (total cost of ownership)

According to a study by Capers Jones, TSP is one of the most successful development methods in terms of timing, quality and budget.

functionality

TSP is based on PSP, i.e. H. every developer has to use PSP. Other team members such as the team lead (similar to Scrum Master) and testers should also receive special training. Every new development project begins with the so-called launch, in which the rough planning is made to meet the management goals (and also to what extent these goals cannot be met), the backlog is created and a detailed plan for the next cycle (the next iteration / sprint) . The duration of the cycle can be between two weeks and three months. Within the cycle, the progress of the project is discussed in regular team meetings (at least weekly) and the plan is adjusted if necessary. At the end of the cycle, the cycle is analyzed in the so-called PostMortem (analogous to the retro perspective of Scrum), problems discussed, possibly improvements planned for the future (lessons learned), and the next cycle planned in detail. A TSP coach should look after the team throughout the project.

Important concepts:

  • self-organizing teams (the team creates the plan)
  • agile handling of processes (the team regularly reflects on the processes and improves them)
  • Iterative approach (breaking up the development in cycles, analogous to the sprints of Scrum)

literature

  • Watts S. Humphrey: TSP - Coaching Development Teams . Addison-Wesley, 2006, ISBN 0-201-73113-4 .
  • Watts S. Humphrey: TSP - Leading a Development Team . Addison-Wesley, 2005, ISBN 0-321-34962-8 .
  • Watts S. Humphrey: Introduction to the Team Software Process . Addison-Wesley, 2000, ISBN 0-201-47719-X .

Individual evidence

  1. ^ Capers Jones: Evaluating ten software development methodologies . 2013. Archived from the original on September 15, 2013.

Web links