mirror of
https://github.com/cse110-fa22-group29/cse110-fa22-group29.git
synced 2024-11-14 14:56:18 +00:00
82 lines
4.2 KiB
Markdown
82 lines
4.2 KiB
Markdown
# Sprint 1 Retrospective (11/14/2022)
|
|
|
|
## Team 29: Hackers1995
|
|
|
|
## Meeting Topic: Sprint 1 Retrospective
|
|
|
|
## Attendance
|
|
|
|
1. Rhea Bhutada
|
|
2. George Dubinin
|
|
3. Sanjit Joseph
|
|
4. Kara Hoagland
|
|
5. Arthur Lu
|
|
6. Mark Rheta
|
|
7. Henry Feng
|
|
8. Gavyn Etzel
|
|
9. Sanjit Joseph
|
|
10. Isaac Otero
|
|
|
|
## Meeting Details
|
|
|
|
- When: 11/14/2022 at 4:30PM
|
|
- Where: On Campus
|
|
|
|
## Agenda:
|
|
|
|
Discuss the review, share more detailed thoughts on sprint 1, and create some resolutions for sprint 2
|
|
|
|
## Sprint 1 Review Below (for convenience)
|
|
|
|
## Sprint 1 REVIEW
|
|
|
|
In collecting feedback during our final sprint the leads decided to ask members individually about their experience during sprint 1 to then summarize these responses. Each member was asked 4 questions with their summarized responses below:
|
|
|
|
### What do you think worked well in the first sprint?
|
|
|
|
We resolved to hold each of our sprint 1 meetings in person with a remote option available to members that couldn't attend. We really liked hanging out at the restaurants before working on the sprint and these experiences encouraged psychological safety in the group. We made some noticeable progress which was very encouraging for the group. Specifically, we figured out quite a bit of the CI/CD pipeline details which will help us going forward and we got a solid grasp of what the visual aspects and feel of the website will be.
|
|
|
|
### What can we improve on for the next sprint?
|
|
|
|
We ran into trouble early on due to some lack of planning for specific tasks. The members agreed that we should have spent more time defining tasks for specific members and defining goals for our different teams (frontend, backend, and unit testing). There was some concern over members not being able to attend all meetings and we think this could have been fixed with regularly scheduled meetings. Some technical concerns were the Javascript unit testing pipeline development lagging behind code development and pipeline requirements being unclear. Perhaps we should write out a style document to guide the automated linting process.
|
|
|
|
### What was your contribution to the sprint?
|
|
|
|
- Rhea Bhutada: Worked on the backend features including how to get create new review card page to open in a new window
|
|
- Gavyn Etzel: Helped with javascript side of things for website
|
|
- Henry Feng: Local image store and meeting support
|
|
- Sanjit: Default photo design and frontend star rating css
|
|
- Daniel: Helped modify html, added upload file feature
|
|
- Arthur Lu: Added JS Linting, Unit testing pipeline actions and rote a few simple unit tests; added deployment pipeline action
|
|
- Marc Rheta: Added HTML Linting and CSS Linting
|
|
- Isaac Otero: Low and mid fidelity wireframes of how our page will look like, Started working on homepage.html
|
|
- George Dubinin: Meeting notes, Repo organization, cookies
|
|
- Kara Hoagland: CRUD backend functionality
|
|
|
|
### Was there anything blocking your progress in the sprint?
|
|
|
|
Communication was challenging especially for members that would attend over Zoom and it was a challenge keeping track of each member's progress. We ran into some issues with the branching strategy with branches rapidly multiplying at points and the GitHub tags not working. The biggest technical issue we experienced involved Node and ES6 compatibility issues.
|
|
|
|
Overall we feel that sprint 1 was a success with many lessons learned. Our enthusiasm for the project is only building and we are excited to get back into it with sprint 2 after a much needed short break.
|
|
|
|
## Resolutions
|
|
|
|
- Divide up tasks and assign tasks to members
|
|
- Define objectives for team groups (frontend, backend, and unit testing)
|
|
- Scheduled meetings with more notice and keep meetings at a more central location so that more members can attend
|
|
- Get the unit testing modules up to date
|
|
- To-do: create a style guide
|
|
- Heed the styles and documentation (to avoid linter issues)
|
|
|
|
## Early Issues
|
|
|
|
- restructure local storage to store individual (key, review) pairs rather than storing data under one key (current schema)
|
|
- implement a file upload system (think canvas file upload)
|
|
- add a cuisine attribute for tagging and filtering
|
|
- Create UI buttons and low fidelity css
|
|
- Unit test all the above
|
|
|
|
## End Time
|
|
|
|
- 11/14/2022 at 5:00PM
|