skip to main content
10.1145/3564721.3564730acmotherconferencesArticle/Chapter ViewAbstractPublication Pageskoli-callingConference Proceedingsconference-collections
research-article

Refining a Risk Framework for Student Group Projects

Published:17 November 2022Publication History

ABSTRACT

Tertiary educators in software related topics experience issues during project-based group assessments. Our long term goal is to help educators manage the challenges that inevitably occur by providing a risk planning mechanism for students that suits the needs of the course. In this paper, we describe the first iteration of an action research study to trial a risk framework for academic group projects. Our aims were to understand how educators appropriate the framework to suit their course, gain insight into students’ understanding of risk concepts and refine the framework. A questionnaire based on the framework was distributed to students in three 12-week computer science (CS) courses. We found that most students reported few issues. Participating courses used the framework in different ways. Students lacked a holistic understanding of risk management concepts, implying the need to formally introduce these. Our study progresses the understanding of the issues experienced in academic group projects and contributes a revised framework to help manage these. In future iterations, we will investigate links between issues and project characteristics and establish a repository of mitigation strategies that is project-specific.

References

  1. Tero Ahtee and Timo Poranen. 2009. Risks in Students’ Software Projects. In Proceedings of the 22nd Conference on Software Engineering Education and Training (CSEET’09). ACM, NY, USA, 154–157. https://doi.org/10.1109/CSEET.2009.31Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Craig Anslow and Frank Maurer. 2015. An Experience Report at Teaching a Group Based Agile Software Development Project Course. In Proceedings of the 46th ACM Technical Symposium on Computer Science Education (Kansas City, MO, USA) (SIGCSE ’15). Association for Computing Machinery, New York, NY, USA, 500–505. https://doi.org/10.1145/2676723.2677284Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. David E. Avison, Francis Lau, Michael D. Myers, and Peter Axel Nielsen. 1999. Action Research. Commun. ACM 42, 1 (jan 1999), 94–97. https://doi.org/10.1145/291469.291479Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Sarah Beecham, Tony Clear, Ramesh Lal, and John Noll. 2021. Do scaling agile frameworks address global software development risks? An empirical study. Journal of Systems and Software 171 (2021), 110823. https://doi.org/10.1016/j.jss.2020.110823Google ScholarGoogle ScholarCross RefCross Ref
  5. Difference Between). 2021. Difference Between PMI and Prince2. Retrieved June 28, 2021 from http://www.differencebetween.net/business/difference-between-pmi-and-prince2/Google ScholarGoogle Scholar
  6. Barry Boehm and Daniel Port. 2001. Educating Software Engineering Students to Manage Risk. In Proceedings of the 23rd International Conference on Software Engineering (ICSE ’01). Association for Computing Machinery, New York, NY, USA, 591–600. https://doi.org/10.1109/ICSE.2001.919133Google ScholarGoogle ScholarCross RefCross Ref
  7. Barry W. Boehm. 1991. Software Risk Management: Principles and Practices. IEEE Software 8, 1 (1991), 32–41.Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. Virginia Braun and Victoria Clarke. 2006. Using thematic analysis in psychology. Qualitative Research in Psychology 3, 2 (2006), 77–101. https://doi.org/10.1191/1478088706qp063oa arXiv:https://www.tandfonline.com/doi/pdf/10.1191/1478088706qp063oaGoogle ScholarGoogle ScholarCross RefCross Ref
  9. Business Research Methodology. n.d.. Action research. Retrieved July 25, 2022 from https://research-methodology.net/research-methods/action-research/Google ScholarGoogle Scholar
  10. Jennifer Campbell and Anya Tafliovich. 2015. An Experience Report: Using Mobile Development To Teach Software Design. In Proceedings of the 46th ACM Technical Symposium on Computer Science Education (Kansas City, USA) (SIGCSE ’15). ACM, NY, USA, 506–511. https://doi.org/10.1145/2676723.2677307Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Daniela Damian and Arber Borici. 2012. Teamwork, Coordination and Customer Relationship Management Skills: As Important as Technical Skills in Preparing our SE Graduates. In 2012 First International Workshop on Software Engineering Education Based on Real-World Experiences (EduRex). 37–40. https://doi.org/10.1109/EduRex.2012.6225704Google ScholarGoogle ScholarCross RefCross Ref
  12. Emeral Publishing. 2022. How to carry out action research. Retrieved July 25th, 2022 from https://www.emeraldgrouppublishing.com/how-to/research-methods/carry-out-action-researchGoogle ScholarGoogle Scholar
  13. Chase Felker, Radka Slamova, and Janet Davis. 2012. Integrating UX with Scrum in an Undergraduate Software Development Project. In Proceedings of the 43rd ACM Technical Symposium on Computer Science Education (Raleigh, North Carolina, USA) (SIGCSE ’12). Association for Computing Machinery, New York, NY, USA, 301–306. https://doi.org/10.1145/2157136.2157226Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. Maria Lydia Fioravanti, Bruno Sena, Leo Natan Paschoal, Laísa de Silva, Ana P. Allian, Elisa Y. Nakagawa, Simone R.S. Souza, Seiji Isotani, and Ellen F. Barbosa. 2018. Integrating Project Based Learning and Project Management for Software Engineering Teaching: An Experience Report. In Proc. 49th ACM Technical Symposium on Computer Science Education (Baltimore, MD, USA) (SIGCSE ’18). ACM, 806–811. https://doi.org/10.1145/3159450.3159599Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. David P. Gluch. 1994. A Construct for Describing Software Development Risks. Technical Report CMU/SEI-94-TR-14. Software Engineering Institute, Carnegie Mellon University.Google ScholarGoogle Scholar
  16. International Standards Organisation. 2008. ISO/IEC 12207: Information Technology - Software Lifecycle Processes). ISO/IEC.Google ScholarGoogle Scholar
  17. International Standards Organisation. 2021. ISO/IEC/IEEE 16085:2021: Systems and Software Engineering - Lifecycle Processes - Risk Management). https://doi.org/10.1109/IEEESTD.2021.9325968Google ScholarGoogle ScholarCross RefCross Ref
  18. An Ju, Adnan Hemani, Yannis Dimitriadis, and Armando Fox. 2020. What Agile Processes Should We Use in Software Engineering Course Projects?. In Proceedings of the 51st ACM Technical Symposium on Computer Science Education(SIGCSE ’20). ACM, NY, USA, 643–649. https://doi.org/10.1145/3328778.3366864Google ScholarGoogle ScholarDigital LibraryDigital Library
  19. Diana Kirk, Andrew Luxton-Reilly, and Ewan Tempero. 2022. Risks in Student Projects. In Australasian Computing Education Conference(Virtual Event, Australia) (ACE ’22). New York, NY, USA, 143–152. https://doi.org/10.1145/3511861.3511877Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. Barbara Kitchenham, Tore Dybå, and Magne Jorgensen. 2004. Evidence-Based Software Engineering. In Proceedings of the 26th International conference on Software engineering (ICSE’04) (Washington, DC, USA). ACM, New York, NY, USA, 273–281.Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. Supannika Koolmanojwong and Barry Boehm. 2013. A Look at Software Engineering Risks in a Team Project Course. In Proceedings of the 26th International Conference on Software Engineering Education and Training (CSEET’13). IEEE, 21–30. https://doi.org/10.1109/CSEET.2013.6595233Google ScholarGoogle ScholarCross RefCross Ref
  22. Timo O.A. Lehtinen, Mika V. Mäntillaä, Jari Vanhanen, Juha Itkonen, and Casper Lassenius. 2014. Perceived causes of software project failures - An analysis of their relationships. Information and Software Technology 56, 6 (2014), 623–643.Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. Sherlock A. Licorish, Matthias Galster, Georgia M. Kapitsaki, and Amjed Tahir. 2022. Understanding Students’ Software Development Projects: Effort, Performance, Satisfaction, Skills and Their Relation to the Adequacy of Outcomes Developed. J. Syst. Softw. 186, C (2022). https://doi.org/10.1016/j.jss.2021.111156Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. Axelos Limited. 2021. Prince2 - Project Management. Retrieved June 28, 2021 from https://www.axelos.com/best-practice-solutions/prince2Google ScholarGoogle Scholar
  25. Samuel Mann and Lesley Smith. 2007. Software Engineering Class Eating Its Own Tail. In Proceedings of the Ninth Australasian Conference on Computing Education - Volume 66(ACE ’07). Australian Computer Society, Inc., 115–123.Google ScholarGoogle Scholar
  26. Ana M. Moreno, María-Isabel Sánchez-Segura, Fuensanta Medina-Domínguez, Lawrence Peters, and Jonathan Araujo. 2016. Enriching Traditional Software Engineering Curricula with Software Project Management Knowledge. In ICSE ’16: Proceedings of the 38th International Conference on Software Engineering Companion. ACM, NY, USA, 404–411. https://doi.org/10.1145/2889160.2889193Google ScholarGoogle ScholarDigital LibraryDigital Library
  27. Claudia Ott and Veronica Liesaputra. 2020. Industry-focused Projects in an Intense One-Year ICT Programme. In Proceedings of 22nd Australasian Computing Education Conference (ACE2020 (Melbourne, Victoria, AU). Australian Computer Society, Inc., AUS, 132–141. https://doi.org/10.1145/3373165.3373180Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. Janne Ropponen and Kalle Lyytinen. 2000. Components of Software Development Risk: How to Address Them? A Project Manager Survey. IEEE Transactions on Software Engineering 26, 2 (2000), 98–112.Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. Roy Schmidt, Kalle Lyytinen, Mark Keil, and Paul Cule. 2001. Identifying Software Project Risks: An International Delphi Study. Journal of Management Information Systems 17, 4 (2001), 5–36. http://www.jstor.org/stable/40398503Google ScholarGoogle ScholarDigital LibraryDigital Library
  30. Jean-Guy Schneider, Peter W. Eklund, Kevin Lee, Feifei Chen, Andrew Cain, and Mohamed Abdelrazek. 2020. Adopting Industry Agile Practices in Large-scale Capstone Education. In Proc. of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering Education and Training(ICSE-SEET ’20). ACM, NY, USA, 119–129. https://doi.org/10.1145/3377814.3381715Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. J.M. Verner, O.P. Brereton, B.A. Kitchenham, M. Turner, and M. Niazi. 2014. Risks and risk mitigation in global software development: A tertiary study. Information and Software Technology 56, 1 (2014), 54–78. https://doi.org/10.1016/j.infsof.2013.06.005Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. Brian R. von Kronsky and Jim Ivins. 2008. Assessing the Capability and Maturity of Capstone Software Engineering Projects. In Proceedings of the Tenth Conference on Australasian Computing Education - Volume 78(Wollongong, NSW, Australia) (ACE ’08). Australian Computer Society, Inc., AUS, 171–180.Google ScholarGoogle Scholar
  33. Linda Wallace and Mark Keil. 2004. Software Project Risks and their Effects on Outcomes. Commun. ACM 47, 4 (2004), 68–73. https://doi.org/10.1145/975817.975819Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Refining a Risk Framework for Student Group Projects

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Other conferences
      Koli Calling '22: Proceedings of the 22nd Koli Calling International Conference on Computing Education Research
      November 2022
      282 pages
      ISBN:9781450396165
      DOI:10.1145/3564721

      Copyright © 2022 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 17 November 2022

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • research-article
      • Research
      • Refereed limited

      Acceptance Rates

      Overall Acceptance Rate80of182submissions,44%

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader

    HTML Format

    View this article in HTML Format .

    View HTML Format