HeaderSIS.jpg

IS480 Final wiki: 2016T1 WEGOT

From IS480
Jump to navigation Jump to search
Logo-vertical.png


HOME

ABOUT US PROJECT OVERVIEW PROJECT MANAGEMENT DOCUMENTATION


MAIN WIKI MIDTERM WIKI FINAL WIKI

Documentations


Presentation-slides.png
Video-pitch.png
Deployment-link.png
Past-docs.png








WEGET Progress Summary


Midterm-project-summary.png


Xfactor.png


Project Highlights:


Project-highlights-progress.png


Project-highlights-main.png


Project Challenges:

Challenge Faced Impact Mitigation Plan Outcome

Lack of resources to market mobile application

Without proper marketing, our application would be on the play store with no real users. This makes our entire project pointless as the core of our project's revolves around user to user interactions

Develop and upload marketing plan given the resources we have at the moment

Mitigated: Weget Marketing Plan

Proof-of-concept testing for our mobile application with real users

We have done user testing with simulated users for short periods of time. However, our real users would be using this application in a much more frequently. Hence, our group feel its important to obtain users feedback from a prolonged user testing.

Executing marketing plan in targeted areas that are within our reach. After execution, obtain some of these newly found users to assist us in doing a live testing lasting at least one week.

In-Progress

Team is not supported by sponsor, sponsor was dropped after being uncontactable for more than 2 months

Initially, our sponsor had assured us that he would be obtaining live users for our application. However, halfway through he decided that he wanted to use this as a prototype. We tried reasoning with him but he has been uncontactable since. Without his support our group now has to perform additional tasks of marketing and obtain users with whatever means possible to make our application a success.

Adopting our own business and marketing plan, change focus from profiting to understanding whether current business model works and how to improve based on live feedback.

In-Progress


Project Achievements

Xfactor-targed-vs-achieved.png

Project Management

Project Scope (Plan Vs Actual):

Changes-made-scope.png


Planned-title.png


Scope-4.png


Actual-title.png


Banner-Project Scope.png



You can view WEGET's detailed scope changes here!

Project Schedule (Plan Vs Actual):

Changes-made-schedule.png


Planned-title.png


Schedule-version-4.jpg


Actual-title.png


Banner-schedule.jpg


You can view WEGET's detailed schedule changes here!

Project Metrics:

Bug&task-title.png


Combined-wegot.png


You can view WEGET's detailed metrics here!

Technical Complexity:

Banner-archi--midterms.png


Complexities-title.png


Issue 1.png


Issue 2.png


Issue 3.png



Quality of product

Intermediate Deliverables:

Type Specification Documentations
Project Management Risk, Metrics and Minutes

Risk Management
Task and Bug Metrics
Meeting Minutes

Analysis, Design and Diagrams Market Research,Prototype, Persona, Scenarios, Storyboard, Use Case and Architecture Diagram Market Research and Surveys

Prototype
Persona and Scenarios
Storyboard
Use Case and Architecture Diagram

Testing User Test Plan User Testing 1, Test Plan

User Testing 2, Test Plan
User Testing 3, Test Plan
User Testing 4, Requestor Test Plan
User Testing 4, Fulfiller Test Plan


Quality

Deployment:

WEGET android application can be found on the Play Store, can be downloaded via https://play.google.com/store/apps/details?id=com.weget.fuyan.fyp , or downloaded via the QR Code below

Qrcode.jpeg
  • Our application is compatible with all android devices
  • Testing:

    User Testing User Testing Results

    UAT 1

    User Testing 1, Results

    UAT 2

    User Testing 2, Results

    UAT 3

    User Testing 3, Results

    UAT 4

    User Testing 4, Results


    Future Development:

    Future Development Plan Development Plan Description

    Develop an iOS version (or on other mobile operating systems)

    WEGET is currently only available Android operating systems. However, there are a large group of users whom use other operating systems. Hence, our team aims to extend the number of operating systems that WEGET is available on to expand our user base.

    Change mobile application name to increase SEO

    Currently it is very difficult to increase our SEO as the term “WEGET” is often mistaken by the term “Widget” and results will generally return the top used widgets in the marketplaces. Hence, we would need to rename the application to something unique and relevant with regards to the tools our mobile application provides.

    Improved/different process workflow

    Currently, our process provides more functions that cater to requestors rather than fulfillers. To improve our app for fulfillers, it is also important that we have more functions to support our fulfillers in completing the task as the fulfillers actully investment more compared to the requestors. One idea that our team has agreed on is that fulfillers can post a “Request Offer” which tells other users that they are buying something in a place nearby.

    Replace/propose new payment modes

    Currently, WEGET is only supporting credit card as payment with a service charge for each transaction. Our team suggests the use of a”points-cash” system, where a user needs to make sure that they have “points” in their account before they can use this system to make payment for their transactions. Users will obtain points though credit card/cash payments. This will result in less cost as users would only need to add points once in a while rather than making payment for every transaction. Other modes of payment considered were cash and NFC payments. However, security has to be taken into consideration first before introducing new modes of payment.

    Improved confirmation system for completed transactions

    Currently, WEGET requires both the requestor and fulfiller to confirm the delivery. This is done to protect both parties. However, this confirmation process is inefficient as it requires both users to take action on their phones.

    To tackle this, our team plans to implement QR code verification for users, where the fulfiller is required to scan the qr code sent to the requestor.


    Reflection

    Team Reflection:

    Reflection-2.png
    Reflection-1.png


    Reflection-3.png