\uD83D\uDDD3 Date
Time: 9pm - late
Location : Online (teams)
\uD83D\uDC65 Minute Taker
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
Finish Sprint 2 ~ All issues on the board!
Finalise plan for Sprint retrospective topics - what went well, even better if , ways forward for sprint 3
\uD83D\uDDE3 Discussion topics
Item | Notes |
|---|---|
SQL DataBase - Demo of Joshua |
|
Team Update | Joshua : Working on the SQL database Michelle : Working on Communications Garvi : Sprint retrospective planning, finish table for interphase and refine user stories TONIGHT! Edward : Going to finish tests in the morning (has clocked out for tonight) - run purest on our main before we run (should have done it in the beginning - Joshua tried for 1 hour - didn’t get pytest working ~ only pylint |
Authentication | security : have an account for this environments: not share password for |
Workspace | Time : 9:45pm onwards. |
Psuedocode | Have no complex functions → ensure to note that there isn't and issue on the time complexity? |
Interface | From sprint 1 it was noted that we only needed to add more options ~ rather than add references to how we justified certain aspects on the difficulty of certain lanauges. Continue in the similar style of Sprint 1. |
Requirements | Security → finished. Need to consider points for performance → How is MVP related / embed |
✅ Action items
- Edward - Add Swagger to documentation
- Tay - add ER diagram + finish up tests for code
- Joshua - finish up code
- Garvi - overcheck the stack architecture updates + requirements
- Create diagram based on lecture notes
- Write pseudocode based on functions written + consider the time complexity