Home > Articles > Software Development & Management

An Interview with Watts Humphrey, Part 22: The Process Conferences and the PSP Course

In this transcript of an oral history, Grady Booch interviews SEI Fellow Watts Humphrey. In Part 22, Humphrey explains why he stopped going to process conferences and why he decided to write a book and teach a course on PSP.

This interview was provided courtesy of the Computer History Museum.

See the entire interview.

Like this article? We recommend

The Process Conferences

Booch: In terms of influences, I remember there was a lot of discussion about what’s called process programming, and Lee Osterweil and crew were talking about that, and Barry Boehm was in the midst of it as well. Do you have any recollection of that being an influence, or you influencing what was going on there?

Humphrey: I participated in those workshops -- the software process workshops. They invited me to come, and I presented the maturity model at one of them, and everybody got all excited about it, and so I’d do a big talk on that. I used to go to ICSE (International Conference on Software Engineering) meetings, and I discovered surprisingly quickly that I was really off in left field. No one was where I was, and I kept describing what I was doing and why, and everybody was very interested in what Watts had to say, but nobody ever picked up on it. And I remember we had one of the software process workshops in Yokohama in Japan. Isn’t that that the north island?

Booch: Yes.

Humphrey: I think it is, yeah. Went out there, and a bunch of the guys were there. Of course, I’m the old guy. I was the old guy in all of this stuff, and the Japanese were probably closer than anybody to where I was, and they were pretty much reflecting what I was saying. They’re much more people-oriented. I was quite surprised.

By the way, I didn’t say I had put together a steering committee when I was running software process and quality at IBM, and I had Lee Osterweil on it. Lee Osterweil and Bob Balzer were both on the committee. I had a bunch of academics that were coming and reviewing what we were doing and giving us advice. I had a whole tool group and everything else in Poughkeepsie, and they were looking at the Ada design language stuff. So when I got working with them as well and we had a great time in this meeting near Denver and I’m trying to remember the name of it. Brecken--

Booch: Breckenridge, yeah.

Humphrey: Yeah, we were meeting in Breckenridge, and that’s where Lee Osterweil came out with his processes are programs, and I came up with this a _____eahhe name of it.  Brechbout next step.ing in is designing and programming has really basically repalced y needed essen CMM maturity model. Harlan Mills was involved then. I didn’t talk about my interactions with Harlan at IBM, but I did have some interactions with him there, and so Harlan was all excited about it. I remember at the ICSE meeting where Lee Osterweil and I both presented our talks, Harlan got up and made some comment about, “This is the best session we’ve ever had.” But he was a wonderful guy. I loved him. I used to meet with him. I’d go over to the east coast of Florida occasionally and meet with him. I disagreed with his Cleanroom stuff, though. Not because of what he did, but I disagreed with it because it didn’t measure. He didn’t gather data and measure stuff, and he and I were not together on the quality principles of where we were going.

But in any event, yes, I had met with these groups, and we were not on the same wavelength at all, and the meetings, they’d go through all this discussion. They’d want to automate this stuff, and they were trying to get tools to do this and that and a language for this and it was tech-y. It wasn’t focusing on what people do and that bothered me, because the way I thought about it was if I’m running a programming organization how was this going to help? And I didn’t see that and I still don’t. I mean, I think they’re still going in that same loop. I don’t know at all. I think it stayed mostly academic but I really don’t know. I haven’t gone back and looked. That may be unfair.

But in any event, we’d submit papers every year and they were reviewing them. And so I’d submit a paper every year and I’d get invited and I’d go, and one year they sent out the reviews. I’d never gotten the reviews before, but one year they sent out the reviews. This is for the one at Washington, and the reviews all said, “Why do we want to hear this stuff?” They had no interest in it but I was still invited to go. Obviously, I was going only because I was Watts Humphrey, not because what I would say was of interest to anybody, and I decided this is not something I’m going to continue doing, so I stopped.

The PSP Course

However, one meeting I did go to was the one in Germany. There was one in Germany and there was also a meeting in-- where was it? -- in Berlin a previous week. Some kind of a process conference, and Peter Feiler and I gave a paper on process terminology we put together. And when I was sitting in this process conference, it was boring as the devil and I wasn’t interested. I had developed the PSP and couldn’t get anybody to try it, and I’d talked to some people. I think Mahdevi -- not sure if you know him but he was a professor at McGill. I was chatting to him about it and he said, “You ought to teach a course.” I said, “That’s not a bad idea.” And so he said, “Well, I teach a software engineering course. Well, why don’t you come teach at McGill?” I said, “That’s a thought.” So I began to think about how I’d teach a course and concluded that to do that I needed some kind of a text.

So in the conference while all these people were talking, I was organizing my textbook, and this was early in the year, like, February. And so going to the conference, I had outlined my textbook, and I spent the weekend in Berlin because I had to go to this other conference elsewhere. And I had a wonderful time there going to look at the torn-down Berlin wall, and I went to a concert every night, and had a great weekend. Unfortunately, my wife wasn’t with me, so I was all alone, but it was a great weekend.

But I had this book to design, and I went to sit through the software process workshop the next week. I realized that I had no further interest in it. I was getting nothing out of these conferences in terms of what I was trying to do. So I didn’t quit in any way, but I had decided not to continue going, so I just stopped going to the process workshops or ICSEs. None of it seemed to have any effect. I’ll get back to ICSE in a minute, but I wrote the textbook. I got started in February. I had used PSP to make a plan for my textbook and I got a hold of my publisher who published Managing the Software Process, and he was very interested in it. I put together a schedule. My book would take me till January to get a manuscript out, and then I expected to submit it the following year.

Then I was deciding what to do to teach it, and at the same time one of the guys that I had known at the SEI who was there as a CMU student in our masters of software engineering program was Howard -- Howie Dow -- and he had actually spent some time with me and was very interested in what I was doing on the PSP. When he heard I was writing a book on it and was putting together a course, he got a hold of me and wanted to teach the course at the University of Massachusetts. He worked for DEC, and he wanted to use it at DEC and teach it there, and he wanted to start in September. My plan said the book wouldn’t be done until January, but I had been using a PSP on writing, and my PSP data showed me I would be through with the first draft of the manuscript in September. So I gulped and I told Howie that I’ll get you the manuscript in September for your course.

Booch: It’s known as eating your own dog food.

Humphrey: Exactly, exactly. So I basically said, “This is why -- you might as well prove it,” so I did. And it turned out to be a bit of a push at the end because I ended up having to reorganize the book a couple of times. I took chapter one and then made it chapter thirteen, and I decided I needed a whole new appendix because I was using a lot of statistics. But I didn’t want to write a statistics textbook. I had found statistics textbooks almost incomprehensible, so I put together an appendix A in my A Discipline for Software Engineering book and appendix A was, sort of, a you-drive-it statistics, how do you do this stuff. And the programming problems I put in the textbook 10 programming problems, eight of which were all just simple statistics, simple correlations and linear regression, multiple regression. I had chi-squared tests and approximations, a bunch of things.

So it was a lot of interesting stuff, but I had to explain it to people so the people who knew nothing about statistics could read it and that’s what appendix A in my book was. I learned a lot by writing it. Writing about statistics was fascinating. So in any event it ended being an 800 page book, and I got the manuscript together from February to September. Now, that’s pretty speedy, and so Howie Dow taught the course. I had decided not to teach at McGill but to teach at CMU, and so we put a PSP course together at CMU.

And so I started that in January and used my manuscript and taught the PSP course at CMU. I decided to wait on submitting the manuscript. I was going to rewrite it after I taught the course because the only data I had before I taught the course was personal data. So I got Howie Dow’s data. The first class he did worked well. He had lots of constructive comments. It was very helpful having somebody else do it. There were some guys at Embry-Riddle University who wanted to teach it, so they taught a course. I don’t think in parallel with mine. They taught in the fall.  And others -- some guy at Howard University wanted to teach a course and he got in there and it was a disaster. He didn’t really get it.

I guess about three or four courses were taught and I taught some courses. Some companies got quite interested and they worked extremely well. The course results were astounding. My first class at CMU I think four people in that course all changed their careers in the course to say, “This is what I want to work on.” And three of them are working directly with us still on the TSP and PSP. They just got so excited about it that they said, “It works. This is what process is.” A number of people have been working on process work on the CMM even. Once they took the PSP course, they concluded that, “Hey, now I understand it. This is really what it is.” And that’s what it did. You really learn what a process is and why it’s helpful when you actually use it personally to do your own work.

Booch: So thinking of other people around this time, did you have any connections with people like Walker Royce’s dad, Winn Royce, who wrote some of the classic papers in waterfall life-cycle or for that matter, the work that Filipe – I forget his last name – was doing starting around that time for what became the rational process? Did you have connections with any of those folks?

Humphrey: Yeah, I knew Winn Royce. I’d been involved in a number of things with the SEI and of course, Larry brought him in periodically. A marvelous guy, a wonderful guy. So I got to know him quite well. Of course, I got to know Barry Boehm very well and worked with him and yeah, there’s a whole list of people. I’ve been involved with just about everybody in the community one way or another. I never got to know the Rational folks, but I did get to know an awful lot of people when I got involved with him, so I’ve got an enormous array of people that I run into that I sort of know.

And there are a lot of people that I know that I don’t know, if you know what I mean. They say, “Well, I met you here when…“ I’ve given an enormous number of talks over the years and, of course, I’ve written so much stuff, but I’ve gotten to know an awful lot of people and it’s been a very rewarding period.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020