Sprint‐1 Retrospective Meeting Minutes - SubarnaSaha08/JUMCMS-Jahangirnagar-University-Medical-Center-Management-System GitHub Wiki

Date

October 2, 2024

Location

Online, Google Meet

Time

09:25 PM

Attendees

Product Owner

Hasan Al Mamun(HS)

Scrum Master

Subarna Saha(SS)

Other team Members

  • Fatima Binte Aziz(FB)
  • Sudipta Singha(SD)
  • Shabrina Akter Shahana(SA)
  • Saud Al Nahian(NH)

Sprint Overview

Sprint Goal

This sprint's objective was to create the Jahangirnagar University Medical Center Management System's basic features, with an emphasis on patient management, user access, and critical services. The team's goal was to have basic functionality available by the conclusion of the sprint, such as the ability to create an account and log in, schedule patient appointments, publish information about seasonal diseases, dispensing medications, rescheduling tests, and viewing ambulance information. These characteristics will facilitate early system interactions and offer a useful foundation for future advancements.

Sprint Duration

October 24, 2024 to November 2, 2024

Total Story Points

Total 8 story points was planned and all of them are completed

What Went Well

Discussing the positive aspects of the sprint, including achievements, successful teamwork, and processes that worked well.

  • Role-based Login functionality was completed successfully where custom tests are passed.
  • Implementation of features of displaying different attributes of a Doctor in a user-friendly went smoothly and finished testing the features.
  • The Make Appointment feature was successfully implemented, allowing users to schedule appointments with doctors as required.
  • The Create Blogpost feature was successfully developed and integrated into the project, meeting all the initial requirements. Testing and debugging were managed well, leading to a relatively smooth development process.
  • Completed Account Creation feature.
  • Completed Dispense Medicine feature where custom tests are passed for all feature.
  • Implementation of text appointment rescheduling functionalities went well.
  • Completed View Ambulance Information feature and implemented User Interface for viewing ambulance information in tabular format.
  • The team collaborated effectively, with each member contributing efficiently to their assigned tasks.

What Could Be Improved

Identifying areas for improvement, including challenges faced, bottlenecks, and aspects of the sprint that could be better.

  • Problems faced during implementing the reset password option, the password saving feature and inactivity detection procedure. These features could be implemented for the better performance of the application.
  • The appointment form could be optimized for better user experience where UI could be more smooth and documentation for the feature could be improved.
  • Sprint planning and time estimation could be improved, documentation could be improved to include more detailed steps for setting up the feature and testing coverage for edge cases could be increased, especially for image uploads and error handling.
  • The UI could be improved and more knowledge about URL routing would be helpful for handling challenges in URL routing.
  • Problem faced during implementation as I preferred bottom-up approach like completed the backend part first then the frontend which introduced me redundant implementation. Will try to avoid this in future sprint.
  • The User Interface could be improved to show exact location of ambulance in google map.

Lessons Learned

Capturing any key lessons learned from the sprint that can be applied to future sprints.

  • Understood that one needs to be careful while using Toggl as it tracks time based on the local device's clock. Any changes to the device's time settings may disrupt the accuracy of Toggl's tracking. Gained the idea of how to estimate time for any project.
  • Learned about Testing and bug fixes.
  • Estimated time was too short, we have learned about a good estimated average time.
  • Got better understanding of Django by actually implementing the product and learned how to use Toggl as a time tracking tool.
  • Should follow the conventional approaches while implementation and will have to be more careful about using Toggl as once I forgot to stop the Toggl which made a real mess-up in tracking.
  • How to use Django & HTML for development and toggl for time tracking.

Next Steps

Important next steps, such as planning for the next sprint or scheduling follow-up meetings.

  • Next Sprint Planning: November 4, 2024
  • Next Retrospective Meeting: November 11, 2024