Daily Scrum 4 (Sprint 1) - shanjida-alam/Smart-Living-Community GitHub Wiki
01-November-2024
6:00 PM
15 Minutes
Discord Voice Channel
Mst.Solaimi Hamid
- Mst.Solaimi Hamid (SH)
- Shanjida Alam (SA)
- Irtifa Haider (IH)
- Hasneen Tamanna (HT)
- Md.Tanvir Hossain Saon (TH)
- Jubaer Ahmad Khan (JK)
- Frequency: Every 2 days
- Time: 6:00 PM
- Scrum Master: Jubaer Ahmad Khan (JK)
- Product Owners: Shanjida Alam (SA)
- Development Team Members: SH, IH, SA, TH, HT, JK
MEMBER(S) | What we did yesterday? | What problems faced? | What will do today? |
---|---|---|---|
1. SH | Implemented the ServiceRequestFragment for submitting service requests,using Spinner ,created the ServiceRequestModel class with Firestore annotations for request properties, developed the ResidentRequestViewModel to manage service request submissions and handle Firestore callbacks. |
Encountered minor issues with Firestore integration, particularly around data fetching and error handling during submission, faced challenges in ensuring data validation before submission. | Conduct unit testing on the ServiceRequestFragment and ResidentRequestViewModel to ensure all functionalities are working as expected,refine the error handling mechanisms to provide more user-friendly feedback during data submission failures. |
2. SA | Successfully fetched data from the database and displayed it in the user interface, implemented the manage profile feature within the navigation component,generated documentation for the manage profile feature. | Encountered challenges while fetching data from the database, faced difficulties in updating data within the database. | Conduct unit testing to ensure the functionality is working as expected,separate the profile interface based on user roles. |
3. IH | Continued development of the UploadEventViewModel and UpdateEventViewModel classes by implementing LiveData variables to track the status of uploads and updates,reviewed and documented the EventRepository methods for event management, specifically for the saveEvent, deleteEvent, and updateEvent functionalities, refactored the AddEventViewModel and EventDetailsViewModel classes, ensuring that all methods align with the MVVM architecture and maintain proper data encapsulation,added detailed documentation throughout the project to enhance code readability and maintainability. | Encountered minor issues with dependency configuration and integration with the Firebase backend, currently addressing these issues and making necessary adjustments to the project setup. | Testing and debugging the EventRepository methods to ensure data operations are functioning correctly with Firebase |
4. HT | Completed profile image upload functionality,implemented email authentication for sending unitCodes, applied registration app to livsmart app on github, Implemented userRole-based registration process. | Implementing the email authentication properly with correct information, Ensuring correct mail is sent to the correct user according to their role. | Ensure user can register to the app using one email only, implement profile image upload functionality, unit testing for security purpose. |
5. TH | Implemented the Secretary Dashboard and Security Officer Dashboard,redesigned the user interface for improved user experience,created documentation to facilitate understanding of the new features. | Encountered challenges with binding the Adapter class to the item XML file, faced issues setting up Gradle configuration and fetching from GitHub. | Implement unit tests to ensure the reliability of the dashboards, write test cases for the unit tests to validate functionality and performance. |
6. JK | Implemented a redirect interface from the Login Activity to the Main Content Activity, added a resource template that encompasses various login scenarios for the user, including: successful login, failed login, login errors due to required permissions. | Encountered a runtime error while establishing navigation between activities. | Develop a separate login interface for different user roles, implement data passing from the Login Activity to the Content Activity, add a splash screen for enhanced user experience, conduct unit testing for several functions to ensure robustness. |
- Maintain a Single Activity with Multiple Fragments: Ensure the project follows a single-activity structure, with navigation handled through multiple fragments. This approach promotes modularity, easier navigation management, and better alignment with modern Android architecture practices.