Difference between revisions of "IS480 Team wiki: 2012T1 STEEP Mid Term Wiki"
Line 15: | Line 15: | ||
− | Our team has progressed slowly but steadily since our acceptance presentation. We | + | Our team has progressed slowly but steadily since our acceptance presentation. We faced issues along the way. However, we have managed to resolve them and have completed most of the core features. |
Initially, we planned to deploy our application on Google Play after User Testing 2. However, we are proud to state that as of 25 September 2012, we have deployed our application to the Google Play Store. | Initially, we planned to deploy our application on Google Play after User Testing 2. However, we are proud to state that as of 25 September 2012, we have deployed our application to the Google Play Store. |
Revision as of 20:02, 8 October 2012
Contents
Project Progress Summary
Mobile Platform:
Get our app now on Google Play
Web Platform:
Our team has progressed slowly but steadily since our acceptance presentation. We faced issues along the way. However, we have managed to resolve them and have completed most of the core features.
Initially, we planned to deploy our application on Google Play after User Testing 2. However, we are proud to state that as of 25 September 2012, we have deployed our application to the Google Play Store.
We are currently approaching 5th Milestone : Midterm Presentation.
Project Highlights
What unexpected events occurred?
- Our team faced issues with Amazon EC2 Cloud. Hence, we switched to Microsoft Azure.
- Microsoft Azure updated its version causing our system to fail. We had to spend time researching and trying different methods to make the functions work.
Project Management
Project Status
Project Schedule(Plan vs. Actual)
Milestones
Reasons :
Acceptance : We had issues with Amazon EC2 Cloud deployment a week before acceptance. Hence, we felt that it would be better to have abit more time.
Google Play Deployment: We were challenged by Prof Gan to have it deployed to Google Play by Midterm and we wanted to achieve it. Furthermore, we felt that it would be better for users to test on their own mobile phone.
Functions
Project Metrics
Project Risks
Technical Complexity
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
Project Management | Minutes | Meeting Minutes (Team, Sponsors, Supervisor) |
Metrics | ||
Risks | ||
Analysis | Use case | |
UI Mockup | Mobile, Web | |
Design | System Architecture Diagram (High Level) | |
System Architecture Diagram (Low Level) | ||
Testing |
Deployment
Mobile
Our Mobile application Gr8Quest has been published on Google Play since 25 September 2012. We were required to create an account, pay for a developer account and upload the relevant APK file into the Google Play Store.
Users with android devices are able to download and use our application.
Web
Our Website has been deployed using Microsoft Azure.
Testing
Our User Testing 1 was conducted on 2 separate occasions, 28 September 2012 (in SIS) and 1 October 2012 (in Fort Canning).
Link : User Testing |
|
Reflections
Link : Learning Outcomes Page |
|
Team Reflection
Our FYP has been an amazing journey for our team so far.
We definitely went through many hurdles along the way to reach where we are right now. There were various instances when we had to prove ourselves to move forward. For instance, we submitted our names for FYP after the deadline resulting in us having to move faster to confirm our project details with Prof Ben Gan in order to confirm a place for FYP.
3 key reflections for us are:
1. Teamwork: We should be supportive to one another which would ensure a proper working environment for the team. By sharing the workload and taking on tasks when there is nothing on hand, we can work faster.
2. Communication: The key to a successful team is communication. As a team, we should not be afraid to voice out our thoughts and opinions to each other. With proper communication, various misunderstandings can be avoided.
3. Prioritization: FYP is not the only module for us and some members are working part-time as well. Hence, we have to prioritize our workload in order to meet deadlines. At times, this includes cancelling or rescheduling our personal outings / interests in order to complete tasks for FYP.
We are indeed very grateful to our sponsors and supervisor who gave us their feedback and suggested improvements.
Individual Reflections
Sunita
The FYP journey so far has been an amazing one for me. Having friends as group members can be both good and bad. Being the Project Manager, there were various times initially where I could not be stern with the team as they are my friends and I do not want to stress them out as well.
It is definitely a challenge being a Project Manager in ensuring everything is up to schedule and being answerable to the questions by the Sponsors. The lessons learnt are invaluable for future careers when taking on leadership roles.
Minh Tri
Qian Ying
It has been an incredible 3 months since we first embarked on this project. Our group faced many challenges in different aspects of the project. We had to juggle between meeting deadlines of IS480 and other modules as well as lifting up to different expectations set by group members, sponsors and professors.
Being the usability analyst, I was tasked to design an application which is user friendly and aesthetically attractive. To accomplished that, I had several elements to take into consideration such the layout of data and the amount of the information displayed to the user. Designing a “treasure hunt” theme and choosing appropriate naming conventions for the game are also part of my job. From all the problems I faced thus far, it has been indeed intellectually challenging and pushing the limits of my creativity.
Eileen
Emerald
Teamwork: For me, teamwork and communication among team members are the most vital skill that I have learnt during FYP. In our group, each of us is responsible for one part of either application development or project management, so we need to communicate and work together closely to ensure the quality of the end-product at the same time keeping track of the project schedule.