Difference between revisions of "IS480 Team wiki: 2016T1 Fixxlar Midterm Wiki"
Line 52: | Line 52: | ||
<h2><div style="background:#E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; border-left: #F5F560 solid 32px; font-size: 16px"><font face="Calibri" color="#ffffff"><center><i> Project Management </i></center></font></div></h2> | <h2><div style="background:#E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; border-left: #F5F560 solid 32px; font-size: 16px"><font face="Calibri" color="#ffffff"><center><i> Project Management </i></center></font></div></h2> | ||
<h3>Project Status</h3> | <h3>Project Status</h3> | ||
+ | Current Sprint: <b>11</b> <br> | ||
+ | Sprint Period: 26 September - 09 October <br> | ||
+ | Major Milestone: <b>Midterm Presentation</b><br> | ||
+ | Features Involved: Fixir Customer Web Application<br> | ||
+ | <br> | ||
+ | <i>Our project consists of 15 sprints and we have completed <b>67%</b> of our project scope. </i> | ||
+ | <h4>Outstanding Features</h4> | ||
+ | {| border="1" style="border-collapse:collapse;" | ||
+ | |- style="background:#E5A400; color:white" | ||
+ | |align="center"| Module | ||
+ | |align="center"| Status | ||
+ | |align="center"| New Feature? | ||
+ | |align="center"| Confidence Level | ||
+ | |align="center"| Remarks | ||
+ | |- | ||
+ | |||
+ | |align="center"| Valet | ||
+ | |align="center"| | ||
+ | |align="center"|Yes | ||
+ | |align="center"|1 | ||
+ | |align="center"|Project Team suggested to sponsor to add features in this module in order to make the valet process more robust. | ||
+ | |- | ||
+ | |||
+ | |align="center"| Customer Web App | ||
+ | |align="center"| | ||
+ | |align="center"|Yes | ||
+ | |align="center"|0.9 | ||
+ | |align="center"|Project Team suggested to sponsor to make use of a web application that is mobile optimized for the deployment so that their customers can experience their services even before their iOS application is ready. | ||
+ | |- | ||
+ | |||
+ | |align="center"|Payment | ||
+ | |align="center"| | ||
+ | |align="center"|No | ||
+ | |align="center"|0.9 | ||
+ | |align="center"| | ||
+ | |- | ||
+ | |} | ||
+ | <h4>Project Scope (Planned vs Actual)</h4> | ||
+ | {| class="wikitable" | ||
+ | |- style="background:#E5A400; color:white" | ||
+ | ! style="text-align: center; bold;background: #E5A400;color:white; width:17px; border:1px solid #999" | Planned | ||
+ | ! style="text-align: center; bold;background: #E5A400;color:white; width:17px; border:1px solid #999" | Actual | ||
+ | |- | ||
+ | |[[File:Fixxlar Project Scope Version4.jpeg|550px]] || | ||
+ | [[File:Fixxlar Project Scope Version6.1.jpeg|550px]] | ||
+ | |} | ||
<h3>Project Schedule (Planned vs Actual)</h3> | <h3>Project Schedule (Planned vs Actual)</h3> | ||
+ | {| class="wikitable" | ||
+ | |- style="background:#E5A400; color:white" | ||
+ | ! style="text-align: center; bold;background: #E5A400;color:white; width:17px; border:1px solid #999" | Planned | ||
+ | ! style="text-align: center; bold;background: #E5A400;color:white; width:17px; border:1px solid #999" | Actual | ||
+ | |- | ||
+ | |[[File:Fixxlar Schedule Version5.jpeg|550px]] || | ||
+ | [[File:Fixxlar Schedule Version6.jpeg|550px]] | ||
+ | |} | ||
<h3>Project Metrics</h3> | <h3>Project Metrics</h3> | ||
Line 96: | Line 150: | ||
|align="center"|High | |align="center"|High | ||
|| Project Team will make use of the GOOGLE CHROME POSTMAN to demonstrate the scenarios during the presentation. | || Project Team will make use of the GOOGLE CHROME POSTMAN to demonstrate the scenarios during the presentation. | ||
+ | |- | ||
+ | |||
+ | |align="center"| 5 | ||
+ | |align="center"|Resource Risk | ||
+ | ||Unable to find users to try out our application when we deploy the minimal viable web app for customers | ||
+ | |align="center"|Medium | ||
+ | |align="center"|Medium | ||
+ | || We will do our part by marketing our product through social media as early as possible so that users know of our application. | ||
|- | |- | ||
|} | |} | ||
Line 101: | Line 163: | ||
* Project Risk 4 has yet to happen. | * Project Risk 4 has yet to happen. | ||
<h3>Technical Complexity</h3> | <h3>Technical Complexity</h3> | ||
+ | <h4>Architecture Diagram</h4> | ||
+ | [[File:Fixxlar architecture diagram.png|900px]] | ||
<h2><div style="background:#E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; border-left: #F5F560 solid 32px; font-size: 16px"><font face="Calibri" color="#ffffff"><center><i> Quality of Product </i></center></font></div></h2> | <h2><div style="background:#E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; border-left: #F5F560 solid 32px; font-size: 16px"><font face="Calibri" color="#ffffff"><center><i> Quality of Product </i></center></font></div></h2> |
Revision as of 01:18, 28 September 2016
Project Overview
Project Highlights
- One-way valet service has been implemented and integrated into current process.
- Scheduling module has been implemented and integrated.
- Lead developer from Fixir team will be moving on to a full-time job - iOS app will not be delivered as promised (which has always been our biggest risk). This affects our project adversely as it may no longer be possible for us to go “live” in time to collect real user data.
- Major changes in scope, as we drop some functionalities (see scope revision) for our web application, and move our resources to develop a mobile-friendly website to replace the current iOS app (risk mitigation).
Project Management
Project Status
Current Sprint: 11
Sprint Period: 26 September - 09 October
Major Milestone: Midterm Presentation
Features Involved: Fixir Customer Web Application
Our project consists of 15 sprints and we have completed 67% of our project scope.
Outstanding Features
Module | Status | New Feature? | Confidence Level | Remarks |
Valet | Yes | 1 | Project Team suggested to sponsor to add features in this module in order to make the valet process more robust. | |
Customer Web App | Yes | 0.9 | Project Team suggested to sponsor to make use of a web application that is mobile optimized for the deployment so that their customers can experience their services even before their iOS application is ready. | |
Payment | No | 0.9 |
Project Scope (Planned vs Actual)
Planned | Actual |
---|---|
Project Schedule (Planned vs Actual)
Planned | Actual |
---|---|
Project Metrics
Project Risks
S/N | Risk Type | Risk Event | Likelihood | Impact | Mitigation Plan |
1 | Schedule Risk | iOS app used by customers not being able to be delivered by sponsor in time | High | High | Reduce scope for our web application, and do a minimal viable product in a web form (to simulate the iOS app). |
2 | Scope Risk | 2-way valet process flow not feasible, as it has never been done/tested before | High | Low | Only give the option of having 1-way valet which is more straightforward. Collect data from the user testing to figure out how receptive consumers are to this idea. |
3 | Schedule Risk | Client will not deliver the iOS application at all. | High | High | Fixir team will develop a web interface that is compatible on Mobile and use it to stand in for the iOS app so that the business can still be executed and tested by users. |
4 | Schedule Risk | Project Team will not be able to produce the web application in time to stand in for the mobile application | Medium | High | Project Team will make use of the GOOGLE CHROME POSTMAN to demonstrate the scenarios during the presentation. |
5 | Resource Risk | Unable to find users to try out our application when we deploy the minimal viable web app for customers | Medium | Medium | We will do our part by marketing our product through social media as early as possible so that users know of our application. |
- Project Risks 1, 2, 3 has happened and Project Team has informed Project Supervisor and proceed on with Plan B as our Backup Plan.
- Project Risk 4 has yet to happen.
Technical Complexity
Architecture Diagram
Quality of Product
Value Proposition
1. Value for Quotation Management
Before: Total time spent for customer from sending a quotation request, to Fixir administrator Whatsapp-ing/calling 3 workshops, and then replying customer: >30 mins (assuming that workshops pick-up their phones, and that requests are easy-to-understand, without complications)
After: Total time spent for customer to log a request and for 3 different workshop administrators to reply through the new web application with their estimated quotations: <10 mins (average time taken from all the user testings we have done, assuming that workshop administrators are active on the web application)
2. Value for Valet
Research agency 2CV has found that Singaporeans spent an average of 9 hours a week in their cars, which suggests that although Singapore is a tiny little country, most drivers maximise the usage of their vehicles - probably because the cost of owning a private vehicle is one of the highest in the world.
With extensive running of engine hours and mileage clocked, experts recommend that vehicles should be periodically inspected and maintained by professional workshops, ideally within every 20,000km or every 3 months, whichever comes first (kia.com.sg). However, with “time constraint” stated as the most obvious excuse from consumers, a whooping 89% of vehicles (carcare.org) are actually in need of at least one service or minor repair. This may be detrimental to the society as such defects may endanger the lives of all road users, and may also cause a higher volume of harmful emissions to be released into the environment.
Average time spent for basic servicing (including traveling to-and-fro to workshops): 3 hours. Imagine the amount of time saved if you were to get a valet driver to service your car on your behalf!
Immediate 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 |
Deployment
- slides to be updated
- deployment link