Introduction to the Team Software Process [Hardcover]

Watts S. Humphrey (Author)

Book Description

ISBN-10: 020147719X | ISBN-13: 978-0201477191 | Publication Date: September 3, 1999 | Edition: 1

Watts Humphrey is the visionary behind the Capability Maturity Model (CMM) and the Personal Software Process (PSP). The CMM contains a framework for software process improvement at the organizational level. The PSP builds the self-discipline needed for individual programmers to work efficiently and effectively. The author's new Team Software Process (TSP) details methods that should guide the formation of a software development team and that will enhance the team's productivity. This book describes an introductory version of TSP, ideal for smaller projects but also useful for learning basic forms and procedures that apply to other development projects. Methods presented include: how to establish roles; how to conceive, design, and plan a project; and how to track and report on progress. The book walks students through a complete development cycle, illustrating: how best to use the talents at hand; how to formulate well-defined goals; how to coordinate activities for maximum progress; how to promote effective communication; and how to alleviate many of the conflicts that undermine teamwork. The book provides two project exercises, with prescribed development goals and team roles, to help students master this proven process.

Editorial Reviews

Amazon.com Review

Aimed at the computer science student, Introduction to the Team Software Process provides a textbook-style introduction to the author's Team Software Process (TSP), a rigorous group-based design process that stresses planning, metrics, scripts, accountability, and ultimately, higher code quality. Although best suited for a semester- or two-semester-length course, this book provides a useful model for any team development effort.

This textbook focuses squarely on the team-based nature of successful software development. The author, who also invented the Personal Software Process (PSP), outlines the steps for "staffing" a classroom-based software project with different multiple member roles, such as team leaders and development managers. The Team Software Process (TSP) outlined here stresses accountability through numerous scripts and metrics. (An appendix features over 80 pages of scripts and forms that would be used over the course of the semester.) Not only does the author provide a thorough guide to choosing the right team role that fits your personality and skills, but several sections offer some "motivational speaking" on the advantage of "discipline," both as a person and software engineer.

This book does a particularly good job of defining a team's role for each stage in the development process, beginning from the initial planning stages to requirements definition, implementation, testing, and postmortem followup. There are hints for dealing with missed deadlines, staffing, and design problems.

The reality is that teams are used throughout the software industry, but many computer science students do not get much experience working in successful teams. As a first encounter with team development, Introduction to the Team Software Process provides a model for serious implementation of a smart, rigorous software method that can put readers on the right track with group development. --Richard Dragan

Topics Covered: Team Software Process (TSP) basics and scripts, building production software teams, team goals, team roles, planning, risk management, quality plan, requirements, design principles, product implementation, integration and system testing, test planning, defect tracking, documentation, conducting postmortems, team leaders, development managers, planning managers, quality/process managers, support managers.

From the Back Cover

Watts Humphrey is the visionary behind the Capability Maturity Model (CMM)(R) and the Personal Software Process (PSP) (sm). The CMM contains a framework for software process improvement at the organizational level. The PSP builds the self-discipline needed for individual programmers to work efficiently and effectively. The author's new Team Software Process (TSP) (sm) details methods to guide the formation of software development teams, to motivate their work, and to enhance their productivity.

This book describes an introductory version of TSP, ideal for smaller projects but also useful for learning basic techniques and procedures that apply to other development projects. Methods presented include:

• how to establish roles;
• how to conceive, design, and plan a project;
• how to track and report on progress.

The book walks readers through a complete development cycle, illustrating:

• how best to use the talents at hand;
• how to formulate well-defined goals;
• how to coordinate activities for maximum progress;
• how to promote effective communication;
• how to alleviate many of the conflicts that undermine teamwork.

Team members should not have to expend valuable time and energy reinventing ways to organize and run their team. By following a proven process, the team will more quickly be able to focus on the successful completion of the project itself. To help a team course apply these methods, the book provides two project exercises, with prescribed development goals and team roles.

020147719XB04062001

See all Editorial Reviews

Product Details

• Hardcover: 496 pages
• Publisher: Addison-Wesley Professional; 1 edition (September 3, 1999)
• Language: English
• ISBN-10: 020147719X
• ISBN-13: 978-0201477191
• Product Dimensions: 9.6 x 6.6 x 1.2 inches
• Shipping Weight: 1.6 pounds (View shipping rates and policies)
• Average Customer Review: 3.3 out of 5 stars  See all reviews (6 customer reviews)
• Amazon Best Sellers Rank: #503,557 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

21 of 21 people found the following review helpful:

3.0 out of 5 stars Good introduction to creating software in a team, August 29, 2000

By 

Proggoddess "proggoddess" (New York) - See all my reviews

This review is from: Introduction to the Team Software Process (Hardcover)

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.

9 of 14 people found the following review helpful:

5.0 out of 5 stars Outstanding Reference for Software Engineers, October 22, 2000

By A Customer

This review is from: Introduction to the Team Software Process (Hardcover)

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!

3 of 5 people found the following review helpful:

5.0 out of 5 stars Excellent Process for Software Devleopment, March 30, 2005

By 

Michael (Atlanta, GA USA) - See all my reviews

This review is from: Introduction to the Team Software Process (Hardcover)

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.