# Sprint Review Oct 22

Doc Type | Sprint Review

Review Meeting Minutes

Project: Learnr

Attendees: Rose, Amani

Start time: 6:00 PM

End time: 6:30 PM

After a show and tell presentation, the implementation of the following user stories was accepted by the product owners:

1. User Story 1: As a developer, I want to transition the Learnr project from using a CSV database to a relational database, so that we can efficiently manage and access data.

2. User Story 2 (Revisited): As a user, I want to be able to see my profile information - Now using the relational database

3. User Story 3 (Revisited): As a user, I want to be able to fill up my account profile with additional information to my profile such as bio, interests, school, so that my profile is complete and reflects my identity within the system - Now using the relational database. Upon creation of a user, all profile information characteristics are filled in with null values (that show nothing if value is true, and get replaced with actual value if information if edited)

4. User Story 4 (Revisited): As a user, I want the ability to edit my account profile information, so that I can keep it up to date as my details change - Now using the relational database

5. User Story 5 (Revisited): As a super mentor, I want the ability to reset the password of other users, so that I can assist them in case they forget their password or encounter login issues. - Now using the relational database

6. Stretch work:
   1. Revisit the previous User stories and adapt to the new database
      Super mentor can fill in user account with high level info (email, position)
      All users have the ability to sign in using a username and password
      User with account created by supermentor can sign in with the username and password created by supermentor
      Super mentor can fill in user account with high level info (username, password)
      Super mentor can create user account (super mentor, mentor, mentee)

The following ones were rejected and moved back to the product backlog to be assigned to a future sprint at a future Sprint Planning meeting.

- None