Sprint 1 Retrospective Meeting Minutes

Date, Time and Location: 2 November 2024 11:00pm - 11:45pm Discord Voice Channel
Scrum Master: Jubaer Ahmad Khan

1. Introduction

• Objective: Reflect on Sprint 1 and identify areas of improvement for Sprint 2.
• Duration: 45 minutes

Attendees:

• Mst.Solaimi Hamid (SH)
• Shanjida Alam (SA)
• Irtifa Haider (IH)
• Hasneen Tamanna (HT)
• Md. Tanvir Hossain Saon (TH)
• Jubaer Ahmad Khan (JK)

Scrum Roles

• Scrum Master: Jubaer Ahmad Khan (JK)
• Product Owner: Shanjida Alam (SA)
• Development Team Members: SH, IH, TH, SA, HT, JK

2. Check-in

• Mood Check: "How are you feeling about this sprint-1?"
  • Responses:
    • Solaimi: "I've gained confidence"
    • Shanjida: "Took me so much time, but eventually learned many things and gained more patience"
    • Irtifa: "A bit overwhelmed by the scope, but learned a lot."
    • Totinee: "Goes smooth so far, hoping to face new challenges"
    • Tanvir: "Confident, but some tasks took longer than expected."
    • Jubaer: "That was really a challenging task to setup the project template codes"

3. Review the Sprint-1 Goals

• Goals:
  • Implement user login and authentication
  • Complete initial testing of the product dashboard
  • Fix high-priority bugs from the last sprint
• Achievements:
  • User login and authentication were implemented successfully.
  • Initial testing of the product dashboard was completed.
• Challenges:
  • A few bugs from previous sprints were more complex than anticipated.
  • Communication around task dependencies needed improvement.

4. Sprint Performance Analysis

What Went Well? 🎉

Project Setup & Architecture

• ✅ Successfully set up the master branch and integrated template code
• ✅ Maintained single-activity architecture with multiple fragments
• ✅ Established proper project dependencies and component navigation
• ✅ Successfully integrated Firebase with the project

Feature Development

✅ Completed major UI & Features implementations:

Feature	Team Member
Service Request functionality	Mst.Solaimi Hamid
Registration system	Hasneen Tamanna
Login interface, Project templates	Jubaer Ahmad Khan
User Dashboards (Resident, Secretary, Security Officer)	Md.Tanvir Hossain Saon
Event management system	Irtifa Haider
Profile management features	Shanjida Alam

Team Collaboration

• ✅ Consistent attendance in daily scrums
• ✅ Regular meetings every 2 days
• ✅ Clear documentation of progress
• ✅ Effective branch management and version control
• ✅ Successfully merged 6 pull requests from teammates

Technical Achievements

• ✅ Successfully implemented email authentication
• ✅ Unicode generation and assigning it for each resident
• ✅ Integrated Firebase Firestore for data storage
• ✅ Implemented MVVM architecture patterns
• ✅ Created comprehensive navigation graphs to handle fragments

What Didn't Go Well? 🚧

Technical Challenges

• ❌ Difficulties with RecyclerView integration
• ❌ Issues with navigation graph flow
• ❌ Challenges with data binding in XML layouts
• ❌ Problems with Firebase connection (particularly for team members new to NoSQL)

Data Management Issues

• ❌ Challenges in fetching and updating data from Firebase
• ❌ Difficulties in proper data validation
• ❌ Issues with database integration

Integration Challenges

• ❌ Runtime errors during activity navigation
• ❌ Problems with adapter class binding
• ❌ Gradle configuration issues
• ❌ Challenges in implementing email authentication properly

Individual Issues

• Profile Management Delay ❌

  • Feature progress impacted due to team member's (SA) health condition
  • Unit testing phase pending completion
  • Will be prioritized in the upcoming sprint

• Event Management Status ❌

  • Development timeline affected by team member's (IH) illness
  • Feature implementation partially completed
  • Both feature completion and unit testing moved to next sprint

How Can We Improve? 📈

Technical Improvements

1. Implement more comprehensive unit testing across all features
2. Create detailed documentation for common issues and their solutions
3. Establish standard practices for Firebase integration
4. Set up regular code review sessions to catch issues early
5. Organize the template codes, then discuss it with teammates to maintain team synchronization

Process Improvements

1. Create templates for common implementations to avoid repetitive issues
2. Establish a knowledge-sharing system for technical solutions
3. Set up pair programming sessions for complex features
4. Do a review for testing before pushing code to GitHub

Quality Assurance

1. Implement systematic unit testing for all new features
2. Create test cases (TDD) before implementation
3. Establish error handling standards

Documentation

1. Maintain up-to-date documentation for all features
2. Create troubleshooting guides for common issues
3. Document best practices for Firebase integration
4. Keep clear records of architectural decisions
5. Maintain the coding standards stictly

5. Discussion

Key Topics

1. Bug Management:
   • We'll allocate additional time for complex bugs in the planning phase.
2. Communication and Dependencies:
   • Set a weekly sync for team members handling interdependent tasks.

• Follow-ups: Review last sprint's action items to ensure they were completed.

6. Closing

• Summary:
  • Improved task dependency communication is crucial for the next sprint.
  • Bug management will be addressed earlier in sprint planning.
• Feedback:
  • "You guys are doing good things, try to put more fuel on it" ~ Jubaer
  • "Putting some extra effort will make this project great" ~ Irtifa