IS480 Team wiki: 2016T2 LickiLicky Midterm Wiki
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Main Wiki | Midterm Wiki | Final Wiki |
---|
Contents
Project Progress Summary
Midterm Slides: To be uploaded
Current Iteration: 12
Total Iterations: 16
Iteration Dates: 20 February 2016 to 4 March 2016
- Overall Project Progress: 90%
- Modules To-Be Done - Tertiary: Backup Module (Cloud backup)
- Modules To-Be Done - Good to Have: Smart Module (Best time to contact)
- Modules Completed: User, Note Taking, Search, Reminder, Group, Social, Multimedia, Scheduling
- LickiLicky is confident of completing all modules up till tertiary functions with an additional good to have function
- Android Mobile Application to be deployed on Google Play Store
Project Highlights
- To be updated
Project Management
Project Scope
Insert Scope Here
Project Timeline
Insert Previous Timeline Here Insert Midterm Timeline HerePlanned | Actual |
---|
Project Status
Module | Status | Confident Level (0-1) | Comment |
---|---|---|---|
User | 100% | 1 | Fully deployed and tested. |
Note Taking | 100% | 1 | Fully deployed and tested. |
Search | 90% | 0.9 | Tag Contacts in Notes and Hashtags functions to be improved. |
Reminder | 100% | 1 | Fully deployed and tested. |
Group | 100% | 1 | Fully deployed and tested. |
Social | 90% | 0.9 | Link Contacts to be improved. |
Multimedia Module | 90% | 0.9 | Attach Media to Notes to be improved. |
Scheduling Module | 100% | 1 | Fully deployed and tested. |
Backup Module | 50% | 0.5 | Cloud backup to be developed after Midterm. |
Schedule Highlights
To be updated
Project Metrics
Schedule Metrics
To be uploaded
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action Taken | Status |
---|---|---|---|---|---|
3 | 14 | 16 | 0.88 | More time needed to complete suggest group function. Follow up action: Schedule slip was presented during Acceptance presentation. No delay to overall schedule as there are no major function to be developed in Iteration 4, which was scheduled to be preparation for Acceptance. Supervisor was informed of the slip after project was Accepted. |
Completed |
7 | 14 | 16 | 0.88 | More time needed to develop filter search function. Follow up action: Supervisor informed about delay. More hours was put into developing the function. No major delay in overall schedule as PM scheduled only one function, birthday reminder, to be developed in Iteration 8 due to festive period. |
Completed |
11 | 14 | 17 | 0.82 | More time needed to develop Hashtags and debug bugs reported for User Test 3 Supervisor informed about delay. More hours was put into developing the function. No major delay in overall schedule as no major function was scheduled to be developed in Iteration 12, prior to Midterm Presentation. |
Completed |
Bug Metrics
To be uploaded
Iteration | Bug Score | Bug Summary | Action Taken |
---|---|---|---|
5 | 42 7 Low 3 High 2 Critical |
A major regression testing was perform after acceptance which causes the spike in bug count. The 2 critical bugs are "new contacts added not reflected under suggest group" and "reminders and notes not backup upon app updates". | Resolve bugs immediately. No major delay was caused as iteration 5 was scheduled for post acceptance debugging. |
6 | 30 5 Low 3 High 1 Critical |
1 critical bug was due to app crash when reminder was set for a non-existing group and there is a notification for this reminder. | Resolve bugs immediately. No major delay was caused as iteration 6 was scheduled for post acceptance debugging. |
8 | 10 2 High |
2 high bugs were "expired reminders continue to remain in reminder list" and "recurring reminders did not take on new date/time" | Resolve bugs immediately. No major delay was caused as iteration 8 was scheduled for post acceptance debugging and development of only 1 function, birthday reminder. |
9 | 122 7 Low 11 High 6 Critical |
The spike in bug count were bugs that were reported during User Test 2. The critical bugs were mainly due to app crashes after a series of actions were performed using different phone models. | Resolve bugs immediately. UT2 took place over a week period and it was design to have participants to submit a daily feedback form. Participants would also report bugs to us which allows the developers to resolve the bugs on a daily basis. PM scheduled a "debugging (backlog)" task and allocated the Lead Developer to resolve these bugs while having 2 Backend Developers to develop the functions that were scheduled for Iteration 9. |
10 | 30 4 High 1 Critical |
The critical bug was an app crash while performing a series of actions using Note 3. | Resolve bugs immediately. Critical bug did not occur again after new APK was released. Similar action was performed but bug did not replicate. |
11 | To be updated |
Project Risks
Risk Description | Category | Impact | Mitigation Strategy |
---|---|---|---|
Limited variety of Android phone models to perform testing | Medium | There may be compatibility issues with less popular Android phone models. | We stretch our user testing period which will allow us to continuously recruit participants and allow testing on more variety of phones. |
Technical Complexity
To be Uploaded