Difference between revisions of "IS480 Team wiki: 2012T2 Team Chm Final Wiki"
(96 intermediate revisions by 3 users not shown) | |||
Line 10: | Line 10: | ||
[[IS480_Team_wiki:_2012T2_Team_Chm_MidTerm_Wiki|<font color="#000000" face=""><ins>''' MID-TERM WIKI'''</ins></font>]] | [[IS480_Team_wiki:_2012T2_Team_Chm_MidTerm_Wiki|<font color="#000000" face=""><ins>''' MID-TERM WIKI'''</ins></font>]] | ||
</center></p></big><br> | </center></p></big><br> | ||
− | [[Image:Team_Chm1.jpg| | + | [[Image:Team_Chm1.jpg|580px|right]] |
== Project Progress Summary == | == Project Progress Summary == | ||
− | [[Image:VideoChm.png| | + | [[Image:VideoChm.png|400px|thumb|'''View our one minute pitch [http://vimeo.com/62894698 HERE]''']] |
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
|scope="row" width="700" style="text-align: left; background: #F5F5F5"| | |scope="row" width="700" style="text-align: left; background: #F5F5F5"| | ||
− | ''' '''<font color="#000000"><big><b>Final Presentation Slides</b></big></font><br><br> | + | 1.''' '''<font color="#000000"><big><b>[https://www.dropbox.com/s/tbvr0ip8y9g8h22/TeamChmFinalPresentation.pdf Final Presentation Slides]</b></big></font><br><br> |
− | ''' '''<font color="#000000"><big><b>[http://mobisupermarket.com/bonx Team Chm Deployed Site Link]</b></big></font><br> | + | 2.''' '''<font color="#000000"><big><b>[http://mobisupermarket.com/bonx Team Chm Deployed Site Link]</b></big></font><br><br> |
− | + | 3.''' '''<font color="#000000"><big><b>[http://vimeo.com/62894698 1 Minute Pitch]</b></big></font><br><br> | |
+ | 4.''' '''<font color="#000000"><big><b>[https://www.dropbox.com/s/yrk8wj1uh1dsp2s/Team%20Chm%20Poster.png Poster]</b></big></font> | ||
+ | |}<br> | ||
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
Line 40: | Line 42: | ||
! scope="row" style="background: #C0C0C0"| '''Sprint 11''' | ! scope="row" style="background: #C0C0C0"| '''Sprint 11''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | '''Social Influence Quantification - | + | '''Social Influence Quantification - Calculation of the effect of Social Messages ''' <br /><br /> |
+ | 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. | ||
|- | |- | ||
Line 46: | Line 49: | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
''' Sponsor unavailability ''' <br /><br /> | ''' Sponsor unavailability ''' <br /><br /> | ||
− | Our Sponsor | + | 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. |
|} | |} | ||
Line 56: | Line 59: | ||
! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font> | ! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font> | ||
|- | |- | ||
− | ! scope="row" style="background: #C0C0C0"| ''' | + | ! scope="row" style="background: #C0C0C0"| '''Social Influence Quantification ''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
<br> | <br> | ||
− | * | + | *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 | *Considered as a technical complexity | ||
<br> | <br> | ||
Line 68: | Line 72: | ||
<br> | <br> | ||
*Faced difficulties in securing testers (B6 students) due to the unavailability of our sponsor | *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 |
<br> | <br> | ||
|- | |- | ||
Line 74: | Line 78: | ||
|} | |} | ||
− | + | === X-Factors (Poster Form) === | |
+ | <center>[[Image:Team_Chm_Poster.png|1000px]]</center> | ||
+ | <br> | ||
== Project Management == | == Project Management == | ||
=== Project Schedule (Planned VS Actual) === | === Project Schedule (Planned VS Actual) === | ||
+ | |||
+ | |||
+ | {| | ||
+ | |[[Image:Planned2.png|500px]] | ||
+ | |[[Image:Actual1.png|560px]] | ||
+ | |} | ||
+ | |||
+ | <br style="clear:both" /> | ||
+ | No changes to proposal and acceptance milestones; and only milestones after them have significant changes to the schedule.<br> Refer to the '''<big><big>[[IS480/2012T2_Team_Chm:_Project_Management#Schedule|current timeline]]'''</big></big> for more information. | ||
+ | <br><br> | ||
+ | '''Change #1''': '''An additional User Testing''', for data gathering needed for our BI tool has been added<br> | ||
+ | '''Change #2''': Part of the '''Manage Hook''' function has been shifted over to past mid terms<br> | ||
+ | '''Change #3''': Part of the '''Manage Insights''' has been shifted to before mid terms<br> | ||
+ | <br> | ||
+ | |||
=== Metrics === | === Metrics === | ||
==== Schedule Metrics ==== | ==== Schedule Metrics ==== | ||
+ | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
+ | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
+ | |||
+ | The diagram below shows the burn-down charts of the 13 sprints we have completed: <br /> | ||
+ | |||
+ | '''Links'''<br> | ||
+ | '''1. [https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Management#Schedule_Metric Schedule Metric Calculation]<br /> | ||
+ | '''2. Schedule Metric Documentation for Sprint Number:''' | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=26 1], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=11 2], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=13 3], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=12 4], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=20 5], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=22 6], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=21 7], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=23 8], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=24 9], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=28 10], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=29 11], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=31 12], | ||
+ | [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=32 13] | ||
+ | |||
+ | <br> | ||
+ | <big><big>'''Overall Release Burn-down Chart'''</big></big><br><br> | ||
+ | [[Image:ReleaseBurndown2.png|525px]]<br /><br /> | ||
+ | <big><big>'''Burn-down Charts'''</big></big><br><br> | ||
+ | [[Image:Burndownchart1.png|525px]] | ||
+ | [[Image:Burndownchart2.png|525px]] | ||
+ | [[Image:Burndownchart3.png|525px]] | ||
+ | [[Image:Burndownchart4.png|525px]] | ||
+ | <br><br> | ||
+ | |||
+ | |} | ||
+ | |||
==== Bug Metrics ==== | ==== Bug Metrics ==== | ||
+ | [[Image:ChmBug1.png|500px|thumb|left]] | ||
+ | <br> | ||
+ | {| class="wikitable" style="text-align: center; height:50px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="row" width="600" style="text-align: center; background: #F5F5F5"|'''Number of Bugs Found'''<br> | ||
+ | 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. <br><br> | ||
+ | Also, there are six bugs that are carried over from Sprint 9 to 10 because we did not manage to resolve them in time.<br><br> | ||
+ | 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.<br><br> | ||
+ | |} | ||
+ | <br> | ||
+ | {| class="wikitable" style="text-align: center; height:50px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="row" width="800" style="text-align: center; background: #F5F5F5"|'''Links'''<br> | ||
+ | '''1. [https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Management#Bug_Metric Bug Metric Calculation]'''<br> | ||
+ | '''2. [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=4 Bug Metric Documentation]''' | ||
+ | |} | ||
+ | |||
+ | <br><br> | ||
+ | |||
+ | === Risk Management === | ||
+ | {| class="wikitable" style="text-align: center; height:100px | ||
+ | |- | ||
+ | | ! scope="col" width="50" style="background-color:#4E4E4E"| <font color="#ffffff"><b><center>S/N</center></b></font> | ||
+ | | ! scope="col" width="300" style="background-color:#4E4E4E"| <font color="#ffffff"><b><center>Risk</center></b></font> | ||
+ | | style="background-color:#4E4E4E"| <font color="#ffffff"><b><center>Mitigation Strategy</center></b></font> | ||
+ | |- | ||
+ | | style="background: #C0C0C0"|<center>''' 1.'''</center> | ||
+ | | 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 | ||
+ | |- | ||
+ | | style="background: #C0C0C0"|<center>''' 2.'''</center> | ||
+ | | Outage of GoDaddy server | ||
+ | | Constantly made back-ups of the database on the server and ensured that the VM was updated regularly. | ||
+ | |- | ||
+ | |style="background: #C0C0C0"|<center>''' 3'''.</center> | ||
+ | | 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 | ||
+ | |||
+ | |- | ||
+ | |style="background: #C0C0C0"|<center>''' 4.'''</center> | ||
+ | | Getting meaningful & realistic testers | ||
+ | | | ||
+ | *Carried out remote testing with our B.6 participants | ||
+ | *Approached Marketing graduates | ||
+ | *Approached SMU students who had Marketing as their <u>first</u> or <u>second major</u> | ||
+ | |- | ||
+ | |} | ||
+ | |||
=== Technical Complexity === | === Technical Complexity === | ||
+ | The technical complexities of our tools employed are in the following descending order: <br /> | ||
+ | |||
+ | {| class="wikitable" style="text-align: center; height:100px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="col" width="100" style="background-color:#4E4E4E"| <font color="#ffffff">COMPLEXITY</font> | ||
+ | ! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">DESCRIPTION</font> | ||
+ | |||
+ | |- | ||
+ | ! scope="row" style="background: #C0C0C0"| '''Creation of Social Message Hooks''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''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 | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | ! scope="row" style="background: #C0C0C0"| '''Tracking of Social Message Views''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''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 | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | ! scope="row" style="background: #C0C0C0"| '''Magento Community Edition''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''What is it?''' | ||
+ | :*Open source e-commerce framework | ||
+ | *'''What was complex?''' | ||
+ | :*Complex directory Structure | ||
+ | :*Based on the Zend Framework | ||
+ | :*Complex database structure - EAV | ||
+ | ::* Click [https://wiki.smu.edu.sg/w/is480/images/9/90/Magentodatabase2.png here] for Magento ER diagram | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background: #C0C0C0"| '''D3.js <br> Data Manipulation Framework''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''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 | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background: #C0C0C0"| '''jQuery UI<br> Framework''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''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. | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background: #C0C0C0"| '''Foundation Framework<br/>by ZURB ''' | ||
+ | |style="text-align: left;"| | ||
+ | *'''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 == | == Quality of Product == | ||
Line 126: | Line 309: | ||
|- | |- | ||
− | ! scope="row" rowspan=" | + | ! scope="row" rowspan="2" style="background: #C0C0C0"|Design |
|style="text-align: center;"|ER Diagram | |style="text-align: center;"|ER Diagram | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
*[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#ER_Diagram ER Diagram] | *[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#ER_Diagram ER Diagram] | ||
|- | |- | ||
+ | |style="text-align: center;"|Server Architecture | ||
+ | |style="text-align: left;"| | ||
+ | *[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#Server_Architecture_.26_Resources Server Architecture] | ||
+ | |- | ||
+ | |||
! scope="row" rowspan="2" style="background: #C0C0C0"|Testing | ! scope="row" rowspan="2" style="background: #C0C0C0"|Testing | ||
Line 140: | Line 328: | ||
|style="text-align: center;"|User Acceptance Test | |style="text-align: center;"|User Acceptance Test | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | [https://wiki.smu.edu.sg/w/is480/images/d/da/ChmUAT.pdf User Acceptance Test Cases] | |
− | [https://wiki.smu.edu.sg/w/is480/images/d/ | ||
|- | |- | ||
|} | |} | ||
− | + | ||
+ | |||
=== Deployment === | === Deployment === | ||
Line 156: | Line 344: | ||
:#'''[http://mobisupermarket.com/bonx Mobisupermarket Frontend Deployment Environment]''' | :#'''[http://mobisupermarket.com/bonx Mobisupermarket Frontend Deployment Environment]''' | ||
:#'''[http://mobisupermarket.com/magento Mobisupermarket Frontend Staging Environment]''' | :#'''[http://mobisupermarket.com/magento Mobisupermarket Frontend Staging Environment]''' | ||
+ | :#'''[http://202.161.45.168/magento Backup VM]''' | ||
:#'''[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#Server_Architecture_.26_Resources Server Architecture & Resources]''' | :#'''[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Design#Server_Architecture_.26_Resources Server Architecture & Resources]''' | ||
=== User Acceptance Test (UAT) === | === User Acceptance Test (UAT) === | ||
+ | |||
+ | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
+ | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
==== Objectives ==== | ==== Objectives ==== | ||
+ | |||
+ | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
+ | |scope="row" width="1000" style="text-align: left; background: #FFF8C6"| | ||
+ | '''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) <br><br> | ||
+ | '''2. Obtain feedback from users such as to improve the usability (learnability, efficiency, errors, satisfaction) and aesthetics of Magento'''<br> | ||
+ | |} | ||
+ | <br> | ||
+ | |||
==== Test Details & Outcome ==== | ==== 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. <br><br> | ||
+ | |||
+ | <b>Most Common Feedback & Rectification</b><br> | ||
+ | {| | ||
+ | | [[Image:ChmImprovement5.png|500px|thumb|'''Solution: '''Implemented a dropdown list instead of a table for product category]] | ||
+ | | [[Image:Chmimprovement6.png|500px|thumb|'''Solution: '''Placed a % sign beside the input field]] | ||
+ | |} | ||
+ | |||
+ | {| | ||
+ | | [[Image:BI_HomePage.png|500px|thumb|'''Solution: '''Implemented the BI HomePage and made it into a dashboard]] | ||
+ | | [[Image:tooltip.png|500px|thumb|'''Solution: '''Implemented a mouse hover function to explain the 2 different scores]] | ||
+ | |} | ||
+ | |||
+ | <br><br> | ||
+ | User Test Cases for the User Acceptance Test is recorded as follows: | ||
+ | *[https://wiki.smu.edu.sg/w/is480/images/d/da/ChmUAT.pdf UAT Test Cases] | ||
+ | *[http://smusg.asia.qualtrics.com/SE/?SID=SV_6Kb2Y2eForYsLCB Survey for our UAT testers and their feedback] | ||
+ | |||
+ | |||
+ | |||
+ | |} | ||
+ | <br> | ||
== Reflections == | == Reflections == | ||
+ | |||
+ | === Team Reflection === | ||
+ | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
+ | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
+ | |||
+ | <big><font color="#CE2B2B">'''Lessons Learnt!'''</font></big> | ||
+ | <br> | ||
+ | :*'''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 === | === Individual Reflections === | ||
{| class="wikitable" style="text-align: center; height:350px" | {| class="wikitable" style="text-align: center; height:350px" | ||
Line 176: | Line 416: | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Ximin'''<br> | '''Ximin'''<br> | ||
− | *To | + | *To always check my sent items and ensure that emails are sent out |
+ | *One can and should never ever run out of mitigation plans | ||
|style="background: #000000"|[[Image:Picture_0056.JPG|120px]] | |style="background: #000000"|[[Image:Picture_0056.JPG|120px]] | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Leonard'''<br> | '''Leonard'''<br> | ||
− | * | + | *I have learnt to to have better time management and people skills |
|- | |- | ||
Line 186: | Line 427: | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Max'''<br> | '''Max'''<br> | ||
− | *I have concluded | + | *I have concluded i operate on placebo effects. |
|style="background: #000000"|[[Image:rachel.png|120px]] | |style="background: #000000"|[[Image:rachel.png|120px]] | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Rachel'''<br> | '''Rachel'''<br> | ||
− | * | + | *Clear and concise is the way to go |
|- | |- | ||
Line 197: | Line 438: | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
'''Joseph'''<br> | '''Joseph'''<br> | ||
− | * | + | *Learnt a little of jQuery and Javascript which are useful frontend development skills to bring to the working world |
|} | |} | ||
Latest revision as of 16:38, 19 April 2013
FINAL WIKI |
Project Progress Summary
1. Final Presentation Slides |
|
Project Highlights
EVENT | HIGHLIGHT / ISSUE |
---|---|
Sprint 11 |
Social Influence Quantification - Calculation of the effect of Social Messages |
Sprint 11 - 13 |
Sponsor unavailability |
Project Challenges
EVENT | HIGHLIGHT / ISSUE |
---|---|
Social Influence Quantification |
|
User Acceptance Testing |
|
X-Factors (Poster Form)
Project Management
Project Schedule (Planned VS Actual)
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 |
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. |
---|
Links |
---|
Risk Management
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 | |
Outage of GoDaddy server | Constantly made back-ups of the database on the server and ensured that the VM was updated regularly. | |
Unavailability of our sponsor representative |
| |
Getting meaningful & realistic testers |
|
Technical Complexity
The technical complexities of our tools employed are in the following descending order:
COMPLEXITY | DESCRIPTION |
---|---|
Creation of Social Message Hooks |
|
Tracking of Social Message Views |
|
Magento Community Edition |
|
D3.js Data Manipulation Framework |
|
jQuery UI Framework |
|
Foundation Framework by ZURB |
|
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 | |
User Acceptance Test |
Deployment
- Staging & Development Environment: deployed on GoDaddy server
- Database: Magento EAV database structure
- Web Links:
User Acceptance Test (UAT)
Objectives
Test Details & OutcomeUser 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
|
Reflections
Team Reflection
Lessons Learnt!
|
Individual Reflections
Sponsor Comments
"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."
|