Sprint 13 - Mentor meeting
- Date: June 17th, 2026
Progress Updates
Completed and received approval for the badge system designs:
- Badge achievement pop-up.
- Badges overview and progress page.
Drafted the initial backend and frontend tasks required for the badge feature.
Started implementing the frontend badge redesign.
Sprint 14 development is now in progress.
Sprint Planning
- The scheduled sprint planning meeting could not be held due to timetable conflicts.
- Development was started asynchronously based on previously agreed responsibilities.
- The mentor emphasized that sprint planning should be completed before the sprint begins, with a clearly defined scope and assigned tasks.
Mentor Feedback
Improve Sprint Planning
- Hold a short planning meeting before each sprint (Saturday or Sunday).
- Define the full sprint scope before implementation begins.
- Estimate effort and assign all tasks during planning.
- Sprint commitments should be agreed upon collectively rather than relying solely on individual responsibility.
Break Down Large Tasks
Large tasks should be decomposed into smaller subtasks.
Smaller tasks:
- Improve transparency.
- Make progress easier to track.
- Are easier to schedule and complete.
Improve Team Coordination
We should ensure everyone knows:
- Their assigned tasks.
- The expected effort for the sprint.
- The work being carried out by the rest of the team.
The sprint backlog should be finalized before development starts instead of adding tasks throughout the sprint whenever possible.
Status Updates
Status updates should be viewed as progress updates rather than formal reports.
They should:
- Keep everyone informed of ongoing work.
- Demonstrate progress toward shared sprint goals.
- Encourage accountability and collaboration across the team.
Agreed Process Improvements
- Hold a weekly sprint planning meeting before each sprint.
- Finalize and estimate all sprint tasks before implementation begins.
- Break large tasks into smaller, manageable units.
- Improve commitment to the agreed sprint scope.
- Use status updates to monitor overall team progress rather than focusing only on individual contributions.