Introduction to the Team Software Process(sm)

Rating:
Summary: totalitarian control is not the answer
Review: 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.

Rating:
Summary: Outstanding Reference for Software Engineers
Review: 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!

Rating:
Summary: Good introduction to creating software in a team
Review: 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.