Difference between revisions of "IS480 Team wiki: 2012T2 Team Chm MidTerm Wiki"

From IS480
Jump to navigation Jump to search
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
<big><p style="text-align: left; font-size: 150%;">[[IS480_Team_wiki:_2012T2_Team_Chm| <font color=#000000" style="text-align: center>'''Main Wiki''']]</font></p></big>
<big><p style="text-align: left; font-size: 150%;"><center>
[[IS480_Team_wiki:_2012T2_Team_Chm|<font color="#000000" face=""><ins>''' MAIN WIKI'''</ins></font>]] 
[[IS480_Team_wiki:_2012T2_Team_Chm_Final_Wiki|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]]

Latest revision as of 17:55, 16 April 2013




Project Progress Summary

Presentation Slides
Mobisupermarket Frontend Deployment Environment


Team Chm is in the midst of Sprint 10 at the moment.

There are several key accomplishments since the project inception on 26 Oct 2012:

  • Authentication
  • Manage Purchases
  • Manage Hooks - Coupons
  • Manage Campaigns
  • Manage Insights - Based on Transaction Data
  • Completed 2 usability test and are currently implementing solutions to given feedback

Team Chm is confident of completing the project within the stipulated schedule as shown below:


Project Highlights

Sprint 2
20 Nov 2012
04 Dec 2012

Incorrect commits to the repository altered files that were meant to be machine-specific

It was not only impractical to commit the entire working folder to our repository because it amounted to 109 megabytes, but also because certain files that resided in the working folder were machine-specific. Minimal documentation by Magento exacerbated the problem and hence the eventual solution only came about with advice from various tech sites (stackoverflow, roseindia, tech blogs) after 2 weeks of trial and error.

Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again.

Sprint 5

No transactional data for Insights

In the course of developing our BI tool during Sprint 5, the team was advised by our supervisor that we do not have any meaningful transactional data in our project. Hence, upon discussion with our sponsor, the team and the sponsor decided to to have a data gathering cum user testing session. Over 30 friends were invited so shop online using Magento E-commerce website, and they were each given $1000 virtual money to spend.

Sprint 7

No realistic data in our project

As the project progressed, the team was advised by our supervisor to try to make the spending behaviour slightly more genuine by means of incorporating real products that existed into the platform's catalog of products, which would in turn be more realistic during our User Tests. This rang true amongst the team because the products in the default catalog provided by Magento was either outdated or fictitious. Thus, both the sponsor and the team has been on the search for the products and their products' description to be input into our catalog. The team found the Yellow Mushmellow online blogshop, and the owner was willing to allow her products to be input into our catalog.

Technical Complexity

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

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.

Project Management

Project Status

Chapters Status Confidence Level (0-1) Member In-Charge
Authentication 100% developed and deployed 1 Joseph
Manage Campaign 100% developed and deployed 1 Leonard
Manage Hooks - Coupons 100% developed and deployed 1 Rachel
Manage Hooks - Social Messages 0% developed 0.9 Max
Manage Purchases 100% developed and deployed 1 Leonard & Rachel
Manage Insights 20% developed 0.9 Max

Project Scope

Project Use Cases

Project scope has not changed since inception

  • Chapters are categorized in priority circles:
  • Core and Good-to-have Features: Developed by Team Chm during IS480
  • Core features represents the features that must be delivered to the client
  • Good-to-have Features: Features of lower priority; can be implemented in future beyond this 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

Project Metrics

Schedule Metric

The diagram below shows the burn-down charts of the 9 sprints we have completed thus far:

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

Release Burn-down Chart


Burn-down Charts

Burndownchart1.png Burndownchart2.png Sprint91.png

Bug Metric


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

Added new Risks as at mid-term. Full entries are shown under the Project Management in the Risk Management Table.

Level of Impact (out of 10)
Mitigation Strategy
5. Getting meaningful and realistic testers In order for the project to realize its full potential, there is a need for professional feedback
Project Manager in talks with sponsor to organise a UAT session with MITB students.
6. Rate of development is decreasing Project would take a longer time to complete
Project Manager to plan and pre-empt the team of the tasks coming up in the following sprint and to encourage team mates to start studying earlier.

Product Quality

Intermediate Deliverables

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

Consumer Test Cases
Marketing Professional 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 Testing 1 (Data Gathering)


1. Determine that the usage of the features in magento are consistent to the expectations of the sponsor

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

3. Generate transaction data for our Business Intelligence Tool that will be implemented later

Scope of Test

Usability Test 1: A basic set up of the test in SMU
S/N Features Tested
1 Facebook Authentication / Log in / Log out Greentick.png
2 Change / Edit password Greentick.png
3 View their E-Wallet Balance Greentick.png
4 View Products Greentick.png
5 Add Product to Cart Greentick.png
6 Checkout Cart Greentick.png
7 Like a Product Greentick.png
8 Share a Product Greentick.png
9 Purchase with a coupon discount -

Conducted Session

User Testing 1 consisted of 2 sessions was successfully conducted on 23 & 24 Jan 2013, 1 – 3pm at the School of Economics SR 5.1 & SR 2.3 respectively.
A total of 30 students from the various schools in SMU assumed the role of a online shopper participated.

User Feedback

Chart 1

User Testing 1 Conclusion

Inferring from the table on the left, there was generally an overall "very good" and "good" feedback given on the easy of usability of Magento. In light of this result, our team has decided to go ahead with the use of Magento, as this E-commerce website was deemed user friendly and easy to use.

Another feedback given by the users was to add a required fill for the postal code upon checkout, this has since been rectified.

Nevertheless, many users expressed that on the whole, the system is easy to use, streamlined, “time-saving” and user-friendly. Users also mentioned that they are able to compare items easily and it was easy searching for products by category.

User Testing 2


1. Determine that the usage of the BI functions in magento are consistent to the expectations of a marketing student

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

3. Marketing students to create a marketing campaign and to observe how online shoppers will respond to it

Scope of Test

Usability Test 2: Poster

S/N Features Consumers Marketing Students
1 Facebook Authentication / Log in / Log out Greentick.png Greentick.png
2 Edit Password Greentick.png -
3 View their E-wallet Balance Greentick.png -
4 View Products Greentick.png -
5 Add Product to Cart Greentick.png -
6 Checkout Cart Greentick.png -
7 Like a Product Greentick.png -
8 Share a Product Greentick.png -
9 Purchase with a coupon discount Greentick.png -
10 Create & Design Coupon Hooks - Greentick.png
11 Delete Coupon Hook - Greentick.png
12 Create & Design Campaigns - Greentick.png
13 Delete Campaign - Greentick.png
14 Generate a graph from past Transactional Data - Greentick.png

Conducted Session

The User Testing 2 session was successfully conducted on 15 Feb 2013, 1 – 4pm at the School of Economics SR 2.5.
A total of 17 marketing major students from Professor Willem Smit class in SMU assumed the role of a marketing professional participated.
A total of 30 students from the various schools in SMU assumed the role of a online shopper participated across the week when the campaign was created

User Test cases for the Usability Test 2 is recorded in the following:

Most Common Feedback & Rectification

Solution: Informative Text for the coupon main page has been added
Solution: A back button has been added
Solution: Selected date has been displayed
Solution: Added an asterisk for the postal code

Results from End-of-Test Qualtrics Survey (Extract):

Chart 2

User Testing 2 Conclusion

User Testing 2 provided us with much insights especially to the overall intuitiveness of using our system. The top few feedback involves how candidates had difficulties in navigating and using the system; and we have since then made changes to the feedback given as shown.

Chart 2 further support this issue, where many candidates believe that the system is either slightly complex or they would need the help of a person to fully exploit the system.


Member Reflections Member Reflections


  • To try and gain more control over external factors in order to reduce the uncertainty of events
Picture 0056.JPG


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


  • I have concluded that caffeine is a placebo effect to me.


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


  • Time management, to balance work load with other module/commitments