Info Topia XOXO Mid Term Presentation Agenda Project

Info. Topia XOXO Mid Term Presentation

Agenda • Project – Team – Market Research – Scope – Tools – Deployment Architecture – Highlight – Progress Summary – Schedule Metric – Bug Metric – Quality of product – Change Management • Demonstration • Team Reflection • Project Management • Q&A – X Factor

The Team 8/10/13 3

The Team Fransisca Xian Ming Lin Bin Project Manager Quality Manager Mobile developer Graphic Designer User X Designer System Analyst Zunhua Zhang Fan Zhao Yao SSI (Lead) Integration Manager Backend Manager Integration Manager Business Analyst Project Manager

The Client

The Project 8/10/13 6

The Project XOXO Mobile App A Browsing & Display, Fashion Sharing and Fashion Searching app Simple Server Interface For administrator to control and manage products and users; analysis on customer behaviour.

For Users XOXO Social Interaction! Teens & young adults would like to share and interact with others on current fashion trends Smart Purchaser User wants to find/purchase similar items of established brand with lower prices

For Merchant XOXO Marketing Your Product Merchants are interested in marketing their newly products on a professional platform Statistics Analysis Merchants are also interested in knowing consumers’ need and want by observing their behavior

Market Research 8/10/13 10

Scope Planning 8/10/13 16

Planned Additional Functions • Send notification Tag item Post history Activity history Share on FB View other’s profile • • • Secondary Functions • • • CRUD categories Trend Analysis Comment Edit Profile Follow Like Product Core Functions • • CRUD product CRUD-B users Extracting attributes Search Simple Server Interface • • • Log in Register Display item& information Search Post picture Take photo Android Mobile App

Additional - Similar items Additional Functions • Tag item - Trend analysis • Post history - Colour • Send • Activity history - Sleeve length notification • Share on FB - Dress length • View other’s profile - Textured Actual Secondary Functions • • • CRUD categories Trend Analysis Comment Edit Profile Follow Like Product Core Functions • • CRUD product CRUD-B users Extracting attributes Search Simple Server Interface • • • Log in Register Display item& information Search Post picture Take photo Android Mobile App

Market Analysis XOXO

Tools 8/10/13 20

Production Tools XOXO

Production Languages

Framework Tools

Production Servers

3 rd Party Tool Google Maps API Facebook API Data Driven Documents

Collaboration Tools

Deployment Architecture 8/10/13 27

SSI: myxoxo. info/xoxo Server running IIS , ASP 4. 5 Android 4. 0 REST Data Exchange Web service M-SQL Server Lat, Long Google Maps Facebook D 3. js

X-Factor 8/10/13 29

X-Factor

X-Factor

X-Factor My location Store location Real Time Location Visibility User will be able to view her current location and the stores that she is interested in to find the items

X-Factor Find this Product Matching Users will be able to get similar items as recommendation Store location Suggest this!!

Technical Complexities 8/10/13 34

Technical Complexity 1

Complexity 2

Complexity 3

Demonstration 8/10/13 38

Project Management 8/10/13 39

Project Highlight 1 The Unexpected Executable not able to search by image Similar item recommendation

Project Highlight 2 The Unexpected Batch upload to name the image Naming based on sleeve. Length_dress. Length_colour_categories

Project Highlight 3 The Unexpected No real users by the client to test UT done in most popular age group which is 19 -23

Project Progress Summary • Completed 95% of our project • Conducted 1 user validation survey • Conducted 5 Usability Testing – 2 SSI – 3 Mobile • 7 no of meetings with client

Completed Functions- SSI • • CRUD users CRUD product categories CRUD product items Search item Extract product attributes Trend analysis Send notifications to users

Completed Functions- Mobile • Facebook/Normal Login • View items by: – Recent – Most popular – Following • Search by: – – • Keyword Attributes Social Interaction – – Comment Like Share on Facebook Follow other users • • • Real time store location Recommendation similar items Receive notification – – From Admin From user activities • View user activities history • Update profile

Planned vs Actual Sprint Task Planned Actual Comment 1 Display item by most recent 24 June 2013 9 July 2013 Unclear about project scope, hence more time for backlog discussion 3 Login via FB 23 July 2013 20 August 2013 Moved to sprint 5 due to preparation of acceptance taking longer than usual. More debugging and UI improvement 6 SSI trend analysis 3 s 7 Septem ber 2013 Unfamiliar with the algorithm and more time dedicated to it. Moreover, client changing requirement about the trend analysis.

Schedule Metric Sprint

Burn Down Chart 700 600 Points 500 400 300 200 100 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Planned Remaining 642 580 475 369 292 160 75 0 0 Actual Remaining 586 485 377 300 160 115 15

Percentage Planned vs Completion Rate Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Planned Completion Rate 9, 66% 26, 01% 42, 07% 53, 43% 73, 64% 88, 34% 100, 00% Actual Completion Rate 8, 72% 24, 45% 40, 82% 52, 15% 73, 64% 82, 12% 97, 71% 100, 00% Sprint

Bug Metric 8/10/13 50

Bug Classification Points Description Low Impact [1] Errors with aesthetic. Feature can still work. Medium Impact [5] Non-critical functionalities errors. The whole application still runs High Impact [10] The whole application is down or crashes when launched. Team has to stop and fix the bugs.

Bug Classification End of each sprint Points Action Plan Points =<20 Hours needed: 1 -2 hours Manpower: 1 No need to inform PM regarding bugs, update bug report accordingly and solve them 20 <Points <40 Hours needed: 3 -7 hours Manpower: 2 -3 Slight delay to the progress. PM to schedule debugging session to solve bugs and review if tasks will be delayed for next iteration. Points =>40 Hours needed: >7 hours Manpower: 2 -3 Critical delay to the progress. Team to discuss and review project scope or reschedule to complete the tasks required.

Bug Tracking Value (points) Bug Metric 30 25 20 15 10 5 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 High Bug Medium Bug Low Bug

Risk Management 8/10/13 54

Risk Metric Probability Impact Highly Likely Less Likely Catastrophic 6 [High] 5 [High] 4 [Medium] Critical 5 [High] 4 [Medium] 3 [Medium] Marginal 4 [Medium] 3 [Medium] 2 [Low] Negligible 3 [Medium] 2 [Low] 1 [Low]

Risk Metric Classification Impact Description Catastrophic Will stop the progress of the project Critical Will definitely impact the progress of the project Marginal Might impact the progress of the project Negligible Would not impact the progress of the project

Risk Metric Probability Description Highly Likely You wouldn’t be surprised if this happens Likely Just as likely to happen as not Less Likely You would be surprised if this happens

Risk Metric Value Action Plan 6 Immediate emergency meeting to activate mitigation plan 5 All members to handle risk with the help of mitigation plan. If risks not eliminated, schedule meeting within 1 day to discuss alternative 4 2 -3 members to handle risk with the help of mitigation plan. If risks not eliminated, schedule meeting within 2 -3 day to discuss alternative 3 Max of 2 members to handle risk using the mitigation plan. 1 -2 1 member to handle risk using the mitigation plan.

Risk and Mitigation 1 Technical Risk (Risk Level 5) Issue Elaboration Impact Mitigation Speed & Network 1. Real time updates 2. High stress on servers to push data 3. Client network dependency Lower response time, lower user experience 1. Keep codes lightweight 2. Only essential data to the server to minimize redundancy

Risk and Mitigation 2 Data Collection Risk (Risk Level 5) Issue Elaboration Impact Mitigation Data collection Small time frame to collect meaningful data Minimum data used for trend analysis and product items 1. Clients support for items database 2. Collection during UAT

Risk and Mitigation 3 Viability Risk (Risk Level 5) Issue Elaboration Impact Mitigation Executable dependency 1. Unfamiliar with executable 2. Compatibility with current framework and DB 3. Executable given in August 1. FYP may be irrelevant. 2. Delaying whole project 1. Pushing for earlier executable 2. More flexible DB design

Quality of Product 8/10/13 62

User Testing Simple Server Interface (SSI) Android Mobile Application #1: 24 September 2013 #1: 17 September 2013 #2: 1 October 2013 #2: 24 September 2013 #3: 28 October 2013 #3: 1 October 2013 #4: 28 October 2013

UT 1 - Mobile Demographics • 8 respondents • Age: 20 -24 years old • Spend >2 hours on social media daily

UT 1 - Mobile Findings • Difficult to understand the icon • Little information on social interaction on main page • Followed users page not available • Item posting date not intuitive • Slow response time

UT 1 - Mobile Follow up actions • Difficult to understand the icon ü Add in words to explain the icon • Little information on social interaction on main page ü Add number of comments/like/share • Followed users page not available ü Add in the page for followed users postings • Item posting date not intuitive ü Change from yyyy/mm/dd to “ 1 day ago”. . ” 1 week ago”

UT 1 - SSI Demographics • 6 respondents • Age: 20 -24 years old

UT 1 - SSI Findings • Difficult to find product categories • Unintuitive icons for user management • Product items attributes difficult to understand

UT 1 - SSI Follow up actions • Difficult to find product categories ü Separate the product categories tab • Unintuitive icons for user management ü Mouse over for short explanation • Product items attributes difficult to understand ü Add in title for the relevant attributes

UT 2 - Mobile Demographics • 8 respondents • Age: 19 -24 years old • Mostly spend 1 -2 hours on social media daily

UT 2 - Mobile Findings • User comment not accurate • Unaware of carousell feature of similar items • Some photos are unable to be loaded • Unsure of the exact shops in map

UT 2 - Mobile Follow up actions • User comment not accurate ü Ensure correct photos and username displayed • Unaware of carousell feature of similar items ü Right left arrows to show items • Some photos are unable to be loaded ü Ensures image path are corrected • Unsure of the exact shops in map ü Clickable icon to display store name

UT 2 - SSI Demographics • 4 respondents • Age: 25 -26 years old

UT 2 - SSI Findings • Need statistics shown for each item • Need time duration to be changed for trend analysis • Show the number of views of each item

UT 2 - SSI Follow up actions • Need statistics shown for each item üClick item to show the individual statistics • Need time duration to be changed for trend analysis üInclude changeable time frame and date • Show the number of views of each item üChange DB structure to fit requirement

UT 3 – Mobile (Client) Demographics • 5 respondents • Age: 23 -26 years old • Mostly spend 1 -2 hours on social media daily

UT 3 – Mobile (Client) Findings • Changing username will create login problems • Tedious to fill in all info to upload • Not able to rotate picture • Confusion for share as user not login to FB

UT 3 – Mobile (Client) Follow up actions • Changing username will create login problems ü Login using email instead • Tedious to fill in all info to upload ü Make description not mandatory • Not able to rotate picture – Ability to rotate • Confusion for share as user not login to FB – Hide the FB share if not login using FB

UI changes- SSI

UI changes- Mobile Profile Page

UI changes- Mobile Most Recent Page

Change Management 8/10/13 82

Change Management Discussion with client Team translates ideas to technical details Introduce additional feature metric Discuss additional values Team does feasibility studies Describe feature in detail Set priority level Follow up with client Approval/Disapprov al from client Schedule for development

Additional Features Feature Description Function Feasibility Value added Similar items recommendation - Listing similar items - Clickable to the real item • • • Develop DB structure for backend system Running executable for each item Retrieving the items based on attributes Develop UI similar items Design and implement web service to retrieve similar items • Integrates quotes web services into mobile app to display similar quotes • Users can get recommendation • Other merchant ability to promote items Trend Analysis of the attributes - Dress Length - Sleeve Length - Textured - Colour • • Develop DB structure to fit the attributes • Merchant can get Running executable for each item better views of trend Retrieving the attributes for particular trend Plotting to the graph

Team Reflections 8/10/13 85

Team reflection There a lot of uncertainty in life, including the requirements of our project and scope in our FYP. Until now, we are still improving our business and technical appeal from our client and users. Although we are trying to accommodate all requests, as a team we learnt on how to prioritize and manage expectations accordingly.

Learning Outcome I have learnt better project management in terms of managing expectations from various stakeholders. I am looking forward to ensure the quality of the app is in high quality. Great technology such as Google Maps API, JQuery, CSS have high learning curve which I have manage to hurdle for mobile apps. I am looking forward to utilize the latest technology for our FYP.

Learning Outcome I learnt the importance of icon and colour positioning in mobile application that will increase the usability of our apps. Looking forward to utilize the best practice in the future I learnt on how to integrate and add value of the client’s executable. Managing a more robust backend system will be next.

Learning Outcome I learnt the importance of having flexible frameworks to ensure that any change requests can be processed more easily. I hope to contribute more in creating a more robust backend system. I developed my skills in presenting project documentations to aid the team performance and efficiency. I hope to conduct better UT to understand valuable user feedback.

Q&A 8/10/13 90