Difference between revisions of "IS480 Team wiki: 2012T1 Shopaholic Final Wiki"
Scchew.2010 (talk | contribs) |
Mei.zou.2010 (talk | contribs) |
||
Line 446: | Line 446: | ||
! width= "300" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Testing Details</font> | ! width= "300" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Testing Details</font> | ||
! width= "400" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Results</font> | ! width= "400" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Results</font> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width= 120 style="background: #ffffff; border: 1px solid black; vertical-align: text-top;"|<font color="#474747">User Test 3 | |width= 120 style="background: #ffffff; border: 1px solid black; vertical-align: text-top;"|<font color="#474747">User Test 3 | ||
Line 594: | Line 488: | ||
*Each participant bought around 2~5 items in 5~10 chosen item categories | *Each participant bought around 2~5 items in 5~10 chosen item categories | ||
</font> | </font> | ||
− | |||
|width= 120 style="background: #ffffff; border: 1px solid black; vertical-align: text-top; padding: 10px;"|<font color="#474747"></font> | |width= 120 style="background: #ffffff; border: 1px solid black; vertical-align: text-top; padding: 10px;"|<font color="#474747"></font> | ||
|} | |} |
Revision as of 13:58, 3 December 2012
Our Team | Project Overview | Project Management | Development | Learning Outcome | Documentation |
| | | | Roles & Responsibilities | | | Mid Term Wiki | | | End Term Wiki | | |
Contents
Project Progress Summary
To view our Mid-Term Presentation Slides: Click Here!
To view our Product, head down to [coming to you soon!]
Progress since mid-term
- Spree Management
- Payment Verification
- Credit Management System
- Add Credut
- Remove Credit
- Adjust Credit
- Social Integration
- Login Through Facebook
- Sharing of 'Tagged' Items on Facebook
- Embed Links for Advertising Sprees
Project Highlights
After seeking advice from our mentor, we made strategic changes crucial for the success of the launch of our portal.
There was a shift in focus in the direction of our project:
- We will not handle credits on launch
- Focus on getting core function out first, which is our minimum viable product (MVP)
- Priority is on gaining organic traffic through social media sharing
Project Challenges
No Framework to Follow
Currently, there is not defined framework in the Spree industry.
In order to redefine the spree buying experience, we have to define our own framework that is intuitive for users.
No Client to Give Direction
As we do not have a client to give us direction in our devleopment, we had to make these crucial decisions.
Through user test, we get our feedbacks from real users, which shapes our development.
Essentially, our portal is designed by users, for users.
Complex Logic involve in Spree Management
Handling Sprees is not as easy as it seems to be.
Complex calculation pertaining to adjustments to credit is involved:
- Top-Ups
- Discounts
- Refunds
The complexity can be seen here >>
Our backend logic had to be powerful enough to handle the calcuation, to make managing Sprees easy for Spree Organizers.
Project Achievements
Tag & Bag Plugins [X-Factor]
We were successfully able to create a framework which allowed us to adopt a new merchant site confidently within 24 hours.
Spree Management Tools
We were able to develop our system to carry out the complex calculations for adjustments for both:
- Line Items
- Each Individual Orders
Project Management
Project Schedule (Plan Vs Actual)
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts. After meeting with our mentor, we adjusted our schedule due to the following reasons:
- Ensure Minimum Viable Product(MVP) is working perfectly for launch. The fuctions are:
- 'Tag & Bag' Plugin
- Spree Management Tools for Spree Organizer
- Smooth Checkout Process for Spree Participants
- Push for Social Element to be up for Launch to gain organic traffic to Site.
- Shelf ESCROW Service till later. Get users to use portal, and gain trust from users first.
To view Detailed Schedule from after mid-term! : Click Here!
To view Plan VS Actual Schedule :
Click Here!
Project Status
Project Progress
Task/ Functionality | Status (%) | Confident Level | Remarks |
---|---|---|---|
Credit Management: | |||
|
100% | 1 | Nil |
|
100% | 1 | Nil |
|
100% | 1 | Nil |
|
100% | 1 | Nil |
User Management: | |||
|
0% | 1 | Drop Functionality - for FYP, but will be developed for future development |
Spree Management: | |||
|
100% | 1 | Nil |
|
100% | 1 | Nil |
Social Integration | |||
|
100% | 1 | Nil |
|
100% | 1 | Nil |
|
100% | 1 | Nil |
Backend Admin Functions | |||
|
100% | 1 | Nil |
Tag and Bag Framework (Plugin) | |||
|
100% | 1 | Nil |
Backend Issues | |||
|
100% | 1 | Nil |
Schedule Metric
Iteration | Planned Start Date (PSD) |
Planned End Date (PED) |
Planned Duration(PD): (PED)-(PSD) |
Actual Start Date (ASD) |
Actual End Date (AED) |
Actual Duration(AD): (AED)-(ASD) |
Duration Difference: (AD)-(PD) |
Performance Index |
Progress Remarks |
---|---|---|---|---|---|---|---|---|---|
6. | 15 Oct 2012 | 2 Nov 2012 | 19 days | 15 Oct 2012 | 3 Nov 2012 | 20 days | 1 day | 1.05 | Used 1 Buffered day |
7. | 5 Nov 2012 | 16 Nov 2012 | 12 days | 5 Nov 2012 | 17 Nov 2012 | 13 days | 1 day | 1.05 | Used 1 Buffered day |
8. | 18 Nov 2012 | 29 Nov 2012 | 12 days | 18 Nov 2012 | 29 Nov 2012 | 12 days | - | 1 | Nil |
Bug Metric
Bug Count by Complexity | |||||
---|---|---|---|---|---|
Iteration | Minor | Normal | Major | Total Bug Count | Total Bug Points |
6 | 15 | 6 | 0 | 21 | 45 |
7 | 3 | 2 | 0 | 5 | 13 |
8 | 19 | 5 | 0 | 24 | 44 |
Project Risks
Issues we faced during since Mid Terms
Risk | Likelihood | Impact | Mitigation Strategies |
---|---|---|---|
Project Management Risk | |||
|
Medium | High |
|
External Risk | |||
|
Medium | Low |
|
Quality of Product
The robustness of our Plugin is illustrated here: Click Here!
The flexibility of our system to handle payment adjustments for top-ups, refunds, discounts for both line items and individual orders is illustrated here: Click Here!
Overall quality of portal and Plugin is determined through constant user testing.
Our group have been constantly testing with our own test cases and getting real users to test the functions.
This is done so that we are able to get the best outcome to improve the overall user's experience.
Technical Complexity
For Complexities of our "Tag & Bag" Plugin Click Here
For Complexities of our Payment Adjustments Click Here
Problem Faced | How we Overcome |
---|---|
|
|
|
|
User Testing
S/No. | Testing Details | Results |
---|---|---|
User Test 3
16 Nov 2012 |
Objective:
Methods:
Participants:
Environment:
Summary
|
For details on our user tests conducted, refer the the following links for more details:
Final Deliverables
Stage | Specification | Modules | |
---|---|---|---|
Project Management | Meeting Minutes | Team Meeting Minutes | |
Supervisor Minutes | |||
Schedule | Detailed Schedule | ||
Metrics | Schedule Metric | ||
Bug Metric | |||
Screenshots | Video |
Prototype Video | |
Plugin Video | |||
Design | Domain Diagram | Domain Diagram | |
Testing |
User Testing 1 | User Test 1 | |
User Testing 2 | User Test 2 | ||
User Testing 3 | User Test 3 | ||
User Testing 4 | User Test 4 | ||
Analysis |
Our Choosen Path | Our Chosen Path | |
Use Case | Use Cases | ||
Poster Day |
Poster | Poster | |
Pitch | Pitch |
Reflection
Team Reflection
We started this project with the intention of starting our own business at the end of the semester.
Throughout these few months, we picked up many valuable tips on how to conduct our user test to get valuable feedback we need in order to make our portal intuitive for users.
Also, our Mentor shared his experience with us, and gave us really useful advice on how to launch our portal.
With all the guidance we received, we really hope that the launch of D2T9 would be successful!
Individual Reflection
Jasmine Chew | Zou Mei | Lau Shu Neng |
---|---|---|
Project Manager | Secretary | Business Development Executive |
It was tough trying to balance the schedule, and new ideas that pop out along the way. |
Not having a mentor was rather tough in our decision making process. |
Having experience in conducting and participating in Sprees gave me a good advantage in knowing the problem domain well. |
Ryan Lim Wen Rong | Ong Zhen Guang | Yong Qian Hwee |
---|---|---|
Developer | Developer | UX Director |
Due to lack of experience in Spree, it was difficult to fully understand the needs of the spree organizer and spree participants. |
As much as we hope to ease the workload of spree organizers and spree participants as much as possible, we are faced with legal limitations that we have to adhere to. |
With help from our supervisor, and much research, i have learnt alot on the importance of designing the site to be easily usable by people. |