-
Notifications
You must be signed in to change notification settings - Fork 1
Proposal
The following is the proposal for the CourseModo Android application.
| NAME | STUDENT No. | COOP STATUS | ROLE |
| Sami Bouchebaba | 4862508 | Non-coop | Project Manager; ScrumMaster |
| Karan Khanna | 5119702 | Non-coop | Build Manager; Architect |
| Amy Wong | 5632880 | Non-coop | Business Analyst; Architect |
| Justin Fleury | 4798883 | Non-coop | QA Manager; Architect |
| Andre Viau | 4826503 | Non-coop | Architect; Lead Dev. |
| Patrick Ronayne | 5698293 | Non-coop | Architect; Lead Dev. |
The objective of this project is to build the Android application for CourseModo which is going to be used by students inside the classroom in order to interact with the professor. Coursemodo is a new collaborative learning tool that focuses on enhancing the professor-student dynamic through in-class polls, quizzes and live feedback. Coursemodo aims to “make class fun” by enriching the students’ learning experience.
Studies show that a majority of post-secondary students own smartphones; this project will leverage this in order to improve student engagement in the classroom environment. The mobile version of CourseModo will be key in providing the ability for a real-time feedback loop for teachers. The teachers can immediately see how students are engaging and where they need more help and/or better explanations.
Amine Haddad is the chief technical officer and head of engineering for Coursemodo. Previously, the company produced NoteWagon, an application that allows students to share study guides online.
Because the customer is located in Toronto, communication will be done over e-mail, Google Hangouts, Skype and bi-monthly meetings in person with the entire team. Customer’s contact information will be delivered shortly.
Contact: Customer E-mail
The platform for this project is Android, and everything will be done using Java. There is no need for hardware as the Android emulator will work fine for displaying the functionality through demos as well as testing.
This is the mobile extension of the CourseModo web-based application .
We anticipate facing challenges in interfacing our Android/Java-based application with the back-end of the current product which is written using the Django/Python framework. We plan on addressing this issue with the customer from the outset and will request access to their API so that core functionality can be accessed using remote procedure calls.
A business-side issue we face is the direct competition from Top Hat Monocle, a similar classroom response system. We plan on finishing the Android App by December, so that iOS development can begin in the second part of this project course (this is still tentative, pending discussion with the customer).
Since the group consists of six members, another potential challenge would be disorganization. With this many people it would be easy to become disorganized or for there to be some miscommunication. This challenge will be addressed by having frequent stand-up meetings and by frequently sending out emails regarding updates and plans.
From a business perspective, this application would be quite beneficial because it provides more options for students to choose from when using CourseModo in the classroom. CourseModo can be easily accessed through the web. However, if a student does not typically bring a computer to class, they would also have the option of installing the app on their Android phone. This becomes a great marketing aspect for the company. A liability which may be produced by this is that the application will only be available on the Android platform and not on iOS or Blackberry.
From an environmental perspective, this application will be great because it provides an easier and more efficient way for professors to engage students, instead of using old fashioned paper.
From the perspective of an end-user, this the CourseModo android application is very useful. Access to CourseModo through mobile devices makes it much more appealing than solely being accessible through the web. The end-users reap the full benefits of this application.
The team will be following a Scrum agile process in producing this application.
- Iterations (sprints) will be 2 weeks long;
- Sprint planning sessions at the beginning of each sprint (mandatory for all team members);
- There will be stand-up meetings 3 times a week; all team members are required to attend (remote attendance is acceptable);
- Product backlog grooming meetings (an hour) will be held to divide user stories into tasks;
- Sprint demos will be held at the end of each sprint to review the work that was completed (and not completed) and present the completed work the stakeholders (Customer)
- Sprint retrospective meetings at the end of each sprint in which all team members reflect on the past sprint to make continuous process improvements. What went well during the sprint? What could be improved during the next sprint? (1-2 hours).
We will be using an open source agile management tool, PangoScrum to manage the product backlog and sprint planning tasks.
Progress will be evaluated at the end of each sprint. Sprint retrospective meetings will be held immediately after each demo to the customer. The number of user stories and tasks completed will be considered as an evaluation metric; we will also reflect on the accuracy of time estimates for completing tasks given by each team member at the beginning of the iteration. May use a burn-down chart to model the progress made by each sprint.
Code inspections will be done weekly for about an hour to make sure everyone is on the right track and to aid any members of the group on their particular part.
Test subjects may be selected by the client and/or development team in order to gain knowledge about the intuitiveness of the application throughout development.
Schedule for the work, including documents you plan to deliver, and on what dates. Gantt and Pert charts can help convey this information.
To be determined.