Post by Anita Nalukenge

Managing Technical Debt and Engineering Velocity: Building Tutukayo via Agile Scrum frameworks Maintaining development velocity across a full-stack, decoupled platform deployment requires strict adherence to project management frameworks and architectural discipline. This week, our engineering team hit major milestones on our platform, TUTUKAYO—a high-availability mobile web application configured to mitigate transit carpooling complexities and unify campus food delivery logistics for students around the Uganda Christian University (UCU) Main Campus in Mukono. Architecturally, our team is implementing a strictly decoupled methodology: Client-Side User Interface: Built using declarative React functional components, managed via Vite compilation configurations, and styled using utility frameworks to minimize browser page-load latency. Server-Side API Gateway: Powered by Node.js and Express.js middleware engines to process inbound validation requests, handle session state tokens, and evaluate coordinate matching algorithms. To ensure parallel development paths without triggering system-wide merge blocks across team members, the global source architecture was mapped across separate backend and frontend remote repositories housed within a unified GitHub Organization sandbox handle. Our Agile Scrum tracking strategy was organized into four distinct project tracks: Product Backlog & Ready Tracks: High-level requirements were broken down into distinct, numbered GitHub Issues (such as our core User Interface Framework #2, Administrative Dashboard View #3, and Database Setup Definitions #8) to maintain clear development lanes. Active In-Progress Track: Engineering tasks focused heavily on building transaction validation routes for mobile wallet payment logging (#5), designing spatiotemporal coordinate matching logic for shared carpooling (#7), and mapping data schemas for booking infrastructures (#6). Verified Done Track: We finalized item #12, establishing complete asynchronous HTTP communication pathways between our detached client layouts and backend network ports without triggering cross-origin or browser blocking errors. A major engineering takeaway from this sprint involved data mocking strategies. Because live production relational databases were being developed concurrently with our frontends, we bypassed integration blocks by designing an in-memory database simulation structure (mockDb.js). Building endpoints that process JSON arrays before migrating to full relational schemas kept our frontend developers completely unblocked. The foundations are secure as we prepare for full database migration. Check out our repository structures directly via our master organization sandbox: https://lnkd.in/dEwSA8fd #SoftwareEngineering #ReactJS #NodeJS #AgileScrum #GitHub #FullStack #Vite #WebDevelopment #CodingBootcamp #TechLogistics #UgandaTech