SMT483G1: Anly.io Project Management

HOME

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

Project Plan

End of Week	Milestone	Features	Progress
1	Discuss Specifications and Logistics with Sponsor Show UI/UX Mockup to Sponsor (7 Jan) Design UI/UX	Main Page	Done
2	Develop Front-end Develop Back-end	Game	Game is delayed
3	Develop Back-end	Login and administration	Login and administration done Shifted from Azure to AWS
4	Showcase a Minimum Viable Product to Sponsor (31 Jan)		Sponsor changed to Victoria School Meeting on 4/2
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

Resources

Technology

a. Stack (Alpha Build)
    i. Front-end: Angular 8 Framework
    ii. Back-end: Flask Framework (Monolith for now)
    iii. DB: PostgreSQL RDB
    iv. Authentication: Basic Access Authentication + JWT + LocalStorage
b. Unit Testing: unittest (If time permits)
c. Project Management and System Architecture
    i. Source Code Management: Gitlab
    ii. Containerization: Docker
    iii. CI/CD: Gitlab
    iv. Hosting: AWS EB/EC2

Self-study For Software Engineering

a. System Architectural Development and Design
b. Angular 8
c. Flask (incl. Unit Tests)

Financial Costs

a. Hosting with Azure App Services
b. Trip money to and from the schools

Temporal Costs

a. Testing with students
b. Meeting client
c. Meeting supervisor

Manpower Costs

a. Developers (us)
b. Testers (students)