SColutions Final
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 6 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
Task/function/features, etc | Status | Confident Level(0-1) | Comment | UI Link (If Available) |
---|---|---|---|---|
Messaging Function
|
Deployed and tested 100% | 1 | Kenneth & Yunru | Deployed and tested 100% |
Admin Analytics (2nd Stage)
|
Deployed and tested 100% | 1 | Ying Neng & Melvin | Deployed and tested 100% |
Added Functionalities (After Mid Term Feedback From Reviewers)
Task/function/features, etc | Status | Confident Level(0-1) | Comment | Snapshots (If Available) |
---|---|---|---|---|
Storewide Discounts
|
Deployed and tested 100% | 1 | Kenneth & Yunru | Deployed and tested 100% |
Store Owners PayPal Merchant Payments
|
Deployed and tested 100% | 1 | Ying Neng & Melvin | Deployed and tested 100% |
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)
- We are currently in the mist of it and all functionalities to be completed for this iteration is on schedule
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.
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)
3rd Technical Complexity (Google Analytics & Social Network Analytics)
Quality Assurance
UT 1 was conducted on ..... We had 10 participants. all of them are SMU students.
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 UAT1
- 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 :)
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 | UT1 | UAT1 |
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 |
|