KHC Basketball Club
Implementing a Web App scheduling system.
Problem
Our client struggled to organize practices and games across multiple teams. They also lacked an efficient way to communicate with players and track availability.
Research & Planning
The team approached the project like a real-world product. We researched existing apps, ran surveys with players and coaches, analysed stakeholder requirements, and created user personas, stories, and journeys to align on their needs.
Solution
We built a calendar web application where coaches could create, update, and manage events. Players could players could keep track of games and practices and also book practice and game slots, with availability updating in real time.
This streamlined event management and improved communication across the club.
Challenges
My biggest challenge was getting familiar with how Supabase handle database queries, authentication and authorization. Although we had not used it before, due to our time constraints, we chose to implement it because it was going help us build our backend faster.
My Role & Development
MVP 1 – Event Calendar
Goal
Display all practices and games in a shared calendar.
My contribution
Backend setup. I helped configuring routes and queries to retrieve event data and render it in the calendar. Adapted quickly to Supabase despite limited prior experience.
MVP2 - Booking System
Goal
Let players reserve slots while preventing overbooking.
My contribution
Implemented database logic so bookings updated availability dynamically. Disabled slots once sessions are filled. Also supported front-end styling.
MVP 3 – Roles & Auth
Goal
Add user profiles with role-based permissions.
My contribution
Worked on authentication so only coaches could create, edit, or delete events. Also helped refining styling of the Bootstrap’s calendar component.
Final Sprint – Testing & Polish
Goal
Deliver a fast, responsive, and reliable app.
My contribution
Led end-to-end testing with Playwright to validate user flows across browsers. Ensured the app was functional, modern, and mobile-friendly.
Outcome
In just four weeks our team delivered a full end-to-end product by applying Agile and Scrum practices, weekly sprints, pair programming, daily stand-ups, and regular stakeholder check-ins.
Although the stakeholder ultimately chose not to move forward because their limited resources. The team demonstrated how quickly we could turn an idea into a working product under real industry conditions.
