HeaderSIS.jpg

IS480 Team wiki: 2012T2 Team Chm Final Wiki

From IS480
Jump to navigation Jump to search

FINAL WIKI

MAIN WIKI            MID-TERM WIKI


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:
FinalSchedule.png

Project Highlights

EVENT HIGHLIGHT / ISSUE
Sprint 11

Social Influence Quantification - Calculation of the effect of Social Messages

Team Chm included the quantification of the effects of Social Media Influence through a calculation suggested by our Sponsor. Upon creating a Social Message Hook and having been assigned to a campaign, it allows the hook to be applicable to a specified customer demographic. When a social message hook is implemented, Mobisupermarket will be able to collect browsing data by our shoppers. Using the Insights wizard, the marketing professional 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 had to fly back to Korea due to personal reasons. Although a similar situation happened in mid-terms (where our sponsor was not in town due to both personal & work), circumstances were less favorable this time as our sponsor faced problems in connecting with us through both our formal and informal channels of communication. Our final UAT dates were affected as well. Hence, we had to kick in our mitigation plans for the lack of realistic and meaningful testers mentioned in our mid-term presentation.

Project Challenges

EVENT HIGHLIGHT / ISSUE
Social Influence Quantification


  • Calculating the social influence scores and the technology required research and constant communication with our sponsor for details
  • Integrating FQL and Magento in order to be able to track viewing behaviours accurately
  • Considered as a technical complexity


User Acceptance Testing


  • Faced difficulties in securing testers (B6 students) due to the unavailability of our sponsor
  • Conducted a UAT on 5 Apr but to a varied pool of testers instead of mainly B.6 students


X-Factors (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

Metrics

Schedule Metrics

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

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


Overall Release Burn-down Chart

ReleaseBurndown2.png

Burn-down Charts

Burndownchart1.png Burndownchart2.png Burndownchart3.png Burndownchart4.png

Bug Metrics

ChmBug1.png


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.

In light of the upcoming UAT in Sprint 12, there was a spike in the number of bugs found in Sprint 12. This was because we did more rigorous regressive testing on our application before, during and after UAT.


Links

1. Bug Metric Calculation
2. Bug Metric Documentation



Risk Management

S/N
Risk
Mitigation Strategy
1.
High uncertainty; Constant change of final target audience Project Manager communicated with supervisor and sponsor consistently to better understand the situation and ensure that the development progress was not affected
2.
Outage of GoDaddy server Constantly made back-ups of the database on the server and ensured that the VM was updated regularly.
3.
Unavailability of our sponsor representative
  • Used both formal & informal channels of communication (to aid the convenience in contacting out sponsor).
  • Updated supervisor constantly when it got more inconvenient for our sponsor to stay in contact
4.
Getting meaningful & realistic testers
  • Carried out remote testing with our B.6 participants
  • Approached Marketing graduates
  • Approached SMU students who had Marketing as their first or second major

Technical Complexity

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

COMPLEXITY DESCRIPTION
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
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
  • AJAX write to database
  • Sequence of FB SDK initialization had to be taken into consideration
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
D3.js
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
Framework
  • 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
by ZURB
  • 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
Metrics
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


Deployment

  • 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. Backup VM
  4. Server Architecture & Resources

User Acceptance Test (UAT)

Objectives

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 and marketing major students' own comfort. With the help and support of our sponsor, we managed to get a few 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
Solution: Implemented the BI HomePage and made it into a dashboard
Solution: Implemented a mouse hover function to explain the 2 different scores



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



Reflections

Team Reflection

Lessons Learnt!

  • The Importance of Risk Management
  • Pre-empt, React, Backup plans; 5 out of 6 risks that we pre-empted took place. This illustrated the importance of being able to pre-empt, react and have back up plans in any project
  • Always pursue clarity in communication
  • We had everything we need. But things got lost in transmission. It was not accurately conveyed to the relevant stakeholders
  • Some things need to be kept constant
  • We felt that some things need to be constant through out the project and one of them is our target audience. Fundamentals such as our target audience should be established from the start to prevent snowballing effect.

Individual Reflections

Member Reflections Member Reflections
Ximin.jpg

Ximin

  • 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

Leonard

  • I have learnt to to have better time management and people skills
Mx.jpg

Max

  • I have concluded i operate on placebo effects.
Rachel.png

Rachel

  • Clear and concise is the way to go
27862 10150160662090024 1905740 n.jpg

Joseph

  • 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