IS480 Team wiki: 2016T1 Fixxlar Finals Wiki

From IS480
Jump to navigation Jump to search

Fixxir-Home.png   HOME


Fixir-about-icon.png   ABOUT US


Fixir-Overview-icon.png   PROJECT OVERVIEW


Project management-icon.png   PROJECT MANAGEMENT


Fixir-documentation-icon.png   DOCUMENTATION


Project Overview

Project Progress

Current Sprint
Sprint 14
07 Nov to 20 Nov

Our project consists of 15 sprints and we have completed 100% of our project scope.

Project Highlights

Product Deployment
Throughout our project, our reviewers and supervisors have warned us about the risk level in projects. However, with their unconditional help the project team managed to understand risk management better and also the ways to handle it. As a result, the project team is able to fully deploy the customer web app and workshop web app on 31st October, 2016.

Drivers and Workshops have since been using the platforms for their needs.

Project Challenges

Change in Management Team
Major changes in scope as lead developer from Fixir team moved on to a full-time job, where the initial iOS app will not be delivered as promised. This affects our project management as we had to revise some functions of the web application to be used by workshops, in order for us to have the resources to come up with a minimal viable product of a mobile site for the drivers. This had to be done as our web application for the workshops will be redundant if there are no users submitting any quotation requests.

There are various users for the two applications which we have done, namely the drivers, workshop administrators, valet drivers, and of course, the Fixir team who will overlook every request. This was challenging as we had to speak to the different stakeholders and ensure that we were meeting all of their needs on the respective platforms - which complicated the user testing process.

Integration of Various Stakeholders
As our product is not only catered to a single user, it stretches the team as we have to consider the needs and requirements of the various stakeholders. This pose as a challenge as because it becomes very confusing as we run through the entire business process flow. At times when we were not very clear with the process flow, it will affect the experience of the entire product. Therefore the project team is constantly interacting with the stakeholders to find out about their views and thoughts about the entire user experience in order to be able to meet their requirements.

Project Achievements

Despite the drastic change in scope, we managed to overcome the challenges we faced and mitigated our risks accordingly. This is attributed to us adhering to the scrum methodology which we had been using right from the start, to track our progress and ensuring that the functions are completed on time.

Project Management

Project Status

Team Fixxlar has delivered to our sponsor on the functionalities that have been agreed on after the change in scope before Midterms.

Midterm vs Final Scope

The team has successfully delivered to our client the scope that we have agreed upon since Midterms. A few of the features that have been highlighted have been taken out due to the modification of the payment system used as well as the process flow. As planned, we were suppose to implement STRIPE Payment system however more time is still required to verify the Amazon Web Service certificate therefore the team decided to use a workaround by using Paypal instead. During MidTerms, Prof Ben Gan advised us to avoid taking up any additional features by week 12 and 13 therefore there are no addition to the project scope.

Midterm Finals
Fixxlar Project Scope Version6.1.jpeg Project Scope Version7.jpeg

Midterm vs Final Project Schedule

There are no changes to the schedule since Midterms, the team completed the required tasks during the sprints and is taking Sprint 13 and 14 to do UI improvements to enhance user experience. The team has completed 2 major events.

Midterm Finals
Fixxlar Schedule Version6.jpeg Fixxlar Schedule Version7.jpeg

User Testing

The team has also conducted a major User Testing on the 27 October as planned in the schedule to approach our Workshops and Users for testing. For the testing with our Users, our sponsor suggested for us to use the cafe usability testing approach. On 27 October, the project team split into 2 teams for the user testing with the workshops and the users.


The project has also deployed the application for the first time on 19 October to release the product for users to be able to start using it. On 31 October, the project team have completely deployed the application. Both the sponsor and the project have been putting in work to market out to users to try out the application.

Project Metrics

Team Velocity


Since Midterms which happened in Sprint 11, excluding those features that have been removed due to business process changes, all the features developed were accepted by our Sponsor. However there are no stories accepted in Sprint 13 and 14 as these sprints were used for User Interface improvements as well as for debugging.

Sprints Burndown Chart

Sprint burndown chart before the midterms can be seen through our midterm wiki.

S/N Sprint Explanation
1 Sprint 11 Burndown Chart.jpeg During the midterm week, the team was able to complete the features that were required for the first deployment and sponsor is satisfied with the product presented.
2 Fixxlar Sprint 12 Burndown Chart.jpeg During Sprint 12, the team completed the remaining features that were required for the valet part in the Fixir Customer Web App. In this sprint, the project team also stop accepting new features to add in.

On Sprint 13 and 14, both the team and sponsored agreed that more efforts will be spent on ensuring the quality of the product. Therefore during these 2 sprints, the team spent time doing debugging as well as improvements to the application which ultimately affects User Interface as well as User Experience.

Risk Management

This risk happened in Sprint 12 when the team was unable to implement the STRIPE feature due to the delay in the verification of the SSL certificate. We worked with the sponsor team and also approached professor Debin to get help in this matter with the certificate verification. After investigating the problem that we were trying to solve, even though we are done setting up the SSL channel for the payment, the verification would take too long before it can work. Therefore the team managed this risk and sourced for alternative, we came to a common agreement that we will use Paypal for the payment in order to deploy our product on time.

Priority List for Change Management

After moving towards our first deployment, the team created a priority list to handle the change management as there were several requests to do User Interface as well as User Experience changes by our sponsors. With the limited time, this priority list was a basis for our discussions with our sponsor on whether to proceed on with the changes. The Team has completed whatever changes that has been discussed and agreed upon after midterms. The sponsor have gone through the changes and are satisfied with the changes.

Priority List

Technical Complexity

Stripe Payment Complexity

The reason we chose Stripe as our Payment option was that it featured a simplified online payment processing. We are able to use its Checkout feature to quickly integrate the payment module into our website. The Checkout feature was a streamlined, mobile-ready payment feature that was also easy to implement. Furthermore, it ensures that the user’s payment info never touches our server. It utilizes a token provided by Stripe to process a payment request. We simply had to make use of Stripe’s javascript library and create a custom form to process the Checkout function.

Problems Encountered
We had problems in terms of implementing an SSL enabled HTTPS page for our payment to be processed on a secure page. We requested for a SSL certificate for our EC2 Instance. Our client verified his identity with Amazon to get approval for the certificate, and we went ahead and linked the certificate to our EC2 Instance where our web application is deployed on. We made sure to enable the HTTPS Protocol on the Load Balancer and upload our acquired Certificate. Left

However, when we tried to access our web app via HTTPS, we could not troubleshoot the issue where the certificate appears to be self-signed.

Calculation of Time for Pick for Valet Drivers

When drivers request for a valet service, instead of just giving the Valet Driver the customer's appointment time we went further a step by helping to calculate the time that the valet driver needs to pick up the vehicle in order to reach the workshop in time. In order for this to happen, we made use of the Google RESTful API to find out the time required for the valet to bring from the customer's pickup location to the drop-off which in this case is the car workshop. Instead of letting the valet drivers plan themselves on what time to pick up, this method reduces any human error of estimation. The additional advantage is also that it provides accountability towards the customers as well. This helps to facilitate the whole flow as the customers are already prepared for the arrival of the valet driver.

Quality of Project

Project Deliverables

Stage Specification Modules
Project Management Meeting Minutes A compilation of internal, sponsor, and supervisor meeting minutes
Project Schedule Project Schedule
Metrics Project Metrics
Risk Management Risk Management and Mitigation
Requirements Project Scope Project Scope
User Stories User Stories and Product Backlog
Analysis Persona and Scenario Persona & Scenario
Market Research Market Research
Technologies and Diagrams Architectural Design, Use Case Diagram, ER Diagram, Workflow Diagram
Design Prototypes Medium & High Fidelity Prototypes
Testing User Test Plan & Results User Test Plan & Results
Project Handover User Manual File:Fixir Mobile Site User Guide.pdf

File:Fixir Web Application User Guide.pdf

Developer Manual Developer Manual
Style Guide Handed over to client privately
Source Code Handed over to client privately


  • A reduction in time from 8.85 seconds in OpenShit to 2.95 seconds on Amazon Web Services



User Testing 3B

Venue: Various Workshops:
    1. Premier-One Auto Pte Ltd (8 Kim Chuan Terrace)
    2. ACMA Engineering (Pioneer Point, 5 Soon Lee Street, #06-20 Singapore 627607
    3. ZG Motors (8 Kaki Bukit Ave 4, Singapore 415875)
    4. AOTO Pte Ltd (No. 42 Toh Guan Road East #01-78 Enterprise Hub Singapore 608583)
Date: 27 October 2016, Thursday
Time: 11:00am - 7.00pm
Duration: 30~60 minutes
Number of Participant(s): 4~5

UT3B Objectives:

  • Identify possible usability issues with Quotation Request Module, Admin Module, Account Module, Dashboard Module, Scheduling Module, Search Module, Chat Module

User Testing 3A

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955), Various cafés
Date: 27 October 2016, Thursday
Time: 11:00am - 5.00pm
Duration: ~30 minutes
Number of Participant(s): 10

UT3A Objectives:

  • Identify possible usability issues with primary functions of Fixir Customer (Driver) Web Application Module, Chat Module

Improvements based on User Testing 3

User Testing 2C

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)
Date: 4 October 2016 - 5 October 2016, Tuesday - Wednesday
Time: 6:00pm - 8.00pm
Duration: ~30 minutes
Number of Participant(s): 5 (TBC)

UT2C Objectives:

  • To gather feedback on the user interface of web application for Customers
  • Identify possible usability issues with primary functions of Fixir Customer Web Application Module

User Testing 2B

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)
Date: 24 September 2016, Saturday
Time: 10:00am - 3.00pm
Duration: ~30 minutes
Number of Participant(s): 5

UT2B Objectives:

  • To gather feedback on the user interface of Valet Driver’s web application - to be compatible with mobile site too
  • Identify possible usability issues with functions and usability of Valet Module

User Testing 2A

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)
Date: 17 September 2016, Saturday
Time: 12:00pm - 2.00pm
Duration: ~30 minutes
Number of Participant(s): 5 (Fixir administrators), 3 (Workshop administrators)

UT2A Objectives:

  • To gather feedback on the user interface of web application for Fixir Administrator
  • Identify possible usability issues with functions of Admin Module, Quotation Request Module, Search Module, Valet Module
  • Allow workshops to retest UT1, with the improved UI we have done after acceptance

User Testing 1

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955) & Respective Workshops
Date: 6 August 2016, Saturday
Time: 10.00am - 2.00pm
Duration: ~30 minutes
Number of Participant(s): 6

UT1 Objectives:

  • To gather feedback on the user interface of Workshop Administrator’s web application
  • Identify possible usability issues with functions of Account Module, Quotation Request Module, Dashboard Module