In my Junior year, I took a class (OSU CSE 3902) who's focus was to professionally develop software
through understanding the agile process, learning design patterns, and working in a small group (5 people).
This was achieved by the creation of a 2D platformer (Mario Bros.). Unfortunately, there are no current
screenshots of the game, but the level more-or-less mirrors the first level of Super Mario Bros, save for a
couple individual touches we made at the end.
Course Webpage
Visual Studio online functioned as our issue-tracking software, a way for us to keep what specific issues needed to be
done for a given Sprint, what items were most important, and how much time they would take (not quite assigning story points,
but a sort of way of seeing how much we've gotten done.
The Backlog functioned like the one my team used while I was at Expedia, a list of the pertinent issues that we, as
a group, decided was the most important.
In order to track our progress within a given sprint, we utilized a burndown chart, with the goal of
it being a linear line downward (It didn't really work out this way, usually).
One of the main focuses when actually constructing the project was to keep things in order, and to
favor many classes with a small amount of code over a few classes with a lot of code. We made a concerted
effort to keep things as clean as possible to both keep things in order, and increase cohesion and decrease coupling.