TSP(SM) Coaching Development Teams

Front Cover
Pearson Education, Apr 10, 2006 - Computers - 448 pages

Most modern software development projects require teams, and good teamwork largely determines a project’s success. The Team Software Process (TSP), created by Watts S. Humphrey, is a set of engineering practices and team concepts that produce effective teams, thereby helping developers deliver high-quality products on time and within budget. TSP bridges Humphrey’s seminal work on the Capability Maturity Model (CMM), an improvement framework for the entire software organization, and his Personal Software Process (PSP), practices designed to improve the work of individual developers.

Typical first-time TSP teams increase productivity by more than 50 percent while greatly increasing the quality of their delivered products. However, TSP teams only continue to improve under the guidance of a capable coach. One industrial-strength team, for example, increased its productivity by an additional 94 percent and reduced test defects by 85 percent through three consecutive TSP quarterly product release cycles. Without competent coaching, teams often do not progress much beyond the initial one-time improvement seen after the introduction of the TSP.

Humphrey distinguishes between TSP coaching and TSP leadership, explaining why the skillful performance of both functions is critical. In this practical guide, he shares coaching methods that have repeatedly inspired TSP teams and steered them toward success. With the help of a coach, TSP teams undergo a brief but intense project launch in which they define their own processes, make their own plans, and negotiate their commitments with management, resulting in dramatically enhanced performance.

Whether you are considering the TSP or are actively implementing it, TSPSM–Coaching Development Teams provides the invaluable examples, guidelines, and suggestions you need to get started and keep developing as a team coach. It’s meant to complement Humphrey’s other books, TSPSM–Leading a Development Team and PSPSM: A Self-Improvement Process for Software Engineers. Together, the three works offer a rich resource for improving your software development capabilities.

 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Contents

14The Management Meeting
15The Launch Postmortem
16Relaunching a Team Project
Part IIICoaching a TSP Project
17PostLaunch Coaching
18Maintaining the Plan
19Managing Quality
20The Project Postmortem

2Team Behavior
3The Coaching Job
4Teambuilding
Part IILaunching a TSP Team
5Launch Preparation
6The Team Charter
7Team Goals
8TeamMember Roles
9Team Planning
10The Overall Plan
11The Quality Plan
12Detailed Planning
13Managing Risk
Part IVTSP Extensions
21Team Variations
22Functional Teams
23Multiple Teams
24Integrated Development Teams
Part VMaintaining a TSP Team
25Developing Teamwork
26Coaching Ethics
27The Coaching Team
28Being a Team Coach
INDEX
Copyright

Other editions - View all

Common terms and phrases

About the author (2006)

Known as “the father of software quality,” Watts S. Humphrey is the author of numerous influential books on the software-development process and software process improvement. Humphrey is a fellow of the Software Engineering Institute (SEI) at Carnegie Mellon University, where he founded the Software Process Program and provided the vision and early leadership for the original Capability Maturity Model (CMM). He also is the creator of the Personal Software Process (PSP) and Team Software Process (TSP). Recently, he was awarded the National Medal of Technology–the highest honor given by the president of the United States to America's leading innovators.

Bibliographic information