Sin título

TSP Teamworking Process

Leading the team

Communication

Maintaining the plan

Rebalancing team workload

TSP quality management

Process Discipline

Issue Tracking

They defined the process for doing the job. In this process the team leader monitors the work to ensure that everyone follows the process and plan that the team produced.

The team leader is responsible for guilding and motivating the team members. His principal responsability is to maintain the team's motivation and energy.

Engineers generally discuss problems in the weekly team meeting. The team leader checks that each issue is one that the team should handle if it its, and then the team tracks every issue with the issue tracking log (ITL).

The team leader is responsive for maintaining open and effective team communications. Is a key part of maintaining the team's energy and drive and responsabilities.

Management reporting

During the weekly meeting, the leader first reviews project statues and any management issues or cencerns. Then they plan for the next week their role-management activities, and the status of the risks they are tracking.

TSP teams tracks progress agains the plan every week using a method called earned value [Humphrey 95].

Estimating project completion

With a formula to calculate the tasks percentage we first multiply the 100% per the hours task, divide the planned hour task and finally we get the percentage value. Next we manage the task hours and the earned values in which these are planned and actual results that are weekly.

These can cause a team to be inefficient. It is not efficient. Unless every member of the team is always fully occupied, the team cannot be fully effective.

Relaunching the project

To manage quality, teams must establish quality measures, set quality goals, establish plans to meet these goals, measure progress agains the plans, and take remedial action.

Once the engineers have completed a TSP launch and have detailed personal plans, they can generally rebalance team workload in only an hour or two.

QM: 1- quality plan

QM: 1- identifying quality problems

Based on the estimated size of the product and historical data con defect injection rates, they estimate how many defects they will inject in each phase.

For every small projects, it can take a substantial amount of time to examine the process data.

QM: 1- finding and preventing quality problems

TSP quality measures can indicate likely quality problems even before the first compile, and they provide a reliable measure of module or component quality before the start of integration or system test.

Once a TSP has identified the modules that most likely have quality problems.

In TSP the design can further reduce defect injection rates by ensuring that the team produces a complete and high-quality design