TSP and CMMI are two SEI technologies focused on improving
Posted: Sat Feb 22, 2025 8:50 am
Organizational processes. Both share the same goals: helping companies develop quality products within the assigned time and budget.
On the one hand, CMMI is a reference model and on the other hand, TSP is an implementation of high-performance processes that is used by self-managed teams. While CMMI considers organizational aspects and infrastructure, TSP focuses on developing process discipline and a quality culture at a personal level (through PSP) and builds high-performance teams.
One of TSP's strengths is the quality of the products developed: The average Tunisia Mobile Database number of errors reported after product delivery is 0.06 per thousand new or modified lines of code (KLOC) while the average for CMMI N5 companies is 1.05 [04].
CMMI is a how, while TSP is a product with process elements, training materials, and a framework for metrics, planning, and quality. The weaknesses of TSP can be solved with the organizational approach of CMMI. The risk of implementing bureaucratic processes that do not add value to the company is mitigated by using TSP.
Instead of continuing to consider these technologies as rivals and independent, the technologies should be combined taking advantage of the synergy that is produced [5]. The main idea of combining TSP and CMMI is to reduce the time to reach CMMI level 3 (from 4 years to 18 months) by obtaining the institutionalization of defined processes that are used in self-directed teams committed to the plans, with a strong personal focus on quality, with short test cycles, having high performance, and making use of an infrastructure to manage continuous improvement [5].
On the one hand, CMMI is a reference model and on the other hand, TSP is an implementation of high-performance processes that is used by self-managed teams. While CMMI considers organizational aspects and infrastructure, TSP focuses on developing process discipline and a quality culture at a personal level (through PSP) and builds high-performance teams.
One of TSP's strengths is the quality of the products developed: The average Tunisia Mobile Database number of errors reported after product delivery is 0.06 per thousand new or modified lines of code (KLOC) while the average for CMMI N5 companies is 1.05 [04].
CMMI is a how, while TSP is a product with process elements, training materials, and a framework for metrics, planning, and quality. The weaknesses of TSP can be solved with the organizational approach of CMMI. The risk of implementing bureaucratic processes that do not add value to the company is mitigated by using TSP.
Instead of continuing to consider these technologies as rivals and independent, the technologies should be combined taking advantage of the synergy that is produced [5]. The main idea of combining TSP and CMMI is to reduce the time to reach CMMI level 3 (from 4 years to 18 months) by obtaining the institutionalization of defined processes that are used in self-directed teams committed to the plans, with a strong personal focus on quality, with short test cycles, having high performance, and making use of an infrastructure to manage continuous improvement [5].