Iteration 1 Meeting - AvengerDisassemble/KU-connect GitHub Wiki
Iteration 1 Retrospective Report
What went well
- Excessive workload assigned to Sunthorn – this issue has already been addressed.
- Certain tasks were left incomplete due to overlapping academic and extracurricular activities.
- Lack of advance work distribution for upcoming iterations – proper planning would help in workload estimation and fair distribution.
What could be improved
- Team communication was clear and effective.
- Proposal presentation was well-prepared and delivered successfully.
- Workload distribution among members was balanced.
- Documentation quality was sufficient and met requirements.
- Development process was generally smooth and consistent.
- Meetings were flexible yet punctual – schedules could be adjusted in advance, and members attended on time after rescheduling.
How can we improve
- Plan and allocate work for the next two iterations (no need to break down the second one yet).
- Apply time estimation techniques such as Planning Poker (to be conducted in the upcoming week).
- Record estimated working hours per iteration in the Discord forum as allocated time.
- Introduce automation for testing, coding style enforcement, and AI-assisted tools.
- Allow additional story points to be assigned when time is required for automation or learning new tools.
- Refrain from coding during meetings to keep discussions focused.