IS480 Team wiki: 2015T2 Trackoholics/Finals
MAIN WIKI | MIDTERM WIKI | FINAL WIKI |
Contents
- 1 Links and Downloads
- 2 Project Progress and Overview
- 3 Project Management
- 4 Technical Complexity
- 5 Product Quality
- 6 Learning Outcomes
- 7 Reflections
Links and Downloads
Download our Final Presentation slides here: Final Presentation Slides
Visit our deployed application here: Café Management System
Project Progress and Overview
Current Iteration
- Iteration 13 : 02 Apr - 22 Apr 2015
- Tasks: Final Presentation Preparation
- Till date, 11 Apr 2015, 100% of project completed
Remaining Milestones
- Final Presentation: 16 Apr 15
- Poster Day: 22 Apr 15
Project Highlights
Since Midterm:
- Completion of last module, Analytics module
- Client Testing 3 with Tuckshop management
- User Acceptance Test 2 with 33 testers
- Live Deployment in The Tuckshop
- Live Deployment in Red Baron, a new client cafe
- Improvements to our Cafe Management System based on feedback from Midterm, Supervisor, CT, UAT and Live Deployment
Project Challenges
- Steep learning curve for Analytics
- Unsure of next live deployment of our application in The Tuckshop
Project Achievements
- Successfully implemented all functions in our scope
- Successfully achieved our midterm X-factor of live deployment in The Tuckshop for a week
- Successfully achieved our final X-factor of live deployment in The Tuckshop with >50 transactions
- Successfully deployed our application in a new client cafe, Red Baron, showing the versatility of our application
Project Management
Project Scope
Overall Scope
Scope Covered After Midterm
- Implementation of 3rd Module, Analytics
- Changes in Analytics Charts Generated (Shown in Purple in Actual Column)
Project Schedule (Planned vs Actual)
Planned Schedule
Actual Schedule
Change Management
Change Log
Schedule Metrics
Effort Metrics
Total Effort Metrics
Bug Metrics
Bug Count vs Bug Score Metrics
Project Risks
Risk Management
Technical Complexity
Technical Complexity 1
Technical Complexity 2
Technical Complexity 3
Product Quality
Project Deliverables
Project Area | Description | Links |
Project Overview | Description | Description |
Motivation | Motivation | |
Market Research | Market Research | |
Project Management | Metrics | Metrics |
Meeting Minutes | Meeting Minutes | |
Project Documentation | Internal Testing | Test Plan |
UI Prototype | Mockups | |
Project Deployment | Web Application | Café Management System |
Architecture Diagram
Testing
User Testing
Test Conducted | Date of Testing | No. of Testers | Demographic of Testers | Platform Used | Link |
User Acceptance Test 1 | 02 Feb 2015 | 30 |
|
Own Mobile Devices | UAT 1 |
User Acceptance Test 2 | 02 Apr 2015 | 33 | Ages:
|
Own Mobile and Tablet Devices | UAT 2 |
Client Test 1 | 12 Jan 2015 | 4 |
|
iPad and iPad Mini | CT 1 |
Client Test 2 | 07 Feb 2015 | 4 |
|
iPad and iPad Mini | CT 2 |
Client Test 3 | 16 Mar 2015 | 2 |
|
Samsung Tablet and MacBook | CT 3 |
Learning Outcomes
1. To manage the various stakeholder expectations (Supervisor, Team, Sponsor, Reviewers, Customers).
2. There will always be changes, and sometimes it’s up to our discretion to change it even if the client does not request.
Reflections
Team Reflections
1. Communication and communication logs are important.
2. We learnt that our diverse skill sets complement each other.
Individual Reflections
Charmaine
FYP definitely improved my knowledge of JavaScript and jQuery syntax. Before FYP there were a lot of JavaScript functions such as set time interval that I wasn’t aware of. I wasn’t familiar with jQuery animations such as the fadeIn and fadeOut that I ended up implementing for navigating between the tabs on the waiter’s interface in our e-ordering application. Before this I only knew very basic JavaScript like getting a value through a HTML element’s id or class name. Besides coding, I also learnt better time management because it was a great challenge to do a mod as intensive and tedious as FYP while juggling with other modules in SMU too. All in all it was a good learning experience as it improved my technical skills and also increased my exposure to working with a greater variety of people.
Inez
As a project manager, this project has taught me the importance of ensuring that skill sets in the group need to be diverse. It was only through our complementary skill sets was the group able to deal with the changes made by our client. FYP has also taught me a lot on giving and taking, which will probably be what the real life will be. Planning the schedule and managing the project sure wasn't easy, but I learnt the importance of each documentation and I realized that documentation really aided in the management of the project. I also learnt how to celebrate every milestone because if not, where's the joy in getting things done? (:
June
Through the roles of deputy project manager and coder in FYP, I got a chance to experience both the managing and developing side of an application. It is by no means an easy feat to balance between the 2 aspects, especially while juggling our sponsor's changing requirements. However, I have learnt that no obstacle is too hard to cross when the team works together to smoothen out problems and overcome challenges. I've also learnt more about technologies that I haven't been exposed before, and being the main minute-taker, I've learnt the importance of being concise while highlighting the gist of the problem or solution of the project.
Stephanie
Through the FYP journey, I’ve grown to become more outspoken as I have to communicate with the sponsor often as well as my team mates and supervisor. I’ve also learnt to work with a group with diverse skillsets and that how we use the skillsets to complement and assist each other. Most importantly, I’ve gained new knowledge skillsets on technologies such as Geo-Fencing, AJAX and DC libraries for analytics. FYP was indeed a good and memorable learning experience.
Wee Nee
Even as QA might seem like a minor part of the project, I have learnt the importance of testing the application consistently and thoroughly before we release it for live deployment or before any user tests. Through user and client tests, I learnt that the best way to gather feedback is through the potential real users. Overall, this project had taught me to work with many different people, be it my team mates, sponsors or supervisor.