METHOD SELECTION AND PLANNING
Link to Method Selection and Planning PDFLink to Method Selection and Planning Google Doc
Project Breakdown Work Structure
Sprint Updates
(click charts to enlarge them)
Week One (15/02 - 21/02)
During the first week, our team focused on getting to know each other and understanding project requirements. We conducted a thorough review of the product brief provided by stakeholders and initiated requirements elicitation through the creation of interview questions. We scheduled a customer meeting for February 26th. Project management tools, such as GitHub, were set up alongside the creation of a Gantt chart to outline our project timeline.
Week Two (22/02 - 28/02)
By the end of the second week, we had gained a comprehensive understanding of product requirements and commenced writing the requirement documentation. Simultaneously, we initiated our risk assessment process. Weekly meetings were supplemented with impromptu meetings as needed, during which roles and tasks were delegated, and design brainstorming sessions were held for the game.
Week Three (29/02 - 06/03)
At the end of week three, significant progress was made in completing documentation. Discussions on architecture design enabled the assigned team members to initiate this phase. Concurrently, the risk assessment was finalised, and research on map design commenced. The project website was established, and the method selection writeup started. The Gantt chart was updated to reflect current role assignments and included all sections of the report.
Week Four (07/03 - 13/03)
In week four, substantial progress was achieved as implementation commenced. The map design was finalised, and initial drafts of the architecture were completed, later updated to accommodate ongoing implementation. Key features such as the home screen, preferences, and basic movement were implemented. To ensure timely completion, additional meetings were held, clarifying individual responsibilities and ensuring adherence to deadlines.
Week Five (14/03 - 20/03)
With the project deadline looming, daily 'stand-ups' were implemented to monitor progress. While the development team focused on implementation, other team members concentrated on documentation and ensuring readiness for client handover.