# Retrospective Nov 3

Doc Type | Retrospective

Sprint Retrospective Meeting Minutes

Project: Learnr

Attendees: Rose, Amani

Start time: 6:30

End time: 7:00

Did we do a good job estimating our team's velocity?

- Given our awareness of the Dunning-Kruger effect, where individuals tend to overestimate their competence due to a lack of knowledge and skills, it is noteworthy that our estimation of team velocity has performed commendably.

Did we do a good job estimating the points (time required) for each user story?

- Our estimation of points (time required) for user stories presents a mixed picture. It aligns well with expectations for the user interface portion but falls short in the case of setting up the Microsoft authentication process.

Did each team member work as scheduled?

- On a positive note, each team member adhered to their schedules as planned.

- Several key aspects contributed to our successes:
  - Effective communication fostered collaboration.

    What went right?

  - Steady progression ensured a continuous workflow.
  - Exploring multiple avenues allowed us to consider and test out various solutions.
  - Proactive assistance-seeking demonstrated a commitment to problem-solving.

How to address the issues in the next sprint?

How to improve the process?

- In order to enhance our processes, we should consider the following strategies:
  - Draw upon historical team performance to better estimate user stories, especially for complex tasks like Microsoft authentication setup.

How to improve the product?

- Implement UI/UX enhancements to improve the overall user experience, making the project more user-friendly and visually appealing.

- Incorporate necessary account management and administrative features to enhance the project's functionality and meet user needs.