Skip to main content
SpringerLink
Log in

Why don't they practice what we preach?

  • Published:
Annals of Software Engineering

Abstract

One of the most intractable problems in software is getting engineers to consistently use effective methods. The Software Engineering Institute (SEI) has worked on this problem for a number of years and has developed effective methods for addressing it. This paper describes these methods and shows what they have accomplished with several hundred students and working engineers. After first describing the problem of changing engineers' practices, the paper discusses the logic engineers typically follow in deciding what methods to use. Next is a description of the Personal Software Process (PSP) and the Team Software Process (TSP). Finally, the implications of SEI's experiences with the PSP and TSP are described, with particular emphasis on software engineering and computer science education.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Ferguson, P., W.S. Humphrey, S. Khajenoori, S. Macke, and A. Matvya (1997), “Introducing the Personal Software Process: Three Industry Case Studies,” IEEE Computer 30, 5, 24–31.

    Google Scholar 

  • Hayes, W. (1997), “The Personal Software Process: An Empirical Study of the Impact of PSP on Individual Engineers,” Technical Report CMU/SEI-97-TR-001.

  • Hilburn, T.B. and J. Over (1997), “Lectures and Exercises,” In PSP Faculty Workshop, Software Engineering Institute and Embry-Riddle Aeronautical University, Daytona Beach, Florida, June 23–27.

  • Humphrey, W.S. (1989), Managing the Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Humphrey, W.S. (1995), A Discipline for Software Engineering, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Humphrey, W.S. (1996), “Using a Defined and Measured Personal Software Process,” IEEE Software, May.

  • Humphrey, W.S. (1997), Introduction to the Personal Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Humphrey, W.S. and J. Over (in press), Introduction to the Team Software Process, Addison-Wesley, Reading, MA.

  • Kaplan, C., R. Clark, and V. Tang (1994), Secrets of Software Quality, 40 Innovations from IBM, McGraw-Hill, Inc., New York. On pages 173–176, the authors discuss this issue and give an example of a large product where the correlation between development test and customer-reported defects was 0.964 with a significance of better than 0.001.

    Google Scholar 

  • Paulk, M.C. et al. (1995), The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, MA.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. The Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 15213, USA

    Watts S. Humphrey

Authors
  1. Watts S. Humphrey
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Humphrey, W.S. Why don't they practice what we preach?. Annals of Software Engineering 6, 201–222 (1998). https://doi.org/10.1023/A:1018997029222

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1018997029222

Keywords

Search

Navigation