HeaderSIS.jpg

IS480 Team wiki: 2016T1 Airvolution Midterm Wiki

From IS480
Revision as of 22:10, 24 September 2016 by Weirong.tay.2014 (talk | contribs)
Jump to navigation Jump to search


Airvolution-Logo.png


Airvolution-House.png  HOME

 

Airvolution-About-Us.png  ABOUT US

 

Airvolution-Project-Overview.png  PROJECT OVERVIEW

 

Airvolution-Project-Management.png  PROJECT MANAGEMENT

 

Airvolution-Documentation.png  DOCUMENTATION

 
Main Wiki Midterm WikiAirvolution-Paper-Plane.png Final Wiki


Project Progress Summary

Airvolution-Project-Summary.jpg

Project Management

Project Status

S/N Function/features, etc Status Confident Level (0-1) Remarks
1. Speech-to-query function Fully deployed and tested 100% 1 Completed
2. Search Function Fully deployed and tested 100% 1 Completed
3. Booking Function (Make a new Booking) Fully deployed and tested 100% 1 Completed
4. Payment Function Fully deployed 1 In Progress
5. Account Management Developing 1 In Progress
6. Machine Learning Function Developing 1 In Progress
7. Analytics Dashboard Pre-Processing Data in Progress 1 In Progress
8. Booking Function (Price Watch Function) Developing 1 In Progress
9. Notification Function (Push notification) Future Development 1 Future Development
10. Weather Function Future Development 1 Future Development

Project Schedule (Plan vs. Actual)

Planned Project Schedule

Actual Project Schedule

Project Metrics

Project Risks

Risk Type Risk Event Likelihood Impact Level Category Strategy Adopted Actions
Technological Risk Team is unfamiliar with machine learning, Angular 2.0 and iOS programming. HIGH MEDIUM HIGH Mitigate Team to actively research on technology share the knowledge with the team
Dependency Risk Client unable to give required APIs needed for app to function MEDIUM HIGH HIGH Mitigate Actively engage client and his IT team to provide us with the API. At the same time, we also mock out the APIs and images first to carry on with our sprint
Dependency Risk Client unable to provide us with live transaction data for us to carry our our data mining MEDIUM HIGH HIGH Mitigate Actively engage client to provide us with the data. We got our supervisor to help voice out our concerns as well so as to help expedite the request
Client Risk There may be drastic changes to the clients requests at any point of the project which result in drastic changes to our schedule in order to satisfy them if needed. MEDIUM HIGH MEDIUM Mitigate By using an iterative approach, the client is able to regularly give feedback on our progress so that changes can be made at any time without making drastic changes to our schedule
Client Risk Initial X-factor unable to be done as client does not want to expose his clients to the POC yet as our project is just the start. There are many more components which need to be added before it is ready to be shown to clients which is out of our scope. HIGH HIGH HIGH Mitigate Mitigate Actively engage client to give us another party to validate our app. Client was able to get us Amadeus to vet our progress and app and to give comments for us to learn and improve on.

Technical Complexity

Quality of Product

Intermediate Deliverables

Deployment

Testing

Reflection

Team Reflection

Individual Reflections