From PSP to TSP to CMM

Summary
Management is still the key to the success or failure of software development projects. China's software industry needs to be quickly transferred to the process-centric, taking the road of industrial production. However, relying solely on the Capability Maturity Model CMM cannot truly improve process management. Only by organically integrating with PSP and TSP can the continuous improvement of software processes be achieved.
Preface
This article describes and analyzes the process improvement issues of software development in a step-by-step manner based on various processes of process management. It starts from how to control, manage, and improve the way individuals work, to how to create efficient and self-managed engineering teams, how can engineering personnel become qualified project team members, as well as how managers provide guidance and support to groups, they have been talking about how to define and implement appropriate process specifications that comply with CMM standards throughout the company, and achieve a virtuous circle of continuous improvement.
If we improve the process according to the ideas and systems mentioned in this article, the company's process work will be steadfast and effective. In addition, individuals and companies will benefit from the following benefits:
1. Improve Personal abilities. PSP shows you how to develop a plan and track your work, provide data on the effectiveness of your work, and identify your own strengths and weaknesses, this allows you to constantly understand and improve your skills and talents, and make full use of your unique talents in your work. TSP shows you how to become a qualified project team member and how to create an efficient and self-managed engineering team to achieve efficient collaborative development.
2. Improve the company's process. Combined with TSP and PSP, it is easy to establish a standardized development process throughout the company. In addition, the specific practices and effective ideas provided in this Article can help enterprises improve their management capabilities, including software process management, project management, and continuous improvement processes.
Personal development capability
PSP (personal software process) is a self-continuous improvement process that can be used to control, manage, and improve the way individuals work. It is a structured framework that includes software development tables, guidelines, and procedures. PSP and specific technologies ( Program Design Language, tool, or design method) is relatively independent, and its principles can be applied to almost any software engineering task. PSP can describe the principles of individual software processes, help software engineers make accurate plans, determine the steps that software engineers should take to improve product quality, and establish benchmarks for measuring the improvement of individual software processes; determine the impact of process changes on the software engineer's capabilities.
Team development capability
TSP (personal software process) puts forward a complete set of principles, strategies, and methods for the definition, measurement, and reform of group software processes, combine the management of implementation required by CMM with the skills required by PSP developers to deliver high-quality software on time and keep costs within the budget. In TSP, we talked about how to create an efficient and self-managed engineering team, how engineering personnel can become qualified project team members, and how management personnel can provide guidance and support to groups, how to maintain a good engineering environment so that the project team can make full use of its own level and other software engineering management issues.
Software Development Process
Software Development Process (SDP) is an organization-level process definition, measurement, and improvement across the company. It consists of three parts: development lifecycle, project management practices, and software engineering processes. It is built on the basis of CMM. It integrates specific methods that are effective in practice, focuses on practicality and effectiveness, and achieves the ultimate goal of project delivery predictability and quality assurance.
Development lifecycle. A professional software development company should have a very detailed software development cycle model based on its own development model, including the development phase, tasks in each phase, the specific work and deliverables of the task, the development tools and technologies used, as well as the division of labor, can even be subdivided into general review meetings. The development of all content in the form of a network diagram or flow chart clearly standardized, so that the high-level can be clear on the overall process of the project, so that the project managers can easily track the situation of the task, this makes every developer very clear about their tasks and their roles in the overall development. Only such a life cycle model makes sense for specific development. It is the "Bible" developed by all companies. All technology development and process development must be carried out on this basis, and based on this.
Project management practices. Based on the company's software life cycle and CMM standards, a series of suitable process practices are established for the company. Several key process practices include quality assurance, demand management, configuration management, planning and tracking, and risk control. Then, a project measurement tool is created to manage projects more accurately. If your enterprise does not perform CMM authentication, I think other practices can be avoided first. By putting these basic tasks in place, we can refer to level 3, Level 4, and level 5 practices to improve and supplement these practices, which can completely control the software development process. That is to say, learning CMM is to absorb its essence and spirit.
Continuous improvement process. With standardized development lifecycle models and project management practices, you can find a way to design a virtuous circle mechanism that is based on data, constantly measuring and improving, and continuously improving the enterprise's development capabilities. The model diagram is as follows:

Organic combination of the three
PSP, TSP, and CMM provide an integrated and three-dimensional software process reform framework for the software industry. The three work together with each other to form an integral whole, like a stool with three legs, which is indispensable. In 18 key process domains of the Software Capability Maturity Model CMM, 12 are closely related to the personal software process PSP, and 16 are closely related to the group software process TSP. Therefore, familiarity with individual software processes and group software processes can not only help engineers improve work efficiency, but also facilitate organizational process improvement.
To improve the company's process more effectively, I suggest a step-by-step approach here. As shown in:

PSP focuses on personal skills and can instruct software engineers how to ensure their work quality, estimate and plan their work, measure and track their individual performance, manage Software processes and product quality. After PSP learning and practical formal training, software engineers can make full use of PSP in their project work, thus ensuring the overall progress and quality of the project.
TSP focuses on the team's efficient work and product delivery capabilities, and integrates PSP's engineering skills to tell software engineers how to integrate individual processes into the group's software processes, by telling the management layer how to support and authorize the project team, stick to high-quality work, and manage projects based on data, it shows how to produce high-quality products.
CMM focuses on organizational capabilities and high-quality products. It provides management methods to evaluate organizational capabilities, identify priority improvement needs, and track improvement progress. To expand to the software development process SDP mentioned in this article, it is of a higher level and higher organizational significance.
Summary
If an organization is improving according to CMM, PSP and TSP are completely compatible with CMM. If an organization does not follow the CMM improvement process, training on PSP and TSP can lay a solid foundation for future CMM practices. In short, the implementation of CMM alone cannot completely upgrade the Capability Maturity. Chinese enterprises should also organically combine the implementation of CMM with the implementation of PSP and TSP to maximize the effectiveness of CMM.