Skip to content

Sprint 3 minutes and docs

Imran Ahmed edited this page Mar 23, 2022 · 1 revision

Sprint 3 Meetings

Meeting 7, Feb 25

Meeting Date/Time: Friday February 25, 12:15 pm

Meeting Purpose:

  • Breakdown the tasks to do for Sprint 3

Note Taker: Imran Ahmed

Items to discuss

  • Discussed if any issues/troubles occurred
  • Assign tasks to members for Sprint 3

Work and Progress

Who Item Notes
Imran Ahmed Will work on User story 2. Both front end and Back end Work in progress.
Julian Aloise N/A N/A
Michael Djabauri Will work on improving the login/register pages Troubles occurred in implementing a feature. Will discuss with Mathew for help
Matthew Faigan Will work on the login and register pages (back-end) Will Help Michael with his troubles
Sabari Krishna Orakkan N/A N/A
Siming Shen N/A N/A
Zi Hao Tan Will work on user story 3 with Imran Will wait for Imran to finish user story 2 so that he can explain the process

Meeting 8, March 9

Meeting Date/Time: Wednesday March 9, 12:00 pm (Around 20 minutes)

Meeting Purpose:

  • Additional Breakdown of the tasks to do for Sprint 3

Note Taker: Imran Ahmed

Items to discuss

  • Discussed if any issues/troubles occurred
  • Assign additional tasks to members for Sprint 3

Work and Progress

Who Item Notes
Imran Ahmed Will work on the meeting minutes for meeting 9 Will help Michael explain how to implement admin portal
Julian Aloise N/A N/A
Michael Djabauri Will work on the admin portal to add/edit/delete users and adding to the cart functionalities N/A
Matthew Faigan Will work on the testing Will Make researches during the weekend on which software to use for testing
Sabari Krishna Orakkan N/A N/A
Siming Shen N/A N/A
Zi Hao Tan Will work on acceptance tests for all user stories Brought up concerns about user stories and core features for the project. Wanted clarification

Meeting 9, March 11

Meeting Date/Time: Friday March 11, 12:30 pm (Around 15 minutes)

Meeting Purpose:

  • Following up on the tasks that were given to each member and clarifying any doubts/troubles

Note Taker: Sabari Krishna

Items to discuss

  • Following up on the tasks that were given for each members
  • Clarify any doubts/troubles of each members

Work and Progress

Who Item Notes
Imran Ahmed Following up on each member and how there tasks have been progressing Aiming to finish most of the coding part of the project for this spirnt
Julian Aloise N/A N/A
Michael Djabauri Explaining how he will proceed to implement the cart N/A
Matthew Faigan Decided to use supertest for the testing part of the project He used supertest during his internship and is very familiar with this software. Will work on the weekend and throughout next week
Sabari Krishna Orakkan Will work on handling the github page and arranging the documents/meetings in the way as discussed by TA in tutorials N/A
Siming Shen Interested in working on the testing with Mathew N/A
Zi Hao Tan Will work the acceptance test for all user stories Will take into consideration the feedback from sprint 2 about acceptance testing and will make sure to do them as told by the TA

Meeting 10, March 16

Meeting Date/Time: March 11, 10:00 am (Around 15 minutes)

Meeting Purpose:

  • Have the members shows their progress for their tasks

Note Taker: Imran Ahmed

Items to discuss

  • Have members show what they have done as of this meetings
  • Clarify any doubts/troubles of each members

Work and Progress

Who Item Notes
Imran Ahmed Looking at each members progress of their tasks and giving feedback/constructive criticism for each member Suggested Zi Hao to make the acceptance testing more detailed. Impressed with Michael's work and suggested to improve the UI of the website.
Julian Aloise N/A N/A
Michael Djabauri Implemented user roles and the cart functionality. Will work on the cart a bit more and add more features to it. Will also improve the UI more and make it look a bit modern
Matthew Faigan Still making research about using supertest for the testing Have made progress in the work but not enough to show anything. Will work on it more throughout the week
Sabari Krishna Orakkan N/A N/A
Siming Shen N/A N/A
Zi Hao Tan Showing a document containing all the acceptance tests for each user story Will take into consideration the feedback from Imran in adding more details in the acceptance tests.

Meeting 11, March 18

Meeting Date/Time: Friday March 18, 12:15 am (Around 25 minutes)

Meeting Purpose:

  • Check the rubric of sprint 3 and see if everything has been completed

Note Taker: Imran Ahmed

Items to discuss

  • Look at the rubric and see what is missing.
  • Prepare on what to do for sprint 4.

Work and Progress

Who Item Notes
Imran Ahmed Looking at the rubric and seeing if everything has been completed and none is missing. Will work on user story 3 Will have to represent the risks and story points as issues. Will have to move every documentations in the wiki side
Julian Aloise N/A N/A
Michael Djabauri Will work on the managing profile for next sprint and implement a order history for users Created issues for the coding part of sprint 4
Matthew Faigan Made progress on the testing part for Sprint 3 Wanted to clarify which user stories were done so that he could implement the automated tests
Sabari Krishna Orakkan N/A N/A
Siming Shen N/A N/A
Zi Hao Tan N/A N/A

Acceptance testing for all user stories

User story#1 - As a customer, I want to be able to create an account and/or log in into an existing account because I want to be able to shop for products.

Positive case

  1. The customer clicks ‘Login’ button.
  2. Login form appears.
  3. The customer enters correct information and clicks ‘Login’ button.
  4. The customer clicks on their desired category.
  5. A list of available products related to the clicked category and their description is shown.

Negative case

  1. The customer clicks ‘Login’ button.
  2. Login form appears.
  3. The customer enters incorrect information and clicks ‘Login’ button.
  4. An error message is displayed.

User story#2 - As a seller, I want to be able to create an account and/or log in into an existing account because I want to add/edit/modify a product.

Positive case 1

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Add Product’ button.
  8. Add product form appears.
  9. Seller enters correct information and clicks ‘Add Product’ button.
  10. The list of products of the seller updates. It contains the new added product with ‘Delete’ and ‘Modify’ button.
  11. The list of products for users to browse updates with the new added product of the seller and its information.

Positive case 2

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Delete’ button of one product.
  8. The list of products of the seller updates. It contains one less product.
  9. The list of products for users to browse updates by having one less product available for customers.

Positive case 3

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Modify’ button.
  8. Modify form appears.
  9. Seller enters correct information and clicks ‘Modify’ button.
  10. The list of products of the seller updates. It contains the modified version of the product.
  11. The list of products for users to browse updates by having the modified version of the product.

Negative case 1

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Add Product’ button.
  8. Add product form appears.
  9. Seller enters correct information and clicks ‘Add Product’ button.
  10. The list of products of the seller does not update. It does not contain the new added product with ‘Delete’ and ‘Modify’ button.
  11. The list of products for users to browse does not update with the new added product of the seller and its information.

Negative case 2

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Delete’ button of one product.
  8. The list of products of the seller remains the same and does not update.
  9. The list of available products for customers to browse does not update with the deleted product of the seller.

Negative case 3

  1. The seller clicks ‘Login’ button.
  2. Login form appears.
  3. Seller enters correct information and clicks ‘Login’ button.
  4. ‘My Products’ button appears.
  5. The seller clicks on ‘My Products’ button.
  6. The list of products of the seller appears with their buttons ‘Delete’ and ‘Modify’.
  7. The seller clicks ‘Modify’ button.
  8. Modify form appears.
  9. Seller enters correct information and clicks ‘Modify’ button.
  10. The list of products of the seller does not update. It does not contain the modified version of the product.
  11. The list of products for users to browse does not update by having the modified version of the product.

User story#3 - As an administrator, I want to be able to add/delete/modify an account because I want to be able to maintain the website.

Positive case 1

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Add user’ button.
  8. Add user form appears.
  9. Administrator enters correct information and clicks ‘Add user’ button.
  10. The list of profiles of the website updates. It contains the new added user with ‘Delete’ and ‘Modify’ button.

Positive case 2

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Delete’ button of one of the users.
  8. The list of profiles of the website updates with one less user.

Positive case 3

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Modify’ button of one of the users.
  8. Modify user form appears.
  9. Administrator enters correct information and clicks ‘Modify user’ button.
  10. The list of profiles of the website updates. It contains the modified information of the user.

Negative case 1

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Add user’ button.
  8. Add user form appears.
  9. Administrator enters correct information and clicks ‘Add user’ button.
  10. The list of profiles of the website does not update. It does not contain the new added with ‘Delete’ and ‘Modify’ button.

Negative case 2

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Delete’ button of one of the users.
  8. The list of profiles of the website does not updated with one less user.

Negative case 3

  1. The administrator clicks ‘Login’ button.
  2. Login form appears.
  3. Administrator enters correct information and clicks ‘Login’ button.
  4. ‘Manage profiles’ button appears.
  5. The administrator clicks ‘Manage profiles’ button.
  6. The list of profiles of the website appears with their button ‘Delete’ and ‘Modify’.
  7. The administrator clicks ‘Modify’ button of one of the users.
  8. Modify user form appears.
  9. Administrator enters correct information and clicks ‘Modify user’ button.
  10. The list of profiles of the website does not update. It does not contain the modified information of the user.

User story#4 - As a customer, I want to be able to to filter the products by their categories and/or prices because I want to be able to browse for a specific product.

Positive case

  1. The customer clicks ‘Filter’ button.
  2. Filter form appears.
  3. The customers enters valid filtering information and clicks ‘Filter’ button.
  4. The list of available products is filtered matching the information entered previously.

Negative case

  1. The customer clicks ‘Filter’ button.
  2. Filter form appears.
  3. The customers enters invalid filtering information and clicks ‘Filter’ button.
  4. An error message is displayed.
Clone this wiki locally