Iteration 1 Meeting - AvengerDisassemble/KU-connect GitHub Wiki

Iteration 1 Retrospective Report

What went well

  1. Excessive workload assigned to Sunthorn – this issue has already been addressed.
  2. Certain tasks were left incomplete due to overlapping academic and extracurricular activities.
  3. Lack of advance work distribution for upcoming iterations – proper planning would help in workload estimation and fair distribution.

What could be improved

  1. Team communication was clear and effective.
  2. Proposal presentation was well-prepared and delivered successfully.
  3. Workload distribution among members was balanced.
  4. Documentation quality was sufficient and met requirements.
  5. Development process was generally smooth and consistent.
  6. Meetings were flexible yet punctual – schedules could be adjusted in advance, and members attended on time after rescheduling.

How can we improve

  1. Plan and allocate work for the next two iterations (no need to break down the second one yet).
  2. Apply time estimation techniques such as Planning Poker (to be conducted in the upcoming week).
  3. Record estimated working hours per iteration in the Discord forum as allocated time.
  4. Introduce automation for testing, coding style enforcement, and AI-assisted tools.
  5. Allow additional story points to be assigned when time is required for automation or learning new tools.
  6. Refrain from coding during meetings to keep discussions focused.