Creating high-performing software development teams

R and D Management

Volumn 35, Issue 4, 2005, Pages 375-393

  Pattit, Jason M ^a   Wilemon, David ^a  

^a SYRACUSE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 25144511018     PISSN: 00336807     EISSN: None     Source Type: Journal    
DOI: 10.1111/j.1467-9310.2005.00396.x     Document Type: Article

References (51)

1. Allen, T.J. (1977) Managing the Flow of Technology: Technology Transfer and the Dissemination of Technological Information within the R&D Organizations. Cambridge, MA: MIT Press.
2. Argyris, C. and Schön, D.A. (1978) Organizational Learning: A Theory of Action Perspective. Reading, MA: Addison-Wesley.
3. Argyris, C. (1990) Overcoming Organizational Defenses: Facilitating Organizational Learning. Upper Saddle River, NJ: Prentice Hall.
4. Banker, R.D., Davis, G.B. and Slaughter, S.A. (1998) Software development practices, software complexity, and software maintenance performance: a field study. Management Science, 44, 4, 433-450.
5. Boehm, B.W. (1988) A spiral model of software development and enhancement. Computer, 21, 5, 61-72.
6. Boehm, B.W. (1996) Anchoring the software process. IEEE Software, 13, 4, 73-82.
7. Boudette, N.E. (1999) Europe's SAP scrambles to stem big glitches. Wall Street Journal, November 4, A25.
8. Bourgeon, L. (2002) Temporal context of organizational learning in new product development projects. Creativity and Innovation Management, 11, 3, 175-183.
9. Briner, W., Geddes, M. and Hastings, C. (1990) Project Leadership. New York: Van Nostrand Reinhold.
10. Brooks, F.B. (1975) The Mythical Man-Month: Essays on Software Engineering. London: Addison-Wesley.
11. Burns, T. and Stalker, G.M. (1961) The Management of Innovation. London: Tavistock.
12. Caldwell, B. (1998) Andersen consulting sued over 'flawed' SAP R/3 job. InformationWeek, July 3.
13. Cantor, M. (2002) Software Leadership: A Guide to Successful Software Development. Boston: Addison-Wesley.
14. Carmel, E. and Bird, B.J. (1997) Small is beautiful: a study of packaged software development teams. The Journal of High Technology Management Research, 8, 1, 129-148.
15. Crawford, M. and DiBenedetto, A. (2003) New Products Management. Boston: McGraw-Hill Irwin.
16. Curtis, W. (1989) Three problems overcome with behavioral models of the software development process. Paper presented at the 11th International Conference on Software Engineering. Pittsburgh, PA.
17. DeMarco, T. and Lister, T. (1987) Peopleware: Productive Projects and Teams. New York: Dorset House.
18. Diederich, T. (1999) Bankrupt firm blames SAP for failure. ComputerWorld, August 28.
19. Gobeli, D.H., Koenig, H.F. and Bechinger, I. (1998) Managing conflict in software development teams: a multilevel analysis. Journal of Product Innovation Management, 15, 5, 423-435.
20. Greiner, L.E. (1972) Evolution and revolution as organizations grow. Harvard Business Review, 50, 4, 37-46.
21. Griffin, A. (1997) PDMA research on new product development practices: updating trends and bench-marking best practices. Journal of Product Innovation Management, 14, 6, 429-458.
22. Hage, J., Aiken, M. and Marrett, C.B. (1971) Organization structure and communications. American Sociological Review, 36, 5, 860-871.
23. Hoch, D.J., Roeding, C.R., Purkert, G. and Lindner, S.K. (2000) Secrets of Software Success: Manage ment Insights from 100 Software Firms around the World. Boston: Harvard Business School Press.
24. Hooijberg, R. and Petrock, F. (1993) On cultural change: using the competing values framework to help leaders execute a transformational strategy. Human Resource Management, 32, 29-50.
25. Humphrey, W.S. (2000) Introduction to the Team Software Process. Reading, MA: Addison-Wesley.
26. Jackson, S.E. and Schuler, R.S. (2000) Managing Human Resources: A Partnership Perspective. Cincinnati, OH: South-Western College Publishing.
27. Jiang, J. and Klein, G. (2000) Software development risks to project effectiveness. Journal of Systems and Software, 52, 1, 3-10.
28. Karolak, D.W. (1998) Global Software Development. Los Alamitos, CA: IEEE Computer Society.
29. Knuchten, P. (1996) A rational development process. CrossTalk, 9, 11-16.
30. Leonard-Barton, D., Bower, K., Clark, K., Holloway, C. and Wheelwright, S. (1994) How to integrate work and deepen expertise. Harvard Business Review, 72, 5, 121-130.
31. MacDonald, E. (1999) Maker of Gore-Tex sues PeopleSoft and Deloitte. Wall Street Journal, November 2, B14.
32. Mann, C.C. (2002) Why software is so bad. Technology Review, 105, 6, 33-38.
33. McConnell, S. (1996) Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.
34. McConnell, S. (1998) Software Project Survival Guide. Redmond, WA: Microsoft Press.
35. Miller, D. (1986) Configurations of strategy and structure: towards a synthesis. Strategic Management Journal, 7, 3, 233-250.
36. Montoya, S. (1998) FoxMeyer files suit against SAP software company. AP Wire, August 27.
37. Nord, W.R. and Tucker, S. (1987) Implementing Routine and Radical Innovations. Lexington, MA: Lexington Books.
38. Norris, M., Rigby, P. and Payne, M. (1993) The Healthy Software Project: A Guide to Successful Development and Management. West Sussex, UK: John Wiley & Sons Ltd.
39. Pressman, R. (1996) Software process perceptions. IEEE Software, 13, 6, 16-19.
40. Purser, R.E., Pasmore, W.A. and Tenkasi, R.V. (1992) The influence of deliberations on learning in new product development teams. Journal of Engineering and Technology Management, 9, 1-28.
41. Quinn, R.E. (1988) Beyond Rational Management: Mastering the Paradoxes and Competing Demands of High Performance. San Francisco: Jossey-Bass.
42. Sawyer, S. and Guinan, P.J. (1998) Software development: processes and performance. IBM Systems Journal, 37, 4, 552-569.
43. Sheremata, W.A. (2000) Centrifugal and centripedal forces in radical new product development under time pressure. Academy of Management Review, 25, 2, 389-408.
44. Sheremata, W.A. (2002) Finding and solving problems in software new product development. Journal of Product Innovation Management, 19, 144-158.
45. Smart, C. and Vertinsky, I. (1977) Designs for crisis decision units. Administrative Science Quarterly, 22, 4, 640-657.
46. Thamhain, H.J. and Wilemon, D.L. (1986) Criteria for controlling projects according to plan. Project Management Journal, 17, 2, 75-81.
47. van Genuchten, M. (1991) Why is software late? An empirical study of reasons for delay in software development. IEEE Transactions on Software Engineering, 16, 6, 582-590.
48. Wheelwright, S.C. and Clark, K.B. (1992) Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quantity. New York: The Free Press.
49. Whitaker, K. (1994) Managing Software Maniacs: Finding, Managing and Rewarding Winning Development Teams. New York: Wiley.
50. Whitehead, R. (2001) Leading a Software Development Team: A Developer's Guide to Successfully Leading People & Projects. Harlow, UK: Addison-Wesley.
51. Whitten, N. (1995) Managing Software Development Projects. New York: John Wiley & Sons, Inc.