This sprint marked another important phase of our project as we continued to refine our system and work closely with our community partner. One of our major successes was conducting a productive community partner meeting, which helped us clarify expectations and gather meaningful feedback. Alongside that, our frontend reached near completion, and we also made strong progress on implementing the backend. These milestones brought us much closer to a complete and functional system.
Despite the progress, this sprint also came with a few challenges. Limited team member availability made coordination more difficult than usual, and working on the same files led to multiple conflicts during development. These issues slowed us down at times, but we managed to overcome them through consistent communication and by resolving conflicts using proper version control practices like Git. Preparing for our playback was also demanding, requiring us to stay late at the office to ensure everything was ready. In the end, the effort paid off, and the playback went smoothly.
Our team dynamics remained strong and encouraging. Everyone stayed dedicated to their assigned tasks, and we made it a point to help one another whenever someone got stuck. To refresh ourselves and build stronger bonds, we even went on a hike together, which lifted our spirits and strengthened our team connection (Achut seemed to have had a hard time during the hike). Throughout the sprint, we divided work fairly, motivated each other, asked about pending tasks when necessary, and shared the journey of INSPIRE NEPAL with our mentors. Small end-of-iteration refreshment activities kept us energized and reminded us to celebrate the small wins.
Our collaboration has continued to evolve in a positive way. We divide tasks fairly, communicate openly, and step in to support anyone who falls behind. When problems arise, we tackle them together through brainstorming and shared problem-solving, making the entire development process smoother and more enjoyable.
Looking ahead, we anticipate several challenges in the next sprint. Empowering facilitators to use our system effectively will require careful planning. To address this, we aim to co-design a meaningful user experience, explain the system’s benefits clearly, provide detailed user manuals, and apply for grants to support server and database needs. We will also be working under strict deadlines, as we must both complete the system and prepare for the final conference. To handle this workload, we are planning to focus on proper sprint planning, time management, and task prioritization.
Even with these challenges ahead, the next sprint is something we are genuinely excited for. We are looking forward to visiting a remote Self Help Group, meeting facilitators, deploying our solution on Microsoft Azure, and conducting a soft launch for our community partner. We also plan to provide a bug report sheet, implement stronger authentication and security measures, and make final adjustments to our analytics after the field visit.
As we move forward, we feel more confident in our abilities, our teamwork, and the impact our project can create. This sprint has been yet another reminder that growth happens not only through coding, but also through collaboration, patience, and shared determination.