Packaged software development teams: what makes them different?

Discusses the characteristics of packaged software versus information systems (IS) development environments that capture the differences between the teams that develop software in these respective industries. The analysis spans four levels: the industry, the dynamics of software development, the cultural milieu, and the teams themselves. Finds that, relative to IS: the packaged software industry is characterized by intense time pressures, less attention to costs, and different measures of success; the packaged software development environment is characterized by being a “line” rather than “staff” unit, having a greater distance from the actual users/customers, a less mature development process; the packaged software cultural milieu is characterized as individualistic and entrepreneurial; the packaged software team is characterized as less likely to be matrix managed and being smaller, more co‐located, with a greater shared vision.

[1]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[2]  Tor Guimaraes.  A study of application program development techniques , 1985, CACM.

[3]  Barry W. Boehm,et al.  Improving Software Productivity , 1987, Computer.

[4]  Erran Carmel,et al.  Customer-developer links in software development , 1995, CACM.

[5]  Steve Sawyer,et al.  The Effective Use of Automated Application Development Tools , 1997, IBM Syst. J..

[6]  G. Pascal Zachary.  Armed truce: software in an age of teams , 1998, Inf. Technol. People.

[7]  Martin Wight,et al.  Power politics , 1978 .

[8]  Line Dubé,et al.  Teams in packaged software development: The Software Corp. experience , 1998, Inf. Technol. People.

[9]  Michael A. Cusumano,et al.  How Microsoft builds software , 1997, CACM.

[10]  E. Schein.  Organizational Culture and Leadership , 1991 .

[11]  Tom DeMarco,et al.  Peopleware: Productive Projects and Teams , 1987 .

[12]  Leon S. Levy.  Taming the Tiger: Software Engineering and Software Economics , 1986 .

[13]  Elizabeth C. Ravlin,et al.  Current Thinking About Groups: Setting the Stage for New Ideas , 1986 .

[14]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[15]  Steve Sawyer,et al.  Supporting the social processes of software development , 1997, Inf. Technol. People.

[16]  Mark C. Paulk,et al.  The Evolation of the SEI's Capacity Maturity Model for Software , 1995, Softw. Process. Improv. Pract..

[17]  Joseph E. McGrath,et al.  Time matters in groups , 1990 .

[18]  Richard W. Selby,et al.  Microsoft Secrets-How the World''s Most Powerful Software Company Creates Technology , 1995 .

[19]  Larry Constantine,et al.  Constantine on Peopleware , 1995 .

[20]  Erran Carmel,et al.  A process model for packaged software development , 1995 .

[21]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[22]  Erran Carmel,et al.  American Software Hegemony in Packaged Software and 'the Culture Software' , 1997, Inf. Soc..

[23]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

[24]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[25]  E. Larson,et al.  Organizing for product development projects , 1988 .

[26]  Gerald M. Weinberg,et al.  Psychology of computer programming , 1971 .

[27]  J ElamJoyce,et al.  Inside a software design team , 1993 .

[28]  G. Pascal Zachary,et al.  Show Stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft , 1994 .

[29]  J. Bach.  Enough About Process: What We Need are Heroes , 1995, IEEE Softw..

[30]  M. Lynne Markus,et al.  Power, politics, and MIS implementation , 1987, CACM.

[31]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[32]  Ruth Milkman,et al.  Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People , 1995 .

[33]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[34]  P. Goodman.  Designing effective work groups , 1999 .

[35]  Robert E. Kraut,et al.  Intellectual Teamwork: Social and Technological Foundations of Cooperative Work , 1990 .

[36]  Steve Maguire.  Debugging the development process : practical strategies for staying focused, hitting ship dates, and building solid teams , 1994 .

[37]  Peter Middleton,et al.  Japan's software factories: a challenge to US management , 1993, J. Inf. Technol..

[38]  Rob Kling,et al.  The control of information systems developments after implementation , 1984, CACM.

[39]  Michael A. Cusumano,et al.  Japan's Software Factories: A Challenge to U.S. Management, Michael A. Cusumano. 1991. Oxford University Press, New York, NY. 513 pages. ISBN: 0-19-506216-7 , 1991, The Journal of Asian Studies.

[40]  Kim Halskov,et al.  Customer-vendor co-operation , 1997, Inf. Technol. People.

[41]  Kenneth A. Kozar,et al.  Adopting Systems Development Methods: An Exploratory Study , 1989, J. Manag. Inf. Syst..

[42]  Tom DeMarco,et al.  Why Does Software Cost So Much?: And Other Puzzles of the Information Age , 1995 .

[43]  Edward Yourdon,et al.  Rise and Resurrection of the American Programmer , 1996 .

[44]  Jonathan Grudin.  Interactive systems: bridging the gaps between developers and users , 1995 .

[45]  Mayuram S. Krishnan,et al.  The role of team factors in software cost and quality: An empirical analysis , 1998, Inf. Technol. People.

[46]  E. Carmel.  Cycle time in packaged software firms , 1995 .

[47]  Barbara J. Bird,et al.  Small is beautiful: A study of packaged software development teams , 1997 .

[48]  Derek Leebaert.  News from the frontiers , 1995 .