Difference between revisions of "IS480 Team wiki: 2016T1 Airvolution Midterm Wiki"
Jump to navigation
Jump to search
Line 134: | Line 134: | ||
===<div style=" font-size:85%; font-family:Century Gothic">Actual Project Schedule=== | ===<div style=" font-size:85%; font-family:Century Gothic">Actual Project Schedule=== | ||
[[Image:Airvolution-Project-Schedule-v3.jpg|center|824px|link=]] | [[Image:Airvolution-Project-Schedule-v3.jpg|center|824px|link=]] | ||
+ | <div style="margin-top: 20px;"> | ||
+ | {| class="wikitable" style="background-color:#FFFFFF; width:100%; text-align: center;" | ||
+ | |- | ||
+ | ! style="color:white; background-color:#226C9A;" colspan="8" | Changes in Schedule | ||
+ | |- | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Sprint No. | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Date | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Category | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Change Description | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Reason for Request | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Accept/Reject | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Priority | ||
+ | | style="background-color:#226C9A; color: #FFFFFF; font-weight: bold;" | Status of Request | ||
+ | |- | ||
+ | ||5 | ||
+ | ||31 Aug 2016 | ||
+ | ||X-Factor | ||
+ | ||X- factor to be changed from getting 20 live users to test our app to getting GDSs to validate our app and analytics platform | ||
+ | ||X-factor not able to be done as client is not comfortable with getting the 20 live UOB customers to test the app. | ||
+ | ||Accept | ||
+ | ||Accept & High Priority | ||
+ | ||Closed | ||
+ | |- | ||
+ | |- | ||
+ | ||5 | ||
+ | ||2 Sep 2016 | ||
+ | ||Analytics Dashboard | ||
+ | ||To deploy our analytics dashboard on their own Tocco Azure Server | ||
+ | ||Client wants to have the analytics deployed on their own Azure server so that they can access the dashboard and maintain control over the dashboard as sensitive data will be hosted on it. | ||
+ | ||Accept | ||
+ | ||Accept & High Priority | ||
+ | ||Closed | ||
+ | |- | ||
+ | ||6 | ||
+ | ||1 Sep 2016 | ||
+ | ||Application | ||
+ | ||To add mock flight data which are tagged as UOB preferred | ||
+ | ||Client would like us to mock out some flight data which are UOB preferred so we can simulate such flights | ||
+ | ||Accept | ||
+ | ||Accept & Low Priority | ||
+ | ||Closed | ||
+ | |- | ||
+ | ||6 | ||
+ | ||17 Sep 2016 | ||
+ | ||Application | ||
+ | ||Remove Notification Module - Boarding Gate Updates and belt no. | ||
+ | ||API were not available and creating or sourcing for an API would be too time-consuming | ||
+ | ||Accept | ||
+ | ||Accept & Low Priority | ||
+ | ||Closed | ||
+ | |- | ||
+ | ||6 | ||
+ | ||23 Sep 2016 | ||
+ | ||Application | ||
+ | ||Formally removed seat-booking function, update current booking function, SMS function | ||
+ | ||There are no APIs are available and implementing it ourselves would be very time-consuming. Thus, we decided to formally drop these functions so we can focus on making the app better and on the machine learning | ||
+ | ||Accept | ||
+ | ||Accept & Low Priority | ||
+ | ||Closed | ||
+ | |- | ||
+ | |} | ||
+ | </div> | ||
===<div style="background: #226C9A; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:85%; font-family:Century Gothic"><font color= #FFFFFF>Project Metrics</font></div>=== | ===<div style="background: #226C9A; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:85%; font-family:Century Gothic"><font color= #FFFFFF>Project Metrics</font></div>=== |
Revision as of 15:33, 2 October 2016
Main Wiki | Midterm Wiki | Final Wiki |
Project Progress Summary
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 and test 100% | 1 | In Progress |
5. | Booking Function | Fully deployed not 100% tested. | 1 | In Progress |
6. | Account Management | 50% | 1 | Front-end complete, coding back-end now. |
7. | Analytics Dashboard | 30% | 1 | Basic dashboard is up for now. Analyzing dataset to come up with the charts which need to be included in the dashboard. |
8. | Price Watch Function + Push Notification | 40% | 1 | Remy is able to push notifications now. Currently working on the algorithm for the price watch function. Followed by linking the 2. |
9. | Machine Learning Function | Future Development | 1 | Future Development |
10. | Notification Function (Confirmation Email) | Future Development | 1 | Future Development |
11. | Weather Function | Future Development | 1 | Future Development |
Project Schedule (Plan vs. Actual)
Planned Project Schedule
Actual Project Schedule
Changes in Schedule | |||||||
---|---|---|---|---|---|---|---|
Sprint No. | Date | Category | Change Description | Reason for Request | Accept/Reject | Priority | Status of Request |
5 | 31 Aug 2016 | X-Factor | X- factor to be changed from getting 20 live users to test our app to getting GDSs to validate our app and analytics platform | X-factor not able to be done as client is not comfortable with getting the 20 live UOB customers to test the app. | Accept | Accept & High Priority | Closed |
5 | 2 Sep 2016 | Analytics Dashboard | To deploy our analytics dashboard on their own Tocco Azure Server | Client wants to have the analytics deployed on their own Azure server so that they can access the dashboard and maintain control over the dashboard as sensitive data will be hosted on it. | Accept | Accept & High Priority | Closed |
6 | 1 Sep 2016 | Application | To add mock flight data which are tagged as UOB preferred | Client would like us to mock out some flight data which are UOB preferred so we can simulate such flights | Accept | Accept & Low Priority | Closed |
6 | 17 Sep 2016 | Application | Remove Notification Module - Boarding Gate Updates and belt no. | API were not available and creating or sourcing for an API would be too time-consuming | Accept | Accept & Low Priority | Closed |
6 | 23 Sep 2016 | Application | Formally removed seat-booking function, update current booking function, SMS function | There are no APIs are available and implementing it ourselves would be very time-consuming. Thus, we decided to formally drop these functions so we can focus on making the app better and on the machine learning | Accept | Accept & Low Priority | Closed |
Project Metrics
Project Risks
To view past risks that the team may have/may not been affected by, please visit: IS480 Team wiki: 2016T1 Airvolution-Risk Management
Current Risks that may affect the team:
Risk Type | Risk Event | Likelihood | Impact Level | Category | Strategy Adopted | Actions |
---|---|---|---|---|---|---|
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 | 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. Client has yet to meet Amadeus |
Technical Complexity
Quality of Product
Intermediate Deliverables
Stage | Specifications | Work Product(s) |
Project Management | Minutes | There are 3 types of minutes being maintained: Client Minutes, Supervisor Minutes and Internal Minutes. Our minutes can be found here: Meeting Minutes |
Metrics | We maintain 3 types of metrics to monitor our progress: Sprint Velocity, Scrum Burn down Chart, Bug Metrics. Our metrics can be viewed here: Metrics | |
Change Management | Whenever changes are being made, the team will deliberate and decide on the severity and importance before coming to a group decision of accepting or dropping the change. Our changes can be viewed here: <URL> | |
Risk Management | We have a risk metrics in place to keep track of the risks that may disrupt the success of our project as well as our mitigation. Our risks and mitigation can be viewed here Metrics | |
Sprint Backlog | To look for the breakdown of tasks completed at each sprint, our Sprint Backlog can be viewed here: Sprint Backlog | |
Testing | User test plan | Every sprint, the QA team will conduct an integration and regression testing to ensure that the app is still working fine after the new implementations and to look for more corner cases in order to make the app more stable. Our testing can be viewed here <URL> |
Design & Research | Use case | This is the use case diagram for our iOS app and management dashboard. Our diagram can be viewed here <URL> |
Market Study | We conducted a market study of the popular travels apps in the market to see what are the unique selling points and mandatory features that these apps share to help validate our client's claim that there is a gap in the market for speech-to-text booking and a recommendation engine. Our research can be viewed here: <URL> | |
Screen Shots | As our project is under NDA, we cannot post the screenshots of our App here. To view it, please go to our private document <URL> |