In an industry that is supposed to be driving the future, we see many recurring patterns of dysfunction and self-destructive behavior in the planning and execution of software development projects. Many have questioned typical practices of hiring, educating, and managing software-related professionals. Many of these problems seem to be rampant. Dilbert and many other parodies illustrate the recurring symptoms, but do they really identify the problem?

The response to undisciplined software development has been to search for a metaphor that helps the world envision a more disciplined approach to software that will produce reliable software at a predictable cost. It seems that "software engineering" is the metaphor that has stuck. Some argue that the plethora of the problems we face in our industry stem from the use of the "software engineering" metaphor. Others argue that the problems stem from the misapplication of this metaphor. Is it time for a new metaphor?