Most important, you are interested in and concerned about software quality. The quality strategy is one of the key differences between the TSPi and traditional ways of developing software. Whereas traditional software methods wait to address quality during testing, the TSPi focuses on quality at the be-ginning of the process. The TSPi thus adds tasks and development time to the beginning of the process. Although this added time will be more than recovered by reduced time in compiling and testing, the amount of time saved depends on the degree to which the engineers faithfully follow the TSPi process. When even one engineer produces a poor-quality program, the entire team will be delayed by excessive testing and repair time.