Difference between revisions of "SMT483G1: Anly.io Project Management"
Stsze.2017 (talk | contribs) (Created page with "===Project Plan=== {| class="wikitable" |- ! End of Week !! Milestone !! Features !! |- | 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Spo...") |
Stsze.2017 (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | ==Project Plan== | |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| − | ! End of Week !! Milestone !! Features | + | ! End of Week !! Milestone !! Features |
|- | |- | ||
| 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Sponsor (7 Jan)<br>Design UI/UX || Main Page || | | 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Sponsor (7 Jan)<br>Design UI/UX || Main Page || | ||
| Line 36: | Line 36: | ||
|} | |} | ||
| − | === | + | ==Risks and Assumptions== |
| + | ===Assumptions=== | ||
| + | 1. Teachers are willing to try teaching using games<br> | ||
| + | 2. A cloud-based system by subscription is suitable for MOE's requirements in terms of security and | ||
| + | cost-effectiveness<br> | ||
| + | 3. A single platform is able to meet the learning needs of both IP, express and normal stream students<br> | ||
| + | ===Risks=== | ||
| + | 1. Schedule backlog due to fundamental changes required after user testing<br> | ||
| + | Mitigation: plan schedule with buffer to cater for overrun<br> | ||
| + | 2. Data privacy risk from collecting student and staff details<br> | ||
| + | Mitigation: encrypt student details and other important information when storing them on cloud platform<br> | ||
| + | 3. Insufficient product validation for commercialisation<br> | ||
| + | Mitigation: conduct user acceptance tests on a variety of schools with mix of IP, express and normal stream<br> | ||
| + | students to ensure good product fit<br> | ||
Revision as of 01:13, 20 January 2020
Project Plan
| End of Week | Milestone | Features | |
|---|---|---|---|
| 1 | Discuss Specifications and Logistics with Sponsor Show UI/UX Mockup to Sponsor (7 Jan) Design UI/UX |
Main Page | |
| 2 | Develop Front-end Develop Back-end |
Game | |
| 3 | Develop Back-end | Login and administration | |
| 4 | Showcase a Minimum Viable Product to Sponsor (31 Jan) | ||
| 5 | User Acceptance Test (1st round) (3-9 Feb) | ||
| 6 | Refine usability | Complete Learning Path of “Quests” Develop Buffer Feature |
|
| 7 | Mid-term Presentation and Report | ||
| 8 | User Acceptance Test (2nd round) (24-29 Feb) | ||
| 9 | Refine usability | ||
| 10 | Deploy to Cloud Go Live |
||
| 11 | User Acceptance Test (3rd round) (16-22 Mar) | ||
| 12 | Refine Usability CI/CD Prepare Demo and Presentation |
||
| 13 | Develop Business Model and Go-to Market Strategy CI/CD Prepare Report |
||
| 14 | Final Presentation | ||
| 15 | Report Submission |
Risks and Assumptions
Assumptions
1. Teachers are willing to try teaching using games
2. A cloud-based system by subscription is suitable for MOE's requirements in terms of security and
cost-effectiveness
3. A single platform is able to meet the learning needs of both IP, express and normal stream students
Risks
1. Schedule backlog due to fundamental changes required after user testing
Mitigation: plan schedule with buffer to cater for overrun
2. Data privacy risk from collecting student and staff details
Mitigation: encrypt student details and other important information when storing them on cloud platform
3. Insufficient product validation for commercialisation
Mitigation: conduct user acceptance tests on a variety of schools with mix of IP, express and normal stream
students to ensure good product fit
