Sprint 16 - Team Meeting Summary

• Date: July 11th, 2026

Note: Team meeting summaries are provided periodically and capture the main planning decisions and project updates. Not every internal team meeting was recorded or documented.

Project Updates

• We discussed the remaining work and priorities for the final weeks of the project.
• The Projects feature remains the main development priority but this should be confirmed on next meeting with the client.
• The Follow feature priority will be confirmed with the client before implementation.
• Badge development is mostly complete, with the remaining work focused on testing and bug fixing.

Client Communication

Feature Priorities

• We agreed to contact the client directly to confirm the final feature priorities instead of waiting for another meeting.
• Existing profile designs with the Follow feature will be used as a starting point if approved.
• Regular follow-up with the client was emphasized to avoid waiting for responses.

Handover Preparation

• We reviewed the previous meeting with the next student team.
• A complete handover document will be prepared to describe the system, deployment process, and major changes.

Technical Discussion

Migration Status

• Migration to the university infrastructure is still blocked by pending actions from the university IT department.
• We agreed that better status updates are needed so the team can help if work becomes blocked.
• Team members will contact the infrastructure maintainer directly to clarify the current status.

Infrastructure Issues

• OTP verification works locally but still fails in the deployed environment, likely due to server configuration.
• Telegram bot issues remain unresolved and are believed to be related to the current hosting environment.
• The team will investigate both issues and redistribute work if necessary.

Badge Testing

• Recent badge logic was updated to revoke badges when participation is cancelled.
• We agreed to continue testing the badge system and report any remaining issues.

Team Reflection

• We discussed concerns about mentor feedback and overall project performance.
• While development progress has improved compared to earlier in the project, we recognized that documentation, project artifacts, migration progress, and process quality also affect the evaluation.
• We will review the official feedback once available and address the reported issues.

Agreed Actions

• Confirm the final feature priorities with the client.
• Prioritize the Projects feature and continue badge testing.
• Improve communication on migration status and infrastructure issues.
• Prepare comprehensive handover documentation for the next team.
• Review mentor feedback and address remaining process improvements before the final presentation.