|
In this transcript of an oral history provided by The Computer History Museum, Grady Booch interviews SEI Fellow Watts S. Humphrey. Humphrey is the author of several influential books on the software development process and software process improvement. Mr. Humphrey was a Fellow at the Software Engineering Institute at Carnegie Mellon, where he provided the vision for, and early leadership in the development of, the widely used standard for assessing an organization's software development capability, the Capability Maturity Model (CMM).
Humphrey's most recent book is Reflections on Management: How to Manage Your Software Projects, Your Teams, Your Boss, and Yourself.
We were saddened to hear of the recent passing of Watts Humphrey on October 28th, 2010. Many of us had the privilege of working with him on his books for Addison-Wesley. He will be missed.
The Interview
- Part 1: Beginnings
- Part 2: the Navy, College, and Wrestling
- Part 3: Sylvania and Northeastern University
- Part 4: Building a Computer Group and Starting at IBM
- Part 5: Early Projects at IBM
- Part 6: The IBM 360
- Part 7: The Director of Programming Role at IBM
- Part 8: The Model 91 Announcement
- Part 9: Family History, Phase Plans, and Labs Around the World
- Part 10: The Fortune Interview, IBM Lawsuits, and Virtual Memory
- Part 11: Skiing with Tom Watson and Why RCA Failed
- Part 12: IBM Corporate Policy, Contracts, and Lawsuits
- Part 13: The IBM PC and International Business
- Part 14: Jay Forrester, Program Pricing, and the FS System
- Part 15: The SHARE Meeting, the MVS Review, Release 15/16, and the Compatibility Letter
- Part 16: Semiconductor and Software Quality and the Revolution of CI-105
- Part 17: Measuring and Improving Software Quality
- Part 18: The Move to SEI
- Part 19: Starting at SEI
- Part 20: The SEI 5-Level Maturity Model
- Part 21: The Personal Software Process
- Part 22: The Process Conferences and the PSP Course
- Part 23: IBM Tool Development, the Academic Advisory Board, and the Speak Out Article
- Part 24: Mary Shaw Meetings and the Ashton-Tate Story
- Part 25: SEI Strategy and the Trouble with Trivial Errors
- Part 26: Catastrophic Software Failures and the Limits of Testing
- Part 27: Formal Methods, the Failure of PSP, and Tragedy of Beautiful Software
- Part 28: Early TSP Trials and the Teradyne Team Launch
- Part 29: The Task-Time Measure and Presenting the Plan to Teradyne Management
- Part 30: The TSP Team and Six Months to Live
- Part 31: Expanding TSP Use and Lack of Academic Interest
- Part 32: International TSP Use and the Trouble with Knowledge Work
- Part 33: The Boeing B2 System and the βLast Liar Problem"
- Part 34: Women in Software and the Change Problem
- Part 35: The National Medal of Technology
- Part 36: Agile Methods, Open Source, and Cloud Computing
- Part 37: Language Trends, the Future, and Advice to Young People
|