G_Week4,2025‐03‐12 - 24-S2-2-C-EduKATE/EduKATE_flutter GitHub Wiki

Time

12/03/2025

Attendees

  • Yi Wang
  • Siyi Liu
  • Dong-Jhang Wu
  • Rifang Zhou
  • Wenhui Shi
  • Wenjing Qi

add more if needed

Agenda

  1. Team Stand-ups
  2. Sprint Assessment Requirements Discussion
  3. Required Documentation Review
  4. Project Direction and Architecture

Minutes

Team Stand-ups

  • Yi Wang During the stand-up, I introduced myself as a continuing member of the project. I briefly outlined my role moving forward and mentioned that last week, I reviewed Scrum and Agile-related materials. This week, my focus is on understanding documentation requirements and discussing the necessary files for Sprint 1.

  • Siyi Liu What I did previously: Contacted the client to establish communication. Reviewed the EduKATE project to get familiar with the current state. What I’m going to do next: Identify documentation requirements and clarify necessary reports. Design a suitable architecture and templates for documentation.

  • Dong-Jhang Wu What I have done: Contacted the client and reviewed the project code and document. What I'm going to do: deeply reviewing the current code, and try to identify any potential issues.

  • Rifang Zhou What I Have Done: Review our pervious code What I Have To Do Next: Participate in formulating the plan for this semester

  • Wenhui Shi Finished user story of our project, took a look on our previous code. Next week we will start structuring code and adding the function required in client meeting.

  • Wenjing Qi What I did previously: Reviewed the EduKATE landing page and familiarized myself with the existing codebase. Participated in team meetings to understand project goals and requirements. What I'm going to do next: Contribute to the development of user stories and assist in structuring the code for Sprint 1. Collaborate with team members on documentation requirements.

Sprint Assessment Requirements

We discussed the assessment requirements with the tutor, who explained that the evaluation focuses on five key areas:

  • Stakeholder engagement (20%)
  • Planning and organization (20%)
  • Execution and quality (20%)
  • Reflection and improvement (20%)
  • Collaboration and teamwork (20%)

Required Documentation Review We reviewed and agreed on the necessary documentation for Sprint 1:

  • Sprint backlogs
  • Task assignments
  • Meeting minutes (client, tutor, and group meetings)
  • Progress reports
  • Retrospective reflections Our tutor emphasized the importance of standardized documentation with consistent formatting and regular updates. All members understood that documentation must be detailed and consistently uploaded to meet assessment criteria.

Project Direction and Architecture Dong-Jhang Wu identified several technical issues that need addressing:

  • The object class may require redesigning, with block functions potentially separated into distinct inherited classes
  • A tree structure might be more suitable than the current list structure for tracking block sequences
  • The team needs to review client requirements to revise the context accordingly

Actions

Action Item Responsible Due Date Status
Finalize Sprint 1 goals and task assignments Siyi Liu Week 5 Completed
Complete Sprint 1 documentation including goals and reports Siyi Liu Week 5 Completed
Redesign object class structure Dong-Jhang Wu Week 5 Pending
Review client requirements and revise context All team members Week 5 Completed
Complete user stories based on client requirements Wenhui Shi, Wenjing Qi Week 5 Completed
Create templates for project documents Rifang Zhou, Yi Wang Week 5 Completed
Document Week 4 tutor meeting minutes Yi Wang Week 4 Completed

8-Hour Work Tracking

  • Yi Wang

    I thoroughly analyzed the assessment requirements outlined in the Sprint Guide and discussed them with the team to ensure a clear understanding. Our conversation focused on identifying the required documentation for submission, such as sprint backlogs, meeting minutes, and task breakdowns, while also reviewing the necessary templates for each document. Additionally, we had a meeting with the client to clarify project requirements. This discussion helped define key expectations and deliverables for Sprint 1. As part of this, we also finalized a weekly meeting schedule with the client to ensure regular communication and feedback. Lastly, I completed the Week 4 tutor meeting minutes, ensuring that all important points were recorded and shared with the team for future reference. Moving forward, we will refine the backlog and prepare initial documentation based on the agreed templates.

  • Siyi Liu

    Reviewed information on Wattle to identify the necessary tasks for this semester.
    Met with the tutor to discuss the Sprint structure and understand the checklist for each Sprint.
    Thoroughly examined the Sprint checklist to determine what needs to be logged in Git.
    Attended client meeting to confirm the project direction—focusing on optimizing the Block Part in EduKATE.
    Finalized Sprint 1 goals and assigned individual tasks to team members.
    Completed Sprint 1 documentation including the goals and relevant reports.
    Wrote my section for the group meeting documentation to summarize my contributions.

  • Dong-Jhang Wu

    I reviewed the current code, and there are a few issues that need to be addressed: The object class may require redesigning, as different block functions may need to be separated into distinct inherited classes. Instead of using a list to track the block sequence, a tree structure might be easier to implement. A team review of the client requirements is necessary to revise the context accordingly.

  • Rifang Zhou

    During today’s work, I completed the following tasks:

    I reviewed the TechLauncher 2025 S1 Sprint Assessment Guide to understand the assessment criteria, including stakeholder engagement, planning and organisation, execution and quality, reflection and improvement, and collaboration and teamwork. I carefully studied the general flow of the assessment process, the checklist for each criterion, and the marking rubric to ensure a comprehensive understanding of the expectations.

    I discussed with my team the documents needed for the project and what their templates should be. We identified the essential documents such as project plans, meeting minutes, and sprint backlogs. For each document, we determined the necessary sections, formatting guidelines, and content requirements. We then created templates for each document type, ensuring they align with the project’s needs and the assessment criteria outlined in the guide. This involved designing clear headings, appropriate sections for relevant information, and consistent formatting to enhance readability and usability.

  • Wenhui Shi

    In week 4, I join both client meeting and tutor meeting for our project. In tutor meeting, I study about sprint requirements and checklist so I know what documents we need to finish. We talk about what files we must submit like sprint backlog and meeting notes. Then in client meeting, we confirm what we will do in Sprint 1, mainly focus on making Block Part in EduKATE system better. After meetings, I write some user stories based on what client wants. I also spend time look at our old code to understand how it works and find parts we can improve.

  • Wenjing Qi

    During this week, I first attended both the client meeting and tutor meeting to gain a comprehensive understanding of our project requirements and Sprint assessment criteria. Then I studied the TechLauncher 2025 S1 Sprint Assessment Guide thoroughly to familiarize myself with the evaluation process, including stakeholder engagement, planning, execution, reflection, and teamwork aspects. I also collaborated with team members to identify and create templates for essential project documents. and reviewed our previous codebase to identify areas for improvement and potential optimization in the Block Part of the EduKATE system. Participated in team discussions to finalize Sprint 1 goals and task assignments. Assisted in the preparation of initial Sprint 1 documentation, I mainly contributed to the development of user stories based on client requirements and discussions from our meetings. Finally, I summarized my contributions and next steps on our group meeting records.