Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

The Anatomy of a Successful Student Scrum Team: Motivation, Personalities, and Academic Adaptation

Nadia Damianova, Santiago Berrezueta-Guzman

TL;DR

This paper investigates how Scrum can be effectively taught and practiced in long-running, student-led projects under academic calendars and hybrid work constraints. It uses a year-long case study of an eight-person team developing a VR campus game, leveraging Notion for backlogs, Discord for communication, and GitHub for version control, augmented by a custom communication effectiveness index. The findings show that lightweight, tool-mediated coordination, one-week sprints with pause weeks around exams, and explicit attention to motivation and role clarity enable stable progress in hybrid settings, while human factors remain crucial for success. The study offers concrete recommendations for instructors and student teams, contributing longitudinal, human-centered insights to the education-focused Agile literature and providing a replicable framework for evaluating collaboration tools in academic contexts.

Abstract

Agile methods, and Scrum in particular, are widely taught in software engineering education; however, there is limited empirical evidence on how these practices function in long-running, student-led projects under academic and hybrid work constraints. This paper presents a year-long case study of an eight-person student development team tasked with designing and implementing a virtual reality game that simulates a university campus and provides program-related educational content. We analyze how the team adapted Scrum practices (sprint structure, roles, backlog management) to fit semester rhythms, exams, travel, and part-time availability, and how communication and coordination were maintained in a hybrid on-site/remote environment. Using qualitative observations and artifacts from Discord, Notion, and GitHub, as well as contribution metrics and a custom communication effectiveness index (score: 0.76/1.00), we evaluate three dimensions: (1) the effectiveness of collaboration tools, (2) the impact of hybrid work on communication and productivity, and (3) the feasibility of aligning Scrum with academic timelines. Our findings show that (i) lightweight, tool-mediated coordination enabled stable progress even during remote periods; (ii) one-week sprints and flexible ceremonies helped reconcile Scrum with academic obligations; and (iii) shared motivation, role clarity, and compatible working styles were as critical as process mechanics. We propose practical recommendations for instructors and student teams adopting agile methods in hybrid, project-based learning settings.

The Anatomy of a Successful Student Scrum Team: Motivation, Personalities, and Academic Adaptation

TL;DR

This paper investigates how Scrum can be effectively taught and practiced in long-running, student-led projects under academic calendars and hybrid work constraints. It uses a year-long case study of an eight-person team developing a VR campus game, leveraging Notion for backlogs, Discord for communication, and GitHub for version control, augmented by a custom communication effectiveness index. The findings show that lightweight, tool-mediated coordination, one-week sprints with pause weeks around exams, and explicit attention to motivation and role clarity enable stable progress in hybrid settings, while human factors remain crucial for success. The study offers concrete recommendations for instructors and student teams, contributing longitudinal, human-centered insights to the education-focused Agile literature and providing a replicable framework for evaluating collaboration tools in academic contexts.

Abstract

Agile methods, and Scrum in particular, are widely taught in software engineering education; however, there is limited empirical evidence on how these practices function in long-running, student-led projects under academic and hybrid work constraints. This paper presents a year-long case study of an eight-person student development team tasked with designing and implementing a virtual reality game that simulates a university campus and provides program-related educational content. We analyze how the team adapted Scrum practices (sprint structure, roles, backlog management) to fit semester rhythms, exams, travel, and part-time availability, and how communication and coordination were maintained in a hybrid on-site/remote environment. Using qualitative observations and artifacts from Discord, Notion, and GitHub, as well as contribution metrics and a custom communication effectiveness index (score: 0.76/1.00), we evaluate three dimensions: (1) the effectiveness of collaboration tools, (2) the impact of hybrid work on communication and productivity, and (3) the feasibility of aligning Scrum with academic timelines. Our findings show that (i) lightweight, tool-mediated coordination enabled stable progress even during remote periods; (ii) one-week sprints and flexible ceremonies helped reconcile Scrum with academic obligations; and (iii) shared motivation, role clarity, and compatible working styles were as critical as process mechanics. We propose practical recommendations for instructors and student teams adopting agile methods in hybrid, project-based learning settings.
Paper Structure (45 sections, 2 equations, 4 figures, 3 tables)

This paper contains 45 sections, 2 equations, 4 figures, 3 tables.

Table of Contents

  1. Introduction
  2. Related Work
  3. Scrum in higher education
  4. Agile adaptations in non-industrial contexts
  5. Hybrid and remote teamwork
  6. Human factors in software engineering
  7. Collaboration Tools
  8. Notion:
  9. Discord:
  10. GitHub:
  11. Personalities in software engineering
  12. Gaps in the research
  13. Research Design
  14. Research Questions
  15. Project Context
  16. ...and 30 more sections

Figures (4)

  • Figure 1: Scrum-based workflow used in the project.
  • Figure 2: Summary of collaboration tools used in the case study: Discord (top), Notion (left), GitHub (right).
  • Figure 3: Task heatmap. Distribution of Tasks across a yearly timeline, broken down by weeks (x-axis) and monthly milestones (left y-axis).
  • Figure 4: Commit Frequency graph. The blue line indicates all the commits made during a month; the grey areas show months of remote work.