TheBrosCode MidTermWiki
Revision as of 12:41, 3 September 2018 by Yubin.loh.2016 (talk | contribs)
HOME |
MID TERM |
Modules | Total | Completed | Remaining | Status | Confident Level (0-1) | Comment | % Total Done |
---|---|---|---|---|---|---|---|
Account | 3 | 3 | 0 | 100% | 1 | Fully deployed and tested | - |
Food | 3 | 3 | 0 | 100% | 1 | Fully deployed and tested | |
Activity | 6 | 6 | 0 | 100% | 1 | Fully deployed and tested | |
Event | 4 | 3 | 1 | 75% | 1 | 1 more tertiary function left to do after Mid Terms milestone | |
Affective | 1 | 0 | 1 | 0% | 1 | To be implemented after Mid Terms milestone | |
Social | 2 | 0 | 2 | 0% | 1 | To be implemented next iteration | |
Analytical | 1 | 0 | 1 | 0% | 1 | To be implemented next iteration | |
Friends | 2 | 2 | 0 | 100% | 1 | Fully deployed and tested | |
Notifications | 2 | 2 | 0 | 100% | 1 | Fully deployed and tested | |
Management | 4 | 0 | 4 | 0% | 1 | Sean will be implementing the front-end, Guan Ze will be implementing the back-end. |
Iterations | Planned | Actual | Comments | ||
---|---|---|---|---|---|
1 | Account Module | 23 May 2018 | 24 May 2018 | Sean and Guan Ze went for OCSP so team was short of manpower. Delayed for 1 day. | |
2 | Food Module | 12 June 2018 | 12 June 2018 | Everything went as plan | |
3 | Activity Module | 1 July 2018 | 1 July 2018 | One of the hardest and most complicated module in this entire project. Everyone worked hard and the team managed to complete the iteration within the timeframe. | |
4 | Events Module | 18 July 2018 | 18 July 2018 | Everything went as plan | |
5 | Regression Testing | 28 July 2018 | 28 July 2018 | Everything went as plan | |
User Acceptance Testing 1 | 3 August 2018 | 3 August 2018 | Everything went as plan. Had 30 participants participated in the user testing | ||
6 | Acceptance | 17 August 2018 | 17 August 2018 | Completed our Acceptance milestone. | |
7 | Friends Module | 22 August 2018 | 22 August 2018 | A interesting module that we are excited about. Allowing us to add friends. | |
Notifications Module | 25 August 2018 | 25 August 2018 | One of the hardest module due to the different scenarios that user might face. Everything went as plan. | ||
8 | Analytical Module | 4 September 2018 | Have not implemented | ||
Social Module | 7 September 2018 | Have not implemented |
Risk | Probability | Impact | Mitigation |
---|---|---|---|
Runkicker may not be able to operate on phones that do not meet the minimum SDK version of the app. | High | Low | The team has to ensure that Runkicker supports not only the latest SDK version, but also several older versions in order to reach a wider population. |
The Frontend / Backend development of the mobile app partially relies on online libraries to help speed up the team's progress, however there might be incompatible versions / outdated libraries. | High | Low | The team is required to research and test the libraries thoroughly before implementing any of it into the mobile app. |
As the target audience of the mobile app can range from unmotivated to obese / overweight individuals, finding such users can be a challenging and sensitive task for the team. | High | High | The team is required to have EARLY planning of User Testing sessions internally and also to liaise with sponsors, to see if it is possible to work together with enterprise or government bodies to assist with the testing of the mobile app. |
Stage | Specification | Modules |
---|---|---|
Project Management | Meeting Minutes | TheBrosCode MeetingMinutes |
Task Metrics | TheBrosCode Metrics | |
Bug Metrics | TheBrosCode BugMetric | |
Analysis | Use Case Diagram | TheBrosCode Documentation |
Design | ER Diagram | TheBrosCode ERDiagram |