ScrumBoard
A web-based Scrum project management tool built for software engineering education, with identity management, a developer dashboard, and ML-powered reflection classification.
A web-based Scrum project management tool built for software engineering education, with identity management, a developer dashboard, and ML-powered reflection classification.
Automatically injects OWASP Top Ten vulnerabilities into a Django app, turning it into a ready-made environment for hands-on cybersecurity training.
Helps researchers manage and screen papers for systematic reviews and meta-analyses, with collaborative yes/no/maybe decisions and role-based access.
Over the past few years, we’ve been developing a web-based tool to support students tracking their progress in an agile software development course. In this blog, I’ll explain why we moved away from professional / industry-grade tools and decided to (not) reinvent the wheel.
A few years ago, we looked into how teams deal with the technical debt in a software engineering project course (DOI to paper). One of the main takeaway from the focus group that followed an extensive data analysis (of the evolution of the quality of the code of 8 teams) and a survey (with 25 responses, being 40-ish % of the class) is that the adoption of clean code practices seem to be strongly influenced by a charismatic and engaged “team leader”. From a literature review (to appear soon at EASE, preprint here), we observed that the same pattern, i.e. the need for strong advocates in teams, exist for automated software testing in industry context. From these two studies, I believe that “old” XP advocates actually got it right and we have failed miserably to listen to them. Therefore, we felt into the same trap as before, i.e. process rigidity and putting the process before the people (and when I say “we”, I think education and industry).
I’ll talk about how we teach about Scrum events and principles in a gamified context. First of all, the whole credit goes to Sonja Hof et al.. You may check their paper (just click on Sonja’s name, it’s a hyperref) that we modified a little and tried to adapt to fix the issues they witnessed in their experiment. One day, I actually should try to contact that team to see if they still do this tutorial and if they changed anything.