Discovering high-impact success factors in capstone software projects

ABSTRACT

Capstone software projects in the undergraduate Computer Science curriculum provide valuable learning experiences for the students if the project is successful. Naturally, the team composition and teamwork affect the project results.

The aim of this paper is to find a connection between successful projects and team properties. Early recognition would be useful when the teacher or team instructor tries to help the teams to overcome possible obstacles caused by personal or team weaknesses. We gathered a vast amount of data on 40 students during selected capstone projects with questionnaires, interviews and expert observation over five semesters. The paper shows our measurement technique and its ability to reflect success in the capstone projects.

Close examination of the data revealed that certain team properties and operations were more significant in relation to expert evaluation than other. These factors are called high-impact factors for successful projects. Most significant were pre-learned skills in Computer Science curriculum, communication, coordination, and teamwork. Some success signs were evident from the beginning of the projects, including attitudes and personal needs.

REFERENCES

• 1: L. Adams, M. Daniels, A. Goold, O. Hazzan, K. Lynch, and I. Newman. Challenges in teaching capstone courses. SIGCSE Bull., 35(3):219--220, 2003.
• 2: D. E. Avison, F. Lau, M. D. Myers, and P. A. Nielsen. Action research. Communication of the ACM, 42(1):94--97, 1999.
• 3: M. R. Belbin. Team Roles at Work. Butterworth-Heinemann, Oxford, 1993.
• 4: Situational Leadership®II - The Article. The Ken Blanchard Companies, 2001.
• 5: K. Blanchard, D. Carew, and E. Parisi-Carew. The One Minute Manager Builds High Performing Teams. HarperCollingsPublishers, London, UK, 2004.
• 6: B. Boehm. Software engineering economics. Prentice-Hall, NJ, 1981.
• 7: B. Boehm. Software risk management: Principles and practices. IEEE Software, 8(1):32--41, 1991.
• 8: T. Clear, M. Goldweber, F. H. Young, P. M. Leidig, and K. Scott. Resources for instructors of capstone courses in computing. In ITiCSE-WGR '01: Working group reports from ITiCSE on Innovation and technology in computer science education, pages 93--113, New York, NY, USA, 2001. ACM.
• 9: B. Curtis, H. Krasner, and N. Iscoe. A field study of the software design process for large systems. Communication of the ACM, 31(11):1268--1287, 1988.
• 10: T. Ernest-Jones. I.T. at the speed of business - A survey and whitepaper. Hewlett-Packard Development Company and the Economist Intelligence Unit, 2007.
• 11: R. Felder and R. Brent. Effective strategies for cooperative learning. Journal of Cooperation & Collaboration in College Teaching, 10(2):69--75, 2001.
• 12: W. P. P. Filho. Requirements for an educational software development process. In ITiCSE '01: Proceedings of the 6th annual conference on Innovation and technology in computer science education, pages 65--68, New York, NY, USA, 2001. ACM.
• 13: S. Fisher, W. Macrosson, and G. Sharp. Further evidence concerning the Belbin team role self-perception inventory. Personnel Review, 25(2):61--67, 1996.
• 14: G. C. Gannod, J. E. Burge, and M. T. Helmick. Using the inverted classroom to teach software engineering. In ICSE '08: Proceedings of the 30th international conference on Software engineering, pages 777--786, New York, NY, USA, 2008. ACM.
• 15: R. L. Glass. The Standish report: does it really describe a software crisis? Communication of the ACM, 49(8):15--16, 2006.
• 16: B. Haberman, E. Lev, and D. Langley. Action research as a tool for promoting teacher awareness of students' conceptual understanding. In ITiCSE '03: Proceedings of the 8th annual conference on Innovation and technology in computer science education, pages 144--148, New York, NY, USA, 2003. ACM.
• 17: D. Hartmann. Interview: Jim Johnson of the Standish Group. http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOS [June 25th, 2009]
• 18: O. Hazzan. Computer science students' conception of the relationship between reward (grade) and cooperation. In ITiCSE '03: Proceedings of the 8th annual conference on Innovation and technology in computer science education, pages 178--182, New York, NY, USA, 2003. ACM.
• 19: T. B. Hilburn, S. Mengel, D. J. Bagert, and D. Oexmann. Software engineering across computing curricula. In ITiCSE '98: Proceedings of the 6th annual conference on the teaching of computing and the 3rd annual conference on Integrating technology into computer science education, pages 117--121, New York, NY, USA, 1998. ACM.
• 20: J. M. Hogan and R. Thomas. Developing the software engineering team. In ACE '05: Proceedings of the 7th Australasian conference on Computing education, pages 203--210, Darlinghurst, Australia, Australia, 2005. Australian Computer Society, Inc.
• 21: W. Humprey. Introduction to the Team Software Process. Addison-Wesley, 2000.
• 22: M. Ikonen. Working Toward Success Factors in Software Development Projects. Number 2009-19 in Series of Publications C. Department of Computer Science, University of Helsinki, Helsinki, Finland, 2009.
• 23: T. Jones. Programming productivity. McGrawHill, NY, 1986.
• 24: J. Jurison. Software project management: the manager's view. Communications of the Association for Information Systems CAIS, 2(September), 1999.
• 25: P. Koopman, H. Choset, R. Gandhi, B. Krogh, D. Marculescu, P. Narasimhan, J. M. Paul, R. Rajkumar, D. Siewiorek, A. Smailagic, P. Steenkiste, D. E. Thomas, and C. Wang. Undergraduate embedded system education at Carnegie Mellon. ACM Trans. Embed. Comput. Syst., 4(3):500--528, 2005.
• 26: C. W. Liew. Teaching software development skills early in the curriculum through software engineering. SIGCSE Bull., 37(3):133--137, 2005.
• 27: P. K. Linos, S. Herman, and J. Lally. A service-learning program for computer science and software engineering. In ITiCSE '03: Proceedings of the 8th annual conference on Innovation and technology in computer science education, pages 30--34, New York, NY, USA, 2003. ACM.
• 28: W. C. Oakes, E. J. Coyle, and L. H. Jamieson. EPICS: A model of service-learning in an engineering curriculum. In Proceedings of the ASEE Annual Conference, Saint Louis, MO, June 2000.
• 29: D. Partington and H. Harris. Team role balance and team performance: an empirical study. Journal of Management Development, 18(8):694--705, 1999.
• 30: D. Phan, D. Vogel, and J. Nunamaker. The search for perfect project management. Computerworld, 22:95--100, 1998.
• 31: M. Poppendieck and T. Poppendieck. Lean software development: an agile toolkit. Addison Wesley, Boston, MA, 2003.
• 32: S. P. Robbins. Essentials of organizational behavior. San Diego State University, Prentice Hall, 2002.
• 33: R. H. Rutherfoord. Using personality inventories to form teams for class projects: a case study. In SIGITE '06: Proceedings of the 7th conference on Information technology education, pages 9--14, New York, NY, USA, 2006. ACM.
• 34: K. Simola and M. Ikonen. Improving the quality of software engineering education: Benefits and disadvantages of working processes. In Proceedings of the 12th International Conference on Engineering Education ICEE 2008, Pécs - Budapest, Hungary, 2008. iNEER.
• 36: The Standish Group Report - CHAOS. The Standish Group International, Inc., 1995.
• 37: Chaos - A recipe for success. The Standish Group International, Inc., 1999.
• 38: Extreme chaos. The Standish Group International, Inc., 2001.
• 39: A. Thadani. Factors affecting programmer productivity during application development. IBM Systems Journal, 23(1):19--35, 1984.
• 40: D. Zigarmi, C. Edeburn, and K. Blanchard. Getting to know the LBAII ® - Research, validity, and reliability of the Self and Other forms. Blanchard Training and Development, Inc., Escondido, CA, USA, 4th edition, 1997.
• 41: R. Zmud. Management of large software development efforts. MIS Quarterly, 4:45--55, 1980.

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.3 COMPUTERS AND EDUCATION
      K.3.2 Computer and Information Science Education
          Subjects: Computer science education

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams; Productivity

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

General Terms:
Human Factors, Management

Keywords:
improvement, software project, success factor, team