Sprint 1 Meeting Minutes - 2109688/Market-place GitHub Wiki
Scrum backlog refinement + Sprint planning
6 April 2021
Members present:
- Rylan Perumal (instructor)
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Sisonke Msezane
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
None
Discord Registration and Login planning
Meeting Recap
Three user stories: Registration + Login + Homepage (For Sprint 1 only Registration and Login are expected to be done)
If user has an existing account, then they can log in with their credentials, else they can register for account.
For login we can have the user login using either their username or email address and password (We chose email) For registration we want to capture their first – and last name, date of birth, email address, username and password.
Passwords need to be encrypted.
Backlog
After the Login/Registration the user should be taken to a homepage and the products should be displayed on the home page.
Products should be displayed similar to how it would look on a site like Takealot/Amazon. It should be a set of row where each row represents a different category of product and each column in a row should represent a different product in the category. Each box could contain a picture of the product and underneath the picture the product name and price (This is just an example of what would be seen as acceptable).
For now, just add random products to the database (5-6 categories at least and add products under each category of the database, use fake data for now) We don’t have to use a SQL database, but we need to maintain database integrity (relational integrity).
Each product should be clickable and when you click on an object it should open a modal for that object. The modal should show a bigger picture of the product and if there are multiple pictures of the product it should allow you to scroll through them (This is an unimportant down the line feature). The modal should have the big picture, product name, price, product description and how much stock we have of the product. We can consider storing the single image in an array so that in the future being able to add multiple pictures will be easier to implement. The next step will be to add a buy button for each modal. Another thing to add to the backlog is some sort of navigation bar, a cart and order history.
Security
Don’t use HTTP, use HTTPS/SSL, low priority issue (second sprint) -Be warned, setting up an SSL might take sometime depending on how comfortable we are with them.
Interface
Focus on functionality before trying to make things look amazing and fit to any screen size, but Rylan does want things to look good once we have functionality dealt with.
Sprint 1 vs. Sprint 2
User Stories needs to be done for this sprint and the backlog can be worked on for sprint 2.
Other
In 2nd semester we MIGHT develop an app, but for now just worry about the website.
Setting up everything on Taiga? Set up the user stories Rylan gave us and a product backlog for everything, write everything in user story format. Each user story should have at least one acceptance criteria but most will have more. For now, only worry about doing this for the ones in the current Sprint.
After we put it all onto Taiga, we can split the user stories up into different tasks.
We split the roles as followed:
- Login: Shan, Yaakov
- Registration: William, Shlomo, Yaakov
- Homepage: Moshe, Sisonke
- Database: Yaakov, Tawanda
Use GitHub for version control.
If the user gives the correct login: Take them to the home screen. Wrong logins: Return an alert to the browser. Homepage doesn’t need to be done for Sprint 1, but it’s highly recommended we at least start on its user story and we should have one for now even if it’s only a blank page with the words “Home screen”.
Most people use a GraphQL/Key based database, but a relational database is much easier.
Sprint Planning Part 2
09-April-2021
Members present:
- Rylan Perumal (instructor)
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Yaakov Brill
- Vusumzi Booi (meeting organiser)
Members missing:
- Sisonke Msezane
Meeting recap
Roles
We will have roles going forward. (Specific roles to specific people to be more efficient).
Talk about github and who does which user stories. Everyone needs to commit something to github for the project so if required we can have some people edit and resubmit code as necessary. They’ll also check how frequently you commit things to the github and make changes, everyone needs to make these changes.
Everyone should’ve received a github invitation, some people have not joined yet. Everyone needs to make sure they have access to taiga.io and github. If you need any sort of help with github talk to Shlomo he’ll help you get set up and explain how to commit code to it.
Roles:
- Updating Taiga.io (User Stories + Backlog + Tasks): William (2109688)
- Taking Notes of the meetings + proof of meetings: Shan (2295593)
- Software Sprint: Further work on Login Page + Registration: Yaakov (2153048) + Tawanda (2154154) Further work on the Home Page: Moshe (2153026)
- Github Wiki (Software Architecture and Design): Tawanda (2154154) + Shan (2295593)
- Continuous Integration: Shlomo (2153068)
- Test Driven Design: Sisonke? (2130644) + Shan (2295593) + William (2109688)
- Project Polish: Meeting on Sunday
Meeting Schedule
Setting up a schedule to meet on a regular basis for regular meetings/scrums. Lots of suggestions are being thrown around for the 2nd meeting to prepare for Rylan, here is what people have somewhat agreed upon but everything is still tentative.
- Every Friday straight after our meeting with Rylan
- Every Thursday at 1pm (To prepare for the meeting with Rylan)
- If we feel like we need more meetings we can schedule more throughout the week We have another meeting scheduled for Sunday (11 April) at 1pm. Future meetings we can discuss what everyone has done and if anyone needs help or is confused about anything we can help each other.
Sprint Review
09-April-2021
Members present:
- Rylan Perumal (instructor)
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Yaakov Brill
- Vusumzi Booi (meeting organiser)
Members missing:
- Sisonke Msezane
Meeting recap
Showed Rylan our Register + Log In page.
Make password inputs hidden (Instead of displaying 1234 it should be ****).
Add a navigation bar and put the logout button in there as well as the other buttons the site will have.
Add things to backlog THEN move it to the relevant sprint. Homepage with categories + on click modal should be priority on the backlog. Filling each product with product information should be at the top of the backlog/work on it for now.
Another Sprint meeting next week Friday.
Keep working on user stories until the Sprint Retrospective on Monday, then Friday we’ll talk about Sprint 2.
Proof of Scrum meetings:
- Retrospective: Type up documents/minutes + attach video of it
- Daily Scrums: Export chat logs (Like whatsapp/discord chat logs)
Sprint Retrospective is two parts
One part is the marking, the other is the interpersonal group retrospective meeting where we discuss
- What went wrong
- What could we have done better
- Issues among the team
Summarize into a word document afterwards
Documentation:
Need 4 sets of documents
- 1 for sprint planning (add 5th meeting, backlog of refinement, just make it a separate section, talk about everything that we did in the backlog like adding or removing things, moving things up or down)
- 1 for daily scrums
- 1 for review meetings
- 1 for interpersonal sprint retrospective
Preparing for Sprint 1 deadline For Monday we should get a finished version of our Sprint 1 product on Git, and even if we continue working on the project, we show the Sprint 1 finalized version on Git. For that sprint 1 release, it should be created so that Rylan can just pull the release and open it, and run the program perfectly.
Minutes should be uploaded as a word folder to Taiga or as a wiki article on GitHub (Shan is putting them on there).
- Sprint Planning: Backlog related things, requirements for the project
- Review Meetings: Rylan’s review of our planning and backlog
- Test Driven Design (And the GitHub Badge – 20 minutes into the relevant meeting): For now, you aren’t expected to implement tests yet, but for every user story there is an acceptance criteria (Answer the question who/what/why). The acceptance tests generally happen at the end of a design/deployment of your product.
Must have at least one acceptance test per user story, but most user stories have multiple. Basically these tests are: Given specific inputs like the correct/incorrect details what should happen afterwards? When you connect your Travis CI environment you can add a build status badge to your GitHub home page, that badge says what your current build status on the project is.
GitHub badges:
What they mean by badges is the Travis CI badge should say build successful and the code coverage badge should be a high %. Most important is that the badges are just there (even if for now they are a low percentage). For now, the Travis CI badge should just return build successful since we have no unit tests, but once we start adding them it will run the tests through our program and return a response to us.
User Stories Format + Acceptance Criteria (25:20 minutes into the relevant meeting):
From what it sounds to me, this is basically answering the question “Why is the user interacting with this?” so for a registration page it’s simple “To register an account”. But I’m not 100% sure since Rylan glossed over it. The acceptance criteria are just testing for all possible things that can happen. So for example Test 1 would be all correct inputs are given, and when you try to submit the details, the input is seen as valid while Test 2 would be if some part of the input is invalid and the program will spit out an error message. Rylan specifically mentions if the date of birth input is valid or invalid as acceptance criteria, so I’m not sure if you’d have a test for each input on a registration page for example but it would make sense to me that you would.
Sprint Retrospective with Tutor
12 April 2021
Members present:
- Ahmad Soni (Tutor)
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Sisonke Msezane
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
None
Yaakov shares his screen and is showing the tutor a rundown of our code and the database.
Confused our minutes sprint retrospective with the sprint planning and sprint review.
Need to have a top-down approach that explains our program and how it works, we sort of have it with our Readme + Description.
The focus of Sprint 1 for our project was more on the daily scrums and proof of them.
5 commits from all members, Tawanda and Sisonke didn’t do any commits. People who don’t commit need to be shown they are doing work at other places like on Taiga or in our documentation.
In future you need to have a release ready for each Sprint, for this Sprint we didn’t have a release ready prior to the meeting but could just make one for this retrospective.
Missing both Travis CI and Code Badges.
Soni suggests we try and have everything ready that we are still missing from Sprint 1 that we need to get down now like the Badges.
Daily Scrums
6 April 2021
Members present:
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Sisonke Msezane
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
None
7 April 2021
Members present:
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Sisonke Msezane
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
None
9 April 2021
Members present:
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Sisonke Msezane
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
None
Login and Registration Page Scrum
11 April 2021
Members present:
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Yaakov Brill
- Vusumzi Booi (meetings organiser)
Members missing:
- Sisonke Msezane
Yaakov posted code onto GitHub. Says readme can be improved.
Auto login functionality has been added. Passwords are now hidden on the webpage.
Checking how everyone progressed with the roles they were assigned to
- Wiki has been updated with meeting minutes + Home/Getting Started.
- Login/Registration was slightly refined.
- Meeting minutes were written and published on GitHub.
- Taiga user stories were updated and acceptance criteria added.
- Continuous Integration hasn’t been implemented yet due to technical difficulties. Test Driven Design hasn’t been worked on since it’s mostly for Sprint 2
Discussing the Taiga backlog + user stories, specifically wanting more things in the backlog.
Discussing Test Driven Design, specifically not having the badge yet for the marking rubric.
Lastly, everyone is asked to push something to GitHub and contribute to GitHub.
14 April 2021
Members present:
- Shlomo Brill
- Moshe Brill
- Sithole Tawanda
- Shan O’Neil (minutes writer)
- Yaakov Brill (meetings organiser)
- Sisonke Msezane
Members missing:
- Vusumzi Booi
This meeting was spent discussing the Sprint Retrospective with our tutor and discussing how we’ll assign work and finish everything so that Sprint 1 is ready and finished for our meeting with Rylan
Meeting roles assigned after discussing the Sprint Retrospective:
- Expand the wiki documentation to include a top down view of how to use the program: Tawanda
- Commits: Everyone needs to commit or if they can't tell us so we can make sure to credit their work on Taiga
- Releases at the end of every Sprint: Shan in charge of putting out a release after every Sprint and making sure we always have the most updated release put out on GitHub.
- Travis CI and Code badges on GitHub: Shlomo and Sisonke
- Taiga updates and adding more features that we are working on to the backlog: Moshe
Things from the Sprint Retrospective that have already been fixed:
- Confused on the difference between a sprint retrospective and sprint planning/review: Shan updated the wiki's