Introduction to the Team Software Process(sm)
Published on 27. September 1999
Book
Hardback
496 pages
978-0-201-47719-1 (ISBN)
Description
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.
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.
More details
Person
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.
Content
(Each chapter, except Chapter 18, concludes with a Summary.)
Preface.
I. INTRODUCTION.
1. TSPi Overview.
What Is TSPi?
TSPi Principles.
The TSPi Design.
TSPi Structure and Flow.
The TSPi Process.
The Textbook Structure and Flow.
2. The Logic of the Team Software Process.
Why Projects Fail.
Common Team Problems.
What Is a Team?
Building Effective Teams.
How Teams Develop.
How TSPi Builds Teams.
References.
II. THE TSPI PROCESS.
3. Launching a Team Project.
Why Conduct a Team Launch?
Team Goals.
Team-Member Goals.
The Role Goals.
The TSPi Launch Scripts.
4. The Development Strategy.
Planning First.
What Is a Strategy?
The Conceptual Design.
Risk Management.
A Reuse Strategy.
The Strategy Scripts.
5. The Development Plan.
The Need for Planning.
The TSPi Planning Process.
The TSPi Support Tool.
The Development Plan Scripts.
Tracking the Work.
The Quality Plan.
Reference.
6. Defining the Requirements.
What Are Requirements?
Why We Need Requirements.
Requirements Changes.
The Software Requirements Specification.
The TSPi Requirements Scripts.
References.
7. Designing with Teams.
Design Principles.
Designing in Teams.
Design Standards.
Designing for Reuse.
Designing for Usability.
Designing for Testability.
Design Reviews and Inspections.
The TSPi Design Scripts.
References.
8. Product Implementation.
Design Completion Criteria.
Implementation Standards.
The Implementation Strategy.
Reviews and Inspections.
The IMP Scripts.
Reference.
9. Integration and System Testing.
Testing Principles.
The TSPi Testing Strategy.
The Build and Integration Strategy.
The System Test Strategy.
Test Planning.
Tracking and Measuring Testing.
Documentation.
The TSPi TEST Scripts.
References.
10. The Postmortem.
Why We Need a Postmortem.
What a Postmortem Can Do for You.
The Process Improvement Proposal.
The TSPi Postmortem Scripts.
Reference.
III. THE TEAM ROLES.
11. The Team Leader Role.
The Team Leader's Goals.
Helpful Team Leader Skills and Abilities.
The Team Leader's Principal Activities.
The Team Leader's Project Activities.
12. The Development Manager Role.
The Development Manager's Goals.
Helpful Development Manager Skills and Abilities.
The Development Manager's Principal Activities.
The Development Manager's Project Activities.
13. The Planning Manager Role.
The Planning Manager's Goals.
Helpful Planning Manager Skills and Abilities.
The Planning Manager's Principal Activities.
The Planning Manager's Project Activities.
14. The Quality/Process Manager Role.
The Quality/Process Manager's Goals.
Helpful Quality/Process Manager Skills and Abilities.
The Quality/Process Manager's Principal Activities.
The Quality/Process Manager's Project Activities.
References.
15. The Support Manager Role.
The Support Manager's Goals.
Helpful Support Manager Skills and Abilities.
The Support Manager's Principal Activities.
The Support Manager's Project Activities.
IV. USING THE TSPI.
16. Managing Yourself.
Being Responsible.
Striving for Defined Goals.
Living by Sound Principles.
Your Opinion of Yourself.
Your Opinion of Others.
Your Commitment to Excellence.
Reference.
17. Being on a Team.
The Jelled Team.
Teamwork Obligations.
Communication Among Team Members.
Making and Meeting Commitments.
Participation in the Team's Activities.
Team-building Obligations.
Accepting and Performing a Team Role.
Establishing and Striving to Meet Team Goals.
Building and Maintaining the Team.
References.
18. Teamwork.
Reference.
Appendices.
Appendix A. Need Statements for the TSPi Sample Exercises.
Purpose.
The Change Counter Functional Need Statement.
The Program Analyzer Functional Need Statement.
References.
Appendix B. Software Configuration Management.
The Software Configuration Management Problem.
Software Configuration Management Overview.
The SCM Plan.
The System Baseline.
Automating the SCM Process.
The Software Configuration Management Process.
Appendix C. Software Inspections.
What Are Inspections?
What Makes Inspections Effective?
Inspection Methods.
Inspection Data.
The Inspection Report: Form INS.
Estimating Remaining Defects.
The Importance of High Personal Yields.
Scheduling Inspections.
The TSPi Inspection Script.
References.
Appendix D. The TSPi Scripts.
Appendix E. Role Scripts.
Appendix F. TSPi Forms and Instructions.
Appendix G. The TSPi Standards and Specifications.
Index. 020147719XT04062001
Preface.
I. INTRODUCTION.
1. TSPi Overview.
What Is TSPi?
TSPi Principles.
The TSPi Design.
TSPi Structure and Flow.
The TSPi Process.
The Textbook Structure and Flow.
2. The Logic of the Team Software Process.
Why Projects Fail.
Common Team Problems.
What Is a Team?
Building Effective Teams.
How Teams Develop.
How TSPi Builds Teams.
References.
II. THE TSPI PROCESS.
3. Launching a Team Project.
Why Conduct a Team Launch?
Team Goals.
Team-Member Goals.
The Role Goals.
The TSPi Launch Scripts.
4. The Development Strategy.
Planning First.
What Is a Strategy?
The Conceptual Design.
Risk Management.
A Reuse Strategy.
The Strategy Scripts.
5. The Development Plan.
The Need for Planning.
The TSPi Planning Process.
The TSPi Support Tool.
The Development Plan Scripts.
Tracking the Work.
The Quality Plan.
Reference.
6. Defining the Requirements.
What Are Requirements?
Why We Need Requirements.
Requirements Changes.
The Software Requirements Specification.
The TSPi Requirements Scripts.
References.
7. Designing with Teams.
Design Principles.
Designing in Teams.
Design Standards.
Designing for Reuse.
Designing for Usability.
Designing for Testability.
Design Reviews and Inspections.
The TSPi Design Scripts.
References.
8. Product Implementation.
Design Completion Criteria.
Implementation Standards.
The Implementation Strategy.
Reviews and Inspections.
The IMP Scripts.
Reference.
9. Integration and System Testing.
Testing Principles.
The TSPi Testing Strategy.
The Build and Integration Strategy.
The System Test Strategy.
Test Planning.
Tracking and Measuring Testing.
Documentation.
The TSPi TEST Scripts.
References.
10. The Postmortem.
Why We Need a Postmortem.
What a Postmortem Can Do for You.
The Process Improvement Proposal.
The TSPi Postmortem Scripts.
Reference.
III. THE TEAM ROLES.
11. The Team Leader Role.
The Team Leader's Goals.
Helpful Team Leader Skills and Abilities.
The Team Leader's Principal Activities.
The Team Leader's Project Activities.
12. The Development Manager Role.
The Development Manager's Goals.
Helpful Development Manager Skills and Abilities.
The Development Manager's Principal Activities.
The Development Manager's Project Activities.
13. The Planning Manager Role.
The Planning Manager's Goals.
Helpful Planning Manager Skills and Abilities.
The Planning Manager's Principal Activities.
The Planning Manager's Project Activities.
14. The Quality/Process Manager Role.
The Quality/Process Manager's Goals.
Helpful Quality/Process Manager Skills and Abilities.
The Quality/Process Manager's Principal Activities.
The Quality/Process Manager's Project Activities.
References.
15. The Support Manager Role.
The Support Manager's Goals.
Helpful Support Manager Skills and Abilities.
The Support Manager's Principal Activities.
The Support Manager's Project Activities.
IV. USING THE TSPI.
16. Managing Yourself.
Being Responsible.
Striving for Defined Goals.
Living by Sound Principles.
Your Opinion of Yourself.
Your Opinion of Others.
Your Commitment to Excellence.
Reference.
17. Being on a Team.
The Jelled Team.
Teamwork Obligations.
Communication Among Team Members.
Making and Meeting Commitments.
Participation in the Team's Activities.
Team-building Obligations.
Accepting and Performing a Team Role.
Establishing and Striving to Meet Team Goals.
Building and Maintaining the Team.
References.
18. Teamwork.
Reference.
Appendices.
Appendix A. Need Statements for the TSPi Sample Exercises.
Purpose.
The Change Counter Functional Need Statement.
The Program Analyzer Functional Need Statement.
References.
Appendix B. Software Configuration Management.
The Software Configuration Management Problem.
Software Configuration Management Overview.
The SCM Plan.
The System Baseline.
Automating the SCM Process.
The Software Configuration Management Process.
Appendix C. Software Inspections.
What Are Inspections?
What Makes Inspections Effective?
Inspection Methods.
Inspection Data.
The Inspection Report: Form INS.
Estimating Remaining Defects.
The Importance of High Personal Yields.
Scheduling Inspections.
The TSPi Inspection Script.
References.
Appendix D. The TSPi Scripts.
Appendix E. Role Scripts.
Appendix F. TSPi Forms and Instructions.
Appendix G. The TSPi Standards and Specifications.
Index. 020147719XT04062001