From MCC and CMM: technology transfers bright and dim

ABSTRACT

This paper describes lessons learned during the author's five lives in technology transfer. The author's first life came in General Electric's Space Division where he performed research on software metrics and structured programming, and transferred technology to the pages of technical journals. His second life came at ITT's Programming Technology Center where he was responsible for transferring software measurement practices into common use across ITT's worldwide software operations. Some measurement initiatives survived, but most were short-lived. His third life came in MCC's Human Interface Laboratory and Software Technology Program. MCC's member companies were only occasionally able to transfer the advanced technology they challenged MCC to produce. His fourth life came in directing the Software Process Program at the Software Engineering Institute where he led the team that produced the Capability Maturity Model. Although the CMM's transfer was occasionally too rapid to control, the CMM suggested that you should transfer no technology before its time. The author's fifth and current life involves co-founding TeraQuest and helping companies to improve their software development capability. The paper includes twenty-five lessons in technology transfer and one model.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development; Software process

General Terms:
Design, Management, Measurement, Performance, Theory

Keywords:
CMM, MCC, SEI, capability maturity, change management, design process, model, software engineering institute, software measurement, software process improvement, technology adoption, technology transfer