IS480 Team wiki: 2012T2 Team Chm Final Wiki

From IS480
Jump to navigation Jump to search



Team Chm1.jpg

Project Progress Summary

View our one minute pitch HERE

1.   Final Presentation Slides

2.   Team Chm Deployed Site Link

3.   1 Minute Pitch

4.   Poster

  • Team Chm has completed 13 sprints in total and is now finishing its final milestone.
  • This is where we are on the timeline:

Project Highlights

Sprint 11

Social Influence Quantification - Algorithm to quantify the effect of Social Messages

Team Chm developed the quantification of the effects of Social Media Influence through an algorithm. Through the creation of a Social Message Hook, then assigning it to a campaign, this allows the hook to be applicable to a specified customer demographics base. Through the Social Message Hook creation, Mobisupermarket will track the viewer of the page via its Facebook ID and what Social message the viewer observed or the product bought. The marketing professional through the Insights wizard will then be able to visualize the relevant social influence data through the computation of the social influence score.

Sprint 11 - 13

Sponsor unavailability

Our Sponsor, who is the POC was unavailable and not contactable for a few weeks. We had to improvise and come up with new risk mitigation plan during this period as our User Acceptance Test (UAT) was approaching. Subsequently, with the help of our supervisor we managed to carry out our mitigation plan.

Project Challenges

Social Influence Quantification

  • Developing the Social Influence Algorithm and the technology required research and constant communication with our sponsor for details
  • The tracking of social message views proves to be an uphill task
  • Considered as a technical complexity

User Acceptance Testing

  • Faced difficulties in securing testers (B6 students) due to the unavailability of our sponsor
  • Still managed to conduct a UAT on 5 Apr but to a smaller pool of testers

X-Factor (Poster Form)

Team Chm Poster.png

Project Management

Project Schedule (Planned VS Actual)

Planned2.png Actual1.png

No changes to proposal and acceptance milestones; and only milestones after them have significant changes to the schedule.
Refer to the current timeline for more information.

Change #1: An additional User Testing, for data gathering needed for our BI tool has been added
Change #2: Part of the Manage Hook function has been shifted over to past mid terms
Change #3: Part of the Manage Insights has been shifted to before mid terms


Schedule Metrics

The diagram below shows the burn-down charts of the 13 sprints we have completed:

1. Schedule Metric Calculation
2. Schedule Metric Documentation for Sprint Number: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13

Release Burn-down Chart


Burn-down Charts

Burndownchart1.png Burndownchart2.png

Bug Metrics


Number of Bugs Found

There was a spike in the number of bugs found in Sprint 9. This is due to the more rigorous testing conducted on our application during User Testing 2.

Also, there are six bugs that are carried over from Sprint 9 to 10 because we did not manage to resolve them in time.


1. Bug Metric Calculation
2. Bug Metric Documentation

Risk Management

Technical Complexity

The technical complexities of our tools employed are in the following descending order:

Creation of Social Message Hooks
  • What is it?
  • Creation of Social Message Hooks that is applicable to customer base of demographics specified
  • What was complex?
  • Retrieving the required EAV data
  • Selection of required demographics
  • Applying the hook to the customer that fits the demographics specified
  • Rendering the product page for the customer based on the respective setting
  • Why did we use it?
  • Client requirement — "A novelty idea to quantify social influence"
Tracking of Social Message Views
  • What is it?
  • Tracking the viewer of the page, and what social message the viewer observed
  • What was complex?
  • Retrieving the required EAV data
  • Retrieving the customer's Facebook friends who are also customers on Mobisupermarket via FQL
  • AKAX write to database
  • Sequence of FB SDK initialization had to be taken into consideration
  • Why did we use it?
  • Client requirement — "A novelty idea to quantify social influence"
Magento Community Edition
  • What is it?
  • Open source e-commerce framework
  • What was complex?
  • Complex directory Structure
  • Based on the Zend Framework
  • Complex database structure - EAV
  • Click here for Magento ER diagram
  • Why did we use it?
  • Client requirement — "Magento is very powerful because it gives very granular control of its features, thus making it extensible and scalable for future development."
  • From our data generation sessions, feedback was given that it was easy to use and navigate
Data Manipulation Framework
  • What is it?
  • D3.js is a JavaScript library for manipulating documents based on data
  • What was complex?
  • Challenging process of making use of the D3.js API to manipulate data generated from Magento E-commerce website
  • Why did we use it?
  • Javascript library for building interactive, beautiful and custom data driven charts
jQuery UI
  • What is it?
  • jQuery UI is a JavaScript library that provides abstractions for low-level interaction and animation, advanced effects and high-level, themeable widgets, built on top of the jQuery JavaScript library, that can be used to build interactive web applications.
  • What was complex?
  • Challenging process of implementing the jQuery library and aligning it to the client's requirements
  • Why did we use it?
  • jQueryUI is a mature and reliable framework. There is an active community supporting it and plenty of information is available on blog spots and discussion forums.
Foundation Framework
  • What is it?
  • ZURB Foundation is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions
  • What was complex?
  • Process of learning, downloading and implementing the foundation framework library and aligning it to our project.
  • Why did we use it?
  • Foundation is known to be the most advanced responsive front-end framework in the world. Foundation is developed in Sass, which is powerful CSS pre-processor that helps users to write cleaner, more organized, CSS that users can easily maintain over time. On top of the minimal styling, Foundation has also written powerful Javascript plugins that will make useful interactions easier to implement across screen sizes.

Quality of Product

Project Deliverables

Stage Specification Modules
Project Management Minutes
Requirements Product Backlog
UI Mockups
Analysis Use Case
Design ER Diagram
Server Architecture
Testing User Testing 2 Plan

Consumer Test Cases
Marketing Professional Test Cases

User Acceptance Test

User Acceptance Test Cases


  • Staging & Development Environment: deployed on GoDaddy server
  • Database: Magento EAV database structure
  • Web Links:
  1. Mobisupermarket Frontend Deployment Environment
  2. Mobisupermarket Frontend Staging Environment
  3. Server Architecture & Resources

User Acceptance Test (UAT)


1. Determine if the users are capable of handling the application on their own (without any physical guidance from us, just a document instructing the steps)

2. Obtain feedback from users such as to improve the usability (learnability, efficiency, errors, satisfaction) and aesthetics of Magento

Test Details & Outcome

User Acceptance Test (UAT) was conducted from 5 April 2013 to 11 April 2013 remotely at the B.6 students' own comfort. With the help and support of our sponsor, we managed to get some of her ex B.6 students to become a Marketing Professional, and to create a campaign of both coupons and social messages. They are provided a softcopy word document whereby they will be asked to give us their feedback.

Most Common Feedback & Rectification

Solution: Implemented a dropdown list instead of a table for product category
Solution: Placed a % sign beside the input field

User Test Cases for the User Acceptance Test is recorded as follows:


Team Reflection

Lessons Learnt!

  • The Importance of Backup Plans
  • Despite the project being created originally because of the B6 class, Prof Kyong envisioned this project to be part of a bigger scheme of things in the world of marketing education, and originally was in talks with Prof Michael Netzley, MediaCom — a South East Asian marketing firm, SMU Exec Devt and Louis Vuitton, and Prof Wilheim from LKCSB. Eventually, with the exception of Prof Wilheim, the majority of the project’s testers were our peers who majored in marketing.
  • Always pursue clarity in communication
  • The message on our project scope and nature of our project was not clearly communicated with our supervisor.
  • As a result, Supervisor and Sponsor views’ contrasted in week 4. We struggled to adjust our project goals in such a way that puts both sides’ inputs into high consideration.
  • It is hence important that we clearly communicate how we view the project and how we communicate that view with others

Individual Reflections

Member Reflections Member Reflections


  • To always check my sent items and ensure that emails are sent out
  • One can and should never ever run out of mitigation plans
Picture 0056.JPG


  • To know the limits of each and every one team member and work to their strengths


  • I have concluded i operate on placebo effects.


  • Huge amount of efforts are needed to make an application user friendly
27862 10150160662090024 1905740 n.jpg


  • Learnt a little of jQuery and Javascript which are useful frontend development skills to bring to the working world

"We believe that Mobisupermarket will transform the way marketing trainees and IT systems interact, providing these trainees with an efficient alternative to the traditional data analytics."

~ Prof Kyong Jin Shim
~9 March 2013