Difference between revisions of "SColutions Final"
(15 intermediate revisions by 2 users not shown) | |||
Line 48: | Line 48: | ||
<li>[[SColutions_Diagrams|Diagrams]]</li> | <li>[[SColutions_Diagrams|Diagrams]]</li> | ||
<li>[[SColutions_Midterm|Midterm Wiki]]</li> | <li>[[SColutions_Midterm|Midterm Wiki]]</li> | ||
+ | <li>[[SColutions_Final|Finals Wiki]]</li> | ||
</ul> | </ul> | ||
</td> | </td> | ||
Line 104: | Line 105: | ||
*Presented MyHubStore Project at ITMA 2014! --<b>7 Nov 2014 </b> <br> | *Presented MyHubStore Project at ITMA 2014! --<b>7 Nov 2014 </b> <br> | ||
− | *As of 7th Oct,2014, we have acquired <b>75 Registered Users</b> and have helped them create <b>79 Stores</b>! (Some Merchants Were Upgraded To Premium Store Owners For Our Beta) Additionally, within the span of 14 weeks from our beta release, we have approximately <b>600 Items</b> Listed On MyHubStore.com and we have already had <b> | + | *As of 7th Oct,2014, we have acquired <b>75 Registered Users</b> and have helped them create <b>79 Stores</b>! (Some Merchants Were Upgraded To Premium Store Owners For Our Beta) Additionally, within the span of 14 weeks from our beta release, we have approximately <b>600 Items</b> Listed On MyHubStore.com and we have already had <b>4 successful item transactions</b>. This is a remarkable accomplishment considering that this idea went from concept to reality within the span of 14 weeks! |
==<font face="Bell MT" color="#AF4200"><b>Project Management</b></font>== | ==<font face="Bell MT" color="#AF4200"><b>Project Management</b></font>== | ||
Line 183: | Line 184: | ||
|width="100" align="center"| Kenneth & Melvin | |width="100" align="center"| Kenneth & Melvin | ||
|width="500" align="center"| [[File:SCTrack_Item_Views_&_Comments.PNG|500px]] | |width="500" align="center"| [[File:SCTrack_Item_Views_&_Comments.PNG|500px]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width="300"| <b>Administrator Analytics</b><br>Make visual representation of information provided by Google Analytics and the social networks API | |width="300"| <b>Administrator Analytics</b><br>Make visual representation of information provided by Google Analytics and the social networks API | ||
Line 194: | Line 189: | ||
|width="100" align="center"| 1 | |width="100" align="center"| 1 | ||
|width="100" align="center"| Yunru & Kenneth | |width="100" align="center"| Yunru & Kenneth | ||
− | |width="500" align="center"| [[File:Scolutions | + | |width="500" align="center"| [[File:Scolutions analytics page.png|500px]] |
|- | |- | ||
|} | |} | ||
Line 276: | Line 271: | ||
|width="100" align="center"| 1 | |width="100" align="center"| 1 | ||
|width="100" align="center"| Melvin & Kenneth | |width="100" align="center"| Melvin & Kenneth | ||
− | |width="500" align="center"| | + | |width="500" align="center"| [[File:Scolutions store search.png|500px]] |
|- | |- | ||
|width="300"|<b>Payment Module</b><br> | |width="300"|<b>Payment Module</b><br> | ||
Line 294: | Line 289: | ||
|- | |- | ||
!width="300"|'''Task/function/features, etc''' | !width="300"|'''Task/function/features, etc''' | ||
− | !width=" | + | !width="100" align="center"|'''Status''' |
− | !width=" | + | !width="100" align="center"|'''Confident Level(0-1)''' |
− | !width=" | + | !width="100" align="center"|'''Comment''' |
− | !width=" | + | !width="500" align="center"|'''UI Link (If Available)''' |
|- | |- | ||
|width="300"|<b>Messaging Function</b><br> | |width="300"|<b>Messaging Function</b><br> | ||
− | *Users can message store owners directly by messaging directly in MyHubStore (Email | + | *Users can message store owners directly by messaging directly in MyHubStore (An Email Can Be Decided Whether To Be Sent Based On The Sender) |
− | |width=" | + | |width="100"| Deployed and tested 100% |
− | |width=" | + | |width="100" align="center"| 1 |
− | |width=" | + | |width="100" align="center"| Kenneth & Yunru |
− | |width=" | + | |width="500" align="center"| [[File:Scolutions messaging.png|500px]] |
|- | |- | ||
− | |width="300"|<b>Admin | + | |width="300"|<b>Admin Module (2nd Stage)</b><br> |
− | * | + | *Our Admin Module Second Stage Focuses On Allowing Our Sponsor Control Most Of The Entire Website Without The Need For Technical Assistance |
− | |width=" | + | |width="100"| Deployed and tested 100% |
− | |width=" | + | |width="100" align="center"| 1 |
− | |width=" | + | |width="100" align="center"| Ying Neng & Melvin |
− | |width=" | + | |width="500" align="center"| [[File:Scolutions notification page.png|500px]] <br> [[File:Scolutions store accounts page.png|500px]] <br> [[File:Scolutions user accounts management.JPG|500px]] <br> [[File:Scolutions website and content management page.png|500px]] |
|- | |- | ||
|} | |} | ||
Line 319: | Line 314: | ||
|- | |- | ||
!width="300"|'''Task/function/features, etc''' | !width="300"|'''Task/function/features, etc''' | ||
− | !width=" | + | !width="100" align="center"|'''Status''' |
− | !width=" | + | !width="100" align="center"|'''Confident Level(0-1)''' |
− | !width=" | + | !width="100" align="center"|'''Comment''' |
− | !width=" | + | !width="500" align="center"|'''Snapshots (If Available)''' |
|- | |- | ||
|width="300"|<b>Storewide Discounts</b><br> | |width="300"|<b>Storewide Discounts</b><br> | ||
*Store Owners Are Able To Give Store Wide Discounts To Users. Owners are also able to edit or create discounts for specific items | *Store Owners Are Able To Give Store Wide Discounts To Users. Owners are also able to edit or create discounts for specific items | ||
− | |width=" | + | |width="100"| Deployed and tested 100% |
− | |width=" | + | |width="100" align="center"| 1 |
− | |width=" | + | |width="100" align="center"| Kenneth & Yunru |
− | |width=" | + | |width="500" align="center"| [[File:Scolutions store discount.png|500px]] |
|- | |- | ||
|width="300"|<b>Store Owners PayPal Merchant Payments</b><br> | |width="300"|<b>Store Owners PayPal Merchant Payments</b><br> | ||
*Store Owners Are Able To Quickly Input Their PayPal Merchants And All Item Sales Are Credited To It Immediately On User Purchase | *Store Owners Are Able To Quickly Input Their PayPal Merchants And All Item Sales Are Credited To It Immediately On User Purchase | ||
− | |width=" | + | |width="100"| Deployed and tested 100% |
− | |width=" | + | |width="100" align="center"| 1 |
− | |width=" | + | |width="100" align="center"| Ying Neng & Melvin |
− | |width=" | + | |width="500" align="center"| [[File:Scolutions item paypal.png|500px]] |
|- | |- | ||
|} | |} | ||
Line 343: | Line 338: | ||
====Schedule Metric==== | ====Schedule Metric==== | ||
− | Full Excel Tracking of our Schedule Metrics Can Be Found [[Media: | + | Full Excel Tracking of our Schedule Metrics Can Be Found [[Media:SC_Schedule_MetricsFinal.xlsx| Here << Click To Download]] <br/><br/><br/> |
− | [[Image: | + | [[Image:Scolutions schedule metrics.png|750px]]<br/><br/> |
<u>'''Iteration 8'''</u> | <u>'''Iteration 8'''</u> | ||
*(Twitter Integration) completed on schedule | *(Twitter Integration) completed on schedule | ||
Line 360: | Line 355: | ||
<u>'''Iteration 11'''</u> | <u>'''Iteration 11'''</u> | ||
*(Administrator and Admin Analytics Function) | *(Administrator and Admin Analytics Function) | ||
− | * | + | *All functionalities to be completed for this iteration is on schedule<br/><br/> |
+ | <u>'''Iteration 12'''</u> | ||
+ | *1. Messaging Function, Admin Module (2nd Stage), UAT 3 (A/B Testing) | ||
+ | *All functional implementation is done on schedule, A/B Testing is also finished on time. Results are already consolidated and available under quality assurance.<br/><br/> | ||
====Bug Metric==== | ====Bug Metric==== | ||
− | Full Excel Tracking of our Bug Metrics Can Be Found [[Media: | + | Full Excel Tracking of our Bug Metrics Can Be Found [[Media:Scolutions_Bug_Metrics_LogFinal.xlsx|Here << Click To Download]]<br><br> |
'''Bug Count and Bug Metrics'''<br> | '''Bug Count and Bug Metrics'''<br> | ||
− | [[Image: | + | [[Image:Scolutions bug metrics.png|550px]] |
− | [[Image: | + | [[Image:Scolutions bug metrics2.png|550px]]<br/><br/> |
<u>'''Insights and takeaways'''</u> | <u>'''Insights and takeaways'''</u> | ||
*Large spike in bugs seen in Iteration 8 were due to fixing previous iteration bugs. This include display bugs and changes which sponsor requested for | *Large spike in bugs seen in Iteration 8 were due to fixing previous iteration bugs. This include display bugs and changes which sponsor requested for | ||
Line 372: | Line 370: | ||
*Our developers are fast for interation9 tasks and are familiar with the technologies involved, thus no. of bugs found for this iteration is quite low | *Our developers are fast for interation9 tasks and are familiar with the technologies involved, thus no. of bugs found for this iteration is quite low | ||
*There is an increase in number of bugs for iteration10 due to the completion of gathering UAT as well as discussion with clients. | *There is an increase in number of bugs for iteration10 due to the completion of gathering UAT as well as discussion with clients. | ||
+ | *We witnessed an increased no. of bugs for iteration12 Due to our final UAT and also because this is the last iteration whereby all technical implementation is finishing and being wrapped up and finalized. | ||
====Current Risk==== | ====Current Risk==== | ||
Line 413: | Line 412: | ||
[[File:Scolutions tech complexity 2.png|950px]] | [[File:Scolutions tech complexity 2.png|950px]] | ||
<br> | <br> | ||
− | |||
− | |||
==<font face="Bell MT" color="#AF4200"><b>Quality Assurance</b></font>== | ==<font face="Bell MT" color="#AF4200"><b>Quality Assurance</b></font>== | ||
− | <big> | + | <br><b>User Acceptance Testing 1</b><br> |
+ | <big>UAT 1 was conducted on all SMU Students We had '''10 participants'''. from different faculties. </big><br/><br/> | ||
Using personal laptop, we asked the participants (users) to: | Using personal laptop, we asked the participants (users) to: | ||
#Create a MyHubStore account<br/> | #Create a MyHubStore account<br/> | ||
Line 427: | Line 425: | ||
#Upload an item onto store and main store page<br/> | #Upload an item onto store and main store page<br/> | ||
− | '''Summary of | + | '''Summary of UAT 1''' |
*By conducting our UAT which aim to test above tasks, we were able to generated good insights of what people like and dislike about our projects. Our 10 participants were all very supportive and helpful and most of them were able to provide genuine and useful feedbacks. Our team has consolidated the results and did some necessary analysis for this UAT and reflected on how we can further improve our product. | *By conducting our UAT which aim to test above tasks, we were able to generated good insights of what people like and dislike about our projects. Our 10 participants were all very supportive and helpful and most of them were able to provide genuine and useful feedbacks. Our team has consolidated the results and did some necessary analysis for this UAT and reflected on how we can further improve our product. | ||
+ | To see full version documentation of UAT, click [[is480:Scolutions_Quality_Assurance| here]] :) <br/> | ||
+ | <br><br> | ||
+ | |||
+ | <br><b>User Acceptance Testing 2</b><br> | ||
+ | <big>UAT 2 was more targetted at getting feedback from our vendors. Hence we approached our two largest store owners on MyHubStore, SapiX and SuperGurl Blogshop, to find out more about their experience in using MyHubStore as a platform to connect and sell to their customers. The table shows a summarization of our key findings.<br/> | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! !! SapiX !! SuperGurl Blogshop | ||
+ | |- | ||
+ | | Purpose of Having E-Commerce Store | ||
+ | || • Quicker and More Efficient Sales | ||
+ | • Reach out to greater pool of customers | ||
+ | || • Greater online visibility/presence | ||
+ | • Leverage on e-commerce to boost sales | ||
+ | • Low overhead i.e. Rental | ||
+ | |- | ||
+ | | What do you like about MyHubStore | ||
+ | || • Less labour-intensive and more effiicient to handle the demands faced when dealing with launching sales or promoting items | ||
+ | • Messaging function helps to address buyers’ enquiries to build assurance and trust when buying a product | ||
+ | |||
+ | || • Simple and convenient to upload items with all the designated fields | ||
+ | • The designated fields are sufficient to promote a product | ||
+ | • Able to further leverage on popular social media platforms to reach out to a greater pool of customers (e.g Sharing of items via Facebook, Twitter) | ||
+ | • Messaging function helps to address buyers’ enquiries to build assurance and trust when buying a product which will translate to more sales | ||
+ | |- | ||
+ | | Areas To Improve On | ||
+ | || • Auto-Publish my items | ||
+ | • 1 photo per item | ||
+ | • Auto-set category field | ||
+ | • Tutorial/Help page | ||
+ | • Ratings/Points system | ||
+ | || • Auto-publish items onto main store to save time | ||
+ | • Hover-on pop-up explanation to make the dashboard more intuitive for non-tech savy users to navigate around the website | ||
+ | |- | ||
+ | |} | ||
+ | <br/> | ||
+ | |||
+ | '''Summary of UAT 2''' | ||
+ | *By conducting our UAT on our vendors, we were able to have better understanding on how store owners interact with the website. Progressively, we will make changes as suggested by our vendors (After discussing with our supervisor and sponsor). | ||
To see full version documentation of UAT, click [[is480:Scolutions_Quality_Assurance| here]] :) <br/> | To see full version documentation of UAT, click [[is480:Scolutions_Quality_Assurance| here]] :) <br/> | ||
Line 452: | Line 490: | ||
| || System Architecture || [[SColutions_System_Architecture|System Architecture]] | | || System Architecture || [[SColutions_System_Architecture|System Architecture]] | ||
|- | |- | ||
− | | Quality Assurance || | + | | Quality Assurance || UAT 1 || [[Scolutions_Quality_Assurance| UAT1]] |
+ | |- | ||
+ | | Quality Assurance || UAT 2 || [[Scolutions_Quality_Assurance| UAT2]] | ||
|} | |} | ||
Latest revision as of 16:07, 22 November 2014
Overview | Proj Mgmt | Documentation | Team Resource |
---|---|---|---|
Contents
Project Progress Status Summary
As a team, we have completed
Our project has 14 iterations in total. We are in the midst of our 14th iteration(10Nov - 23Nov). Link to MyHubStore > http://www.myhubstore.com
- To date,we have completed 100% (27 out of 27 tasks) of our project.
- Two user testings have been conducted.
- Note: the very first user testing before acceptance could have been improved by having targetted goals as per advised during our acceptance presentation
- UAT1 is done following required procedures after acceptance at the end of iteration9
- UAT2 is done following required procedures after acceptance at the end of iteration12
- Five Functionality Testing with sponsor
- 10 progress update meetings with sponsor
Functions Completed:
- Login & Logout Functionality
- Store Management Functionality
- Multiple Store Management Functionality
- Store Location Functionality
- Item Management
- Main HubStore Functionality
- Facebook Functionality
- Search Functionality
- Twitter Functionality
- Google+ Functionality
- Payment Function
- Administrator Administration Function
- Administrator Analytics Function
- Messaging Function
- Commission Module
So far, we have completed all tasks planned on schedule is in the mist of preparing for final presentation. We have also done our UAT2 Testing (With a Vendor and a Blogshop Owner) at the end of iteration 12. Details can be found under quality assurance
Our team has stayed on track for all the iterations. Project management wise we have steadily improved over each iteration (Schedule Metrics Wise). We did face some challenges while discussing design related issues with our sponsor, however, we overcome this issue and have bridged an efficient way of communicating to him and he has been very supportive and has given us great flexibility in deciding the technology we use etc. An example to raise is the change in payment technology from PayPal to Google Wallet. Key reasons raised for this change is due to the expensive need for an SSL Certificate as well as the unwilling need for a redirect out of MyHubStore to make payment. The team did consider adding PayPal as an additional payment module however taking into consideration the limited amount of time left, the team decided to focus on improving our core functionalities and ensuring that transactions between buyers and sellers are working and up to standard.
Project Highlights
As a team, we have grew and achieved
- MyHubStore Beta Goes LIVE!--20 July 2014
- Twitter Functionality Released! --21 Aug 2014
- Google Plus Functionality Released! --8 Sep 2014
- MyHubStore Payment Module Released! --28 Sep 2014
- MyHubStore Admin Module (With Analytics) Released! --10 Oct 2014
- Admin Function Released! --26 Oct 2014
- Messaging Function Released! --1 Nov 2014
- Presented MyHubStore Project at ITMA 2014! --7 Nov 2014
- As of 7th Oct,2014, we have acquired 75 Registered Users and have helped them create 79 Stores! (Some Merchants Were Upgraded To Premium Store Owners For Our Beta) Additionally, within the span of 14 weeks from our beta release, we have approximately 600 Items Listed On MyHubStore.com and we have already had 4 successful item transactions. This is a remarkable accomplishment considering that this idea went from concept to reality within the span of 14 weeks!
Project Management
Project Schedule:
Schedule Breakdown by iteration
Planned V.S Actual
- Key Change 1: Administrator Module Split Across Iteration 11 and 12
- Primary Reason attributed to sponsor increasing requirements for Administrator Module
- After our last discussion with sponsor, our developer demoed all completed functionalities to him and he added in and specify some requirements and together we've made some changes in direction for our administrative function. Such as we changed from making visual representation of information provided by Facebook Graph API, Google+ API and Twitter API to making the presentation by Google Analytics (which is not easy to implement) and our originally planned social network APIs.
- Key Change 2: Added UAT 3 (Vendor Testing) To Iteration 12
- The Team want to use this experiment to find out user sentiments and potentially enhance content. Goal is to increase conversion rate in platform users
- We believe that seeking our vendor's feedback is necessary for our app because it can help us understand the different user sentiments and reaction towards different UI/interface designs by controlling the rest variables so as to help us choose and refine the better option and eventually and it can potentially boost click through rate and conversion rate.
Project Tasks & Status:
Project scope and completion diagram
Primary
Secondary
Tertiary
Added Functionalities (After Mid Term Feedback From Reviewers)
Project Metrics
Schedule Metric
Full Excel Tracking of our Schedule Metrics Can Be Found Here << Click To Download
Iteration 8
- (Twitter Integration) completed on schedule
Iteration 9
- (Twitter Integration) completed ahead of schedule
- Action:Extra time was put in researching on google payment function
Iteration 10
- (Payment Function) completed a bit behind schedule
- Reason:
- Majority of time spent on Google Wallet and consolidation of UAT & Heuristic Testing results
- Time also spent on preparing and finalizing mid-term related documents
- Action:
- Team meeting was hold to discuss cause of issue
- Re-prioritize our future task and re-estimate required time for each task based on developers' knowledge and research
Iteration 11
- (Administrator and Admin Analytics Function)
- All functionalities to be completed for this iteration is on schedule
Iteration 12
- 1. Messaging Function, Admin Module (2nd Stage), UAT 3 (A/B Testing)
- All functional implementation is done on schedule, A/B Testing is also finished on time. Results are already consolidated and available under quality assurance.
Bug Metric
Full Excel Tracking of our Bug Metrics Can Be Found Here << Click To Download
Bug Count and Bug Metrics
Insights and takeaways
- Large spike in bugs seen in Iteration 8 were due to fixing previous iteration bugs. This include display bugs and changes which sponsor requested for
- Bugs were fixed within Iteration 8 and did not cause any delay to the schedule
- Our developers are fast for interation9 tasks and are familiar with the technologies involved, thus no. of bugs found for this iteration is quite low
- There is an increase in number of bugs for iteration10 due to the completion of gathering UAT as well as discussion with clients.
- We witnessed an increased no. of bugs for iteration12 Due to our final UAT and also because this is the last iteration whereby all technical implementation is finishing and being wrapped up and finalized.
Current Risk
Key Risks | Impact | Likelihood | Mitigating Actions |
---|---|---|---|
Improper Selection of Users For UAT will Result In Inconclusive Results
|
High | High | 1. Define clear goals for the UAT and identify primary target group for MyHubStore
|
Google Wallet May Be Not As Widely Accepted As Other Payment Platforms
|
High | Medium | 1. Considering Conducting A/B Testing of Payment Module using Google Wallet vs PayPal in Iteration 12 2. Track Usage of Google Wallet Going Forward |
Lack of Experience With New APIs May Result In Delays in Project Schedule
|
High | Medium | 1. Progressively track and update schedules to identify iterations which have higher technical complexities |
Technical Complexity
1st Technical Complexity - Leverage On APIs To Improve E-Commerce Experience
2nd Technical Complexity (Google Wallet for Digital Goods With Recurring Billing)
Quality Assurance
User Acceptance Testing 1
UAT 1 was conducted on all SMU Students We had 10 participants. from different faculties.
Using personal laptop, we asked the participants (users) to:
- Create a MyHubStore account
- Search for a Specific Item
- Share an item via any Social Media Website: Facebook/Twitter Store
Using personal laptop, we asked the participants (store owners) to:
- Set up Store
- Upload an item onto store and main store page
Summary of UAT 1
- By conducting our UAT which aim to test above tasks, we were able to generated good insights of what people like and dislike about our projects. Our 10 participants were all very supportive and helpful and most of them were able to provide genuine and useful feedbacks. Our team has consolidated the results and did some necessary analysis for this UAT and reflected on how we can further improve our product.
To see full version documentation of UAT, click here :)
User Acceptance Testing 2
UAT 2 was more targetted at getting feedback from our vendors. Hence we approached our two largest store owners on MyHubStore, SapiX and SuperGurl Blogshop, to find out more about their experience in using MyHubStore as a platform to connect and sell to their customers. The table shows a summarization of our key findings.
SapiX | SuperGurl Blogshop | |
---|---|---|
Purpose of Having E-Commerce Store | • Quicker and More Efficient Sales
• Reach out to greater pool of customers |
• Greater online visibility/presence
• Leverage on e-commerce to boost sales • Low overhead i.e. Rental |
What do you like about MyHubStore | • Less labour-intensive and more effiicient to handle the demands faced when dealing with launching sales or promoting items
• Messaging function helps to address buyers’ enquiries to build assurance and trust when buying a product |
• Simple and convenient to upload items with all the designated fields
• The designated fields are sufficient to promote a product • Able to further leverage on popular social media platforms to reach out to a greater pool of customers (e.g Sharing of items via Facebook, Twitter) • Messaging function helps to address buyers’ enquiries to build assurance and trust when buying a product which will translate to more sales |
Areas To Improve On | • Auto-Publish my items
• 1 photo per item • Auto-set category field • Tutorial/Help page • Ratings/Points system |
• Auto-publish items onto main store to save time
• Hover-on pop-up explanation to make the dashboard more intuitive for non-tech savy users to navigate around the website |
Summary of UAT 2
- By conducting our UAT on our vendors, we were able to have better understanding on how store owners interact with the website. Progressively, we will make changes as suggested by our vendors (After discussing with our supervisor and sponsor).
To see full version documentation of UAT, click here :)
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | Minutes |
Metrics | Metrics | |
Scope and updates | Dashboard upates | Dashboard ,Scope |
Analysis | Use Case | Use case |
Design | Class Diagram | |
ER Diagram | ER Diagram | |
System Architecture | System Architecture | |
Quality Assurance | UAT 1 | UAT1 |
Quality Assurance | UAT 2 | UAT2 |
Deployment
Website: http://www.myhubstore.com
Presentation Material
The Team's Midterm Presentation Can Be Found Here: Mid Term Presentation PDF
Reflection
Team reflection:
SColutions Member | Role | Learning Outcome |
---|---|---|
Hattie Ren | Team Project Manager |
|
Chan Yunru | Usability Analyst |
|
Ng Ying Neng | Lead Tester & Biz. Analyst |
|
Melvin Leong | Lead Developer |
|
Kenneth Liow | UI Developer |
|