Customer Reviews

Introduction to the Team Software Process

5 star:		(3)
4 star:		(0)
3 star:		(1)
2 star:		(0)
1 star:		(2)

 

 

This is a good introduction to working in a team and using good software engineering techniques such as planning and inspections. It is geared for undergraduate students, therefore the managerial roles have been created. This would probably not work out of the box for an organization that is already set up. For students, the manager roles give each team member ownership in the product while making sure each aspect of good engineering has an advocate.

The processes are written as scripts. These are very easy to follow and take the guesswork out of how to do each step in the lifecycle.

This is a process book therefore there is not a lot of technically-oriented information in the book. For example, the book tells you that you must design your software. It does not give many guidelines on what a good (object-oriented, client-server, real time, etc.) design might look like. In addition, some of the data bookkeeping is long and involved. A good tool would help with this.

Overall, this is a good tutorial and a good reference book. I used this book as a graduate student, and I continue to pull ideas out of it for use in my work.

I've been involved with many different projects in a team environment. This book contains some of the best and most respected procedures to complete a team project. I've used these methods and they work well! The principles outlined in this book apply to more than just software engineering. Take a look! You'll be glad you did!

My software team used the TSP for developing a 3 release Java application over 12 weeks. There is a stiff learning curve, but once you learn it, you can quickly realize the results. This book takes the guesswork out of developing software. If you have a dedicated team that will take the time to learn it, you will be very happy with the results.

I can't understand how anyone could apply TSP or PSP and actually get any work done. My college professor used this book as well as PSP and let me say that it has no use in the real world. Filling out forms and counting lines of code only wastes the developer's time. Any manager that uses this book as a model for developing software has no clue about what it takes to develop software that meets the customer's expectations, is well designed and well tested. Any process that emphasizes lines of code as a useful metric for making estimations is not worth the paper it is written on.

Excelente obra que nos muestra la forma en como sacar provecho de los equipos de trabajo en el desarrollo de proyectos de software. Felicito al Sr. Watts. S. Humprey por su visión en el tema.

A state-of-the-art process for producing PL/I programs on punchcards. If you can master PSP/TSP, you will be more effective than 99% of all software developers at filling out forms and producing status reports. A shockingly wasteful approach to quality management.