Case 01 / 12
Sanan Corporation · Preschool management · Web & Mobile
SanAn Kids
A preschool management ecosystem with mobile apps for parents, teachers, and school staff, plus web platforms for teachers and administrators. Access depends on both the user's role and the school's paid service package.
- What it shows
- Scrum & delivery
- My role
- Frontend Developer · Scrum Master
- When
- 6/2024 – now
- Company
- Sanan Corporation
01 · The problem
SanAn Kids
Context
A preschool runs many workflows at once: student records, service registration, tuition calculation, fee collection, and notifications to parents. Each one shows up in several apps, for several roles.
A small change to a business rule, like how tuition is calculated for a registered service, could touch the parent app, the teacher app, and the admin web at the same time. When edge cases weren't found before development, they turned up late in QA or in production.
02 · What I did
SanAn Kids
- 01Worked with stakeholders to turn requests into concrete flows and screens.
- 02Before estimating, listed the business rules, exceptions, and which roles, screens, and data each change would affect.
- 03Agreed on the solution with Backend, Frontend, and QA early, and helped write the test scenarios we used for acceptance.
- 04Built and maintained Angular web and React Native mobile features, including role-based and package-based access.
- 05As Scrum Master for a 6-person team: ran ceremonies, tracked progress, cleared blockers, and helped analyse production bugs.
03 · Decisions & trade-offs
SanAn Kids
Impact analysis before estimation
For changes to tuition, fees, or services, the team sees the affected roles, screens, and data before giving an estimate. Catching a broken fee flow at that point costs far less than catching it after release.
Access by role and by package
A feature is gated by both the user's role and the school's paid package, so one codebase serves schools on different plans.
04 · Screens
SanAn Kids




05 · What I achieved
SanAn Kids
What changed
- Sprint success rate above 95%, tracked with structured sprint metrics.
- Features shipped on both web and mobile.
Next case study · Sanan
Kizna