Packaged software development teams: What makes them different?

Information Technology & People

Volumn 11, Issue 1, 1998, Pages 7-19

  Carmel, Erran ^a   Sawyer, Steve ^b  

^a AMERICAN UNIVERSITY   (United States)

^b SYRACUSE UNIVERSITY   (United States)

Author keywords

Corporate culture; Product differentiation; Software development; Teams

Indexed keywords

EID: 84986097866     PISSN: 09593845     EISSN: None     Source Type: Journal    
DOI: 10.1108/09593849810204503     Document Type: Article

References (51)

1. Adams, J. and Kirchof, N. (1982), Conflict Management for Project Managers, Project Management Institute, Drexel Hill, PA, pp. 1-13.
2. Bach, J. (1995), “Enough about process: what we need are heroes”, IEEE Software, March, Vol. 12 No. 2, pp. 96-8.
3. Boehm, B. (1987), “Improving software productivity, ” Computer, Vol. 19 No. 9, pp. 43-57.
4. Boehm, B. (1991), “Software risk management: principles and practices, ” IEEE Software, Vol. 8 No. 1, pp. 426-35.
5. Brooks, F. (1974), The Mythical Man-month, Addison-Wesley, Reading, MA.
6. Brooks, F. (1987), “No silver bullet: essence and accidents of software engineering, ” Computer, Vol. 19 No. 5, pp. 10-19.
7. Business Software Alliance (1997), World Trends, BSA, Washington, DC.
8. Carmel, E. (1995), “Cycle-time in packaged software firms, ” Journal of Product Innovation Management, Vol. 12 No. 2, pp. 110-23.
9. Carmel, E. (1997), “American hegemony in packaged software trade and the “culture of software””, The Information Society, Vol. 13 No. 1, pp. 125-42.
10. Carmel, E. and Becker, S. (1995), “A process model for packaged software development, ” IEEE Transactions on Engineering Management, Vol. 41 No. 5, pp. 50-61.
11. Carmel, E. and Bird, B. (1997), “Small is beautiful: a study of packaged software development teams, ” Journal of High Technology Management Research, Vol. 8 No. 1, pp. 129-48.
12. Constantine, L. (1995), Constantine on Peopleware, Yourdon Press, Englewood Cliffs, NJ.
13. Cringely, R. (1992), Accidental Empires, Addison-Wesley, Reading, MA.
14. Crowston, K. and Cammerer, E. (forthcoming), “Software development as collective mind, ” IBM Systems Journal.
15. Curtis, B., Krasner, H. and Iscoe, N. (1988), “A field study of the software design process for large systems, ” Communications of the ACM, Vol. 31 No. 11, pp. 1268-87.
16. Cusumano, M.A. (1991), Japan's Software Factories: A Challenge to US Management, Oxford University Press, New York, NY.
17. Cusumano, M. and Selby, R. (1997), “How Microsoft builds software, ” Communications of the ACM, Vol. 40 No. 6, pp. 53-61.
18. Cusumano, M. and Selby, R. (1995), Microsoft Secrets: How the World's Most Powerful Software-Company Creates Technology, Shapes Markets, and Manages People, Free Press/Simon & Schuster, New York, NY.
19. DeMarco, T. (1995), Why Does Software Cost So Much? and Other Puzzles of the Information Age, Dorsett House Publishing, New York, NY.
20. DeMarco, T. and Lister, T. (1987), “Peopleware: productive projects and teams”, Dorsett House, New York, NY.
21. Dubé, L. (1998), “The difficult journey from a sequential to a team-based development process: the story of Software Co.”, Information Technology & People, Vol. 11 No. 1, pp. 36-61.
22. Frye, C. (1997), “The SOFTWARE 500”, Software Magazine, Vol. 17 No. 8, pp. 41- 52.
23. Goodman, P., Ravlin, E. and Argote, L. (1986), Current Thinking about Groups: Setting the Stage for New Ideas. Designing Effective Work Groups, ” in Goodman, P. and Associates (Eds), Jossey-Bass, San Francisco, CA, pp. 227-42.
24. Grudin, J. (1991), “Interactive systems: bridging the gap between developers and users, ” IEEE Computer, Vol. 24 No. 5, pp. 59-69.
25. Guimaraes, T. (1985), “A study of application program development techniques, ” Communications of the ACM, Vol. 28 No. 5, pp. 494-99.
26. Guinan, P., Cooprider, J. and Sawyer, S. (1997), “The effective use of automated application development tools, ” IBM Systems Journal, Vol. 36 No. 1, pp. 124-39.
27. Harpers (1997), The Harpers Index, Vol. 295 No. 1770, pp. 17, 92.
28. Heckman, R. and Sawyer, S. (1996), “The information resource acquisition process”, in Carey, J. (Ed.), Proceedings of the 1996 AIS Americas Conference, ACM Press, New York, NY, pp. 207-09.
29. Humphrey, W. (1988), Managing the Software Process, Addison-Wesley, Reading, MA.
30. Keil, M. and Carmel, E. (1995), “Customer-developer links in software development, ” Communications of the ACM, Vol. 38 No. 5, pp. 33-44.
31. Kjaer, A. and Madsen, K. (1997), “Customer-vendor co-operation, ” Information Technology & People, Vol. 10 No. 3, pp. 205-23.
32. Kling, R. and Iacono, S. (1984), “The control of information systems developments after implementation, ” Communications of the ACM, Vol. 27 No. 12, pp. 1218-26.
33. Kozar, K. (1989), “Adopting systems development methods: an exploratory study, ” Journal of Management Information Systems, Vol. 5 No. 4, pp. 73-86.
34. Krishnan, M. (1998), “The role of team-factors in packaged software quality, ” Information Technology & People, Vol. 11 No. 1, pp. 20-35.
35. Larson, E. and Gobeli, D. (1988), “Organizing for product development projects, ” Journal of Product Innovation Management, Vol. 5, pp. 180-90.
36. Leebaert, D. (1995), “News from the frontiers, ” in Leebaert, D. (Ed.), The Future of Software, MIT Press, Cambridge, MA, pp. 1-28.
37. Levy, L. (1987), Taming the Tiger: Software Engineering and Software Economics, Springer-Verlag New York, NY.
38. McConnell, S. (1993), Code Complete, Microsoft Press, Redmond, WA.
39. McGrath, J. (1990), “Time matters in groups, ” in Galeghar, J., Kraut, R. and Egido, C. (Eds), Intellectual Teamwork, Social and Technological Foundations of Cooperative Work, Lawrence Erlbaum Associates, Hillsdale, NJ.
40. McGuire, S. (1994), Debugging the Development Process: Practical Strategies for Staying Focussed, Hitting Ship Dates, and Building Solid Teams, Microsoft Press, Redmond, WA.
41. Maglitta, J. (1997), “Super programmers, ” Computerworld, pp. 95-6.
42. Markus, M. (1983), “Power, politics, and MIS implementation, ” Communications of the ACM, Vol. 26 No. 6, pp. 430-44.
43. Paulk, M. (1995), “The evolution of the SEI's capability maturity model for software, ” Software Process, Vol. 1 No. 1, pp. 3-16.
44. Sawyer, S., Farber, J. and Spillers, R. (1997), “Supporting the social processes of software development teams, ” Information Technology & People, Vol. 10 No. 1, pp. 46-62.
45. Schein, E. (1992), Organizational Culture and Leadership, 2nd ed., Jossey-Bass, San Francisco, CA.
46. Walz, D., Elam, J. and Curtis, B. (1993), “Inside a software design team: knowledge acquisition, sharing, and integration, ” Communications of the ACM, Vol. 36 No. 10, pp. 63-77.
47. Weinberg, G. (1971), The Psychology of Computer Programming, Van-Nostrand Rheinhold, New York, NY.
48. Yourdon, E. (1993), Decline and Fall of the American Programmer, Prentice-Hall, Upper Saddle River, NJ.
49. Yourdon, E. (1996), Rise and Resurrection of the American Programmer, Prentice-Hall, Upper Saddle River, New York, NY.
50. Zachary, G. (1994), Showstopper: The Breakneck Race to Create Windows-NT and the Next Generation at Microsoft, The Free Press, New York, NY.
51. Zachary, G. (1998), “Armed truce: software in the age of teams, ” Information Technology & People, Vol. 11 No. 1, pp. 62-5.