Product

We chose the Calender application

Using our application, students can:

Browse, add and delete courses

Subscribe/un-subscribe and receive notifications about picked courses.

Here's the demo

Process

Forking Model

Every team member had their own fork of the repo and worked individually on it.

We submitted a Pull Request to Master on completing a task.

This avoids conflicts and keeps the main repo clean.

Communication/Meetings

We met every week after class.

Communicated through Slack.

All the member's emails were linked to Github to get notifications on commits/PRs

Scrum vs Kanban

Scrum: Assigning priorities and difficulties to tasks, weekly meetings.

Kanban: Kept the tasks moving through the Kanban Board(Trello)

We preferred the Kanban Model because we kept the tasks moving at all times.

Architecture

Technologies

AngularJS + Bootstrap and Flask + SQLite + SVN (Jokes on you!)

Bower/Grunt for automating tasks.

Karma, Jasmine for testing the Front-End code

Model

We used the MVC model.

Decided to make a Web App instead of a Console App.

The backend serves JSON through REST API and does not generate pages.