Sprint 1 Retrospective Meeting Minutes
16 February 2024 10:00 PM - 10:45 PM Google Meet
Sumaita Binte Shorif(SB)
Sanzida(IA) Jannat(JF) Sumaita(SB) Saba(FR) Sathi(AA)
- What went well?
- What went wrong?
- How can we improve?
- What have we learnt?
| What went well | What went wrong | How can we improve |
|---|---|---|
| Payment Feature went well and completed successfully | Problems faced regarding credit card | Will recheck and add more test-cases |
| Book Deliveryman feature went smoothly. | Couldn’t integrate the order tracking | Will improve the tracking feature by integrating “Pathao” API |
| Review, Add Product Request features went smoothly | Problems faced regarding sending email from different Domains (eg. From gmail domain to juniv domain) | Will have to integrate several mail domains |
| Search based on Categories went smoothly. | Problems faced related to integrating search libraries, optimizing search algorithms | Identify and prioritize additional features or functionality that would enhance the search experience for users. Will consider implementing features such as autocomplete suggestions, faceted search, or advanced filtering options to improve usability and efficiency. |
| In add item by renter feature, adding items went smoothly | Faced problems related to branch creating, pushing commits to github. Could not implement select item feature | Will improve this feature by creating forms |
- We have acquired proficiency in using GitHub, managing commits via the terminal, crafting informative commit messages, and harnessing GitHub's wiki and documentation features extensively.
- Our familiarity with Trello has empowered us to efficiently track progress and manage routines.
- We've explored documentation tools like Sphinx, JavaDoc, and JSDoc, and upon conducting comparative analysis, decided that Sphinx works the best for our project.
- Through meticulous work, we've created comprehensive Software Requirements Specifications (SRS), established robust coding standards, and compiled detailed Test-Driven Development (TDD) reports.
- We have taken a deep dive into testing frameworks such as unittest and pytest, and finally decided that unittest works the best for us ensuring the quality and reliability of our code.
- Our commitment to clear and concise communication is reflected in our proficient use of Discord channels to discuss and thus solve all kinds of problems we have faced during sprint 1.
