The Team Software Process Reading Notes

The conditions for teamwork (what is a team )?

At least two members share a common goal. Each member has a specific role and responsibilities. Only the dependency between team members can complete the task.

Effective teams (common features of efficient teams)

The goal of a skilled team is an important, defined, intuitive, and realistic task, resources are suitable for team members. They are active and committed to meeting the goals of the team. They cooperate with each other and support members to carry out work in accordance with the specifications. The team has the ability to innovate. (innovation is not a smart way, it requires creativity and hard work)

Building shorttive teams

Conditions for establishing an efficient team

The team members have established a common goal and their respective role teams reach an agreement on the way of working. The team members abide by a common working process. The team members participate in the formulation of the plan, every Member knows the role team in the plan and the management team negotiate with the plan. The Management Team reviews and accepts the negotiated plan team members to freely and regularly communicate with each other in the way they plan. team members form a whole, the members collaborate with each other to ensure that the target engineers are aware of their status and get feedback from their work in a timely manner, so that the leadership can maintain their initiative.

The formation of an efficient team requires team members to really understand what they want to do, to reach consensus on how to do their work, and to believe that the plan can be achieved. All these conditions are jointly established by the participating engineers. If these plans are built by them, they can almost make the leadership accept them completely.

Although the above conditions are required for an efficient team, the method for establishing these conditions is not very clear. The Organization needs to establish such an efficient team, while TSP provides such guidance.

An Operational Team Process

In order to do a well-defined job, the engineer needs a "operational process" that Dai Ming calls ". These processes precisely define how to do the job. Most of the software processes that are not well defined are very large and complex text descriptions are recorded in a thick book, and the operational process is a simple script, they are designed for True guidance when a team member works.

TSP provides a set of operational processes and guides engineers and managers through a series of team building steps. This process specifies the steps required to establish an efficient team. If there is no specific instruction manual, the engineers need to set up the details required by the Team's work environment on their own.

Although there are many ways to build a team, these methods require multiple individuals to work together to complete a specified job. In TSP, there is a four-day training process called "Team launch ". During this training, all team members participate in the development of a strategy, process, and plan for their projects. After completing this training, the team can work according to their own defined process.

Since defining these details involves a lot of skills and work, and few engineers have the experience or time to make all the necessary details, therefore, engineering teams generally only follow informal team building methods and team work processes. This is a waste of time, and the effect is not good.

If there is a defined process and a plan based on this process, the efficiency of engineers will be improved. Without such a process, they will stop at every step and think about what to do next and how to do it. Most engineering processes are complex and involve many steps. Without specific guidance, engineers are likely to skip some steps to do something that has no output, or waste some time deciding what to do next. TSP provides an operational process for building an engineering team, creating an efficient team environment, and guiding the team to do their work.

1. TSP is one of a series of methods that can help the engineering team develop and support more complex software systems more efficiently. CMM provides an overall improvement framework to improve the efficiency of software development. PSP provides engineering specifications that are required by engineering personnel to consistently use a defined, planned, and measured process. TSP provides the principle of combining the two. CMM and PSP provide the content and skills required by an efficient team, while TSP guides engineers to use them in practice. Therefore, TSP must be prepared on PSP and CMM and provide clear guidance on how to do the work.

The structure of the TSP

The main element 2 of TSP is shown. When participating in the TSP team, the personnel must know how to do the standard work ., PSP training provides the knowledge and skills required to use TSP. PSP training includes learning how to make detailed plans, collecting and using data generated during the process, developing Earned Value plans, tracking projects using Earned Value, and measuring and managing product quality, define and use operational processes. Engineers must be trained on these skills before they participate in the construction of the TSP team and follow the defined TSP process.

Although there are many ways to build a team, these methods require multiple individuals to work together to complete a specified job. In TSP, there is a four-day training process called "Team launch ". In a launch, all team members participate in the development of a strategy, process, and plan for their project. After completing this launch, the team can work according to their own defined process.

As shown in 3, The TSP team needs to relaunched regularly. Because the TSP process follows an iterative and evolutionary development strategy. Periodic relaunch is required so that each stage or cycle can be planned in advance based on the knowledge gained from the previous cycle. Relaunch also needs to update engineer's detailed plans because these detailed plans are generally accurate only for a few months. In TSP lauch, the team develops an overall plan and a detailed plan for the next three or four months. When all (or most) members complete the next project phase or cycle deduction, You can revise the overall plan if necessary, create a detailed plan for the next three or four months. This is guided by the relaunch process of TSP.

 

For more information, see