I have been busy these two days, busy participating in TSP training, busy adding new features, busy finding more time to see books.
TSP is a good thing. My TEAM will become the first TSP of the Chinese Institute. I became the Data Manager of UI Team. The DATA collection and finishing work of the entire team.
The advantage of TSP is that it can develop this very abstract process, standardize, and make it a predictable. In other words, when a development Team uses TSP to specify its development process, after accumulating the Data from the foot, the group's Leader will have enough confidence to predict and estimate the future project. Of course, this is what you can take out full evidence to say to your boss: "I need more time." And this predictive ability is not just for a Team, each member in the Team can also achieve the same PSP. Such an capability. In fact, what is true, it should be like this. When each member in Team has its own prediction, this Team can be given this ability.
Another benefit of TSP is to emphasize the workflow for Team members in software development. It makes it clear to help each member arrange their work in the stage and practice. When the entire Team starts to complete TSP Worshop, each person's work Calendar is also confirmed. Each member of the Team is clear and ordered, and each person's work has also become measured.
Some people say TSP is a methodology. I think this statement is correct. TSP is the same as PSP, they also templates, but not to provide molds; they have norms but no specifications. TSP only provides users with a guidance, even a way of thinking. What you have to do is to adjust the TSP to apply your job.
