Meeting #6

Date

29/05/2020, 1300-1400HRS (AEST), Discord

Participants

@Tommy Truong (Unlicensed)
@Sergio Mercado Ruiz (Unlicensed)
@Paula Tennent (Unlicensed)
@Jie Chen (Unlicensed)
@Abiram Nadarajah (Unlicensed)
@Jarvis W. (Unlicensed)

Goals

Retrospective and Sprint Planning

Please add any discussion points that you would like to talk about below. Make sure to include as much context as you can, as well as an indication for how long you expect the discussion to last. Most discussion points won’t take more than 5-15 minutes.

Discussion topics

Discussion Point	Presenter	Duration	Context	Notes

Discussion Point	Presenter	Duration	Context	Notes
Follow up on action items from previous meeting		5	@Tommy Truong (Unlicensed) . Bring up the timeline of the design to the execs and come back with a plan. 16/05/2020, Plan by 18/05/2020 @Tommy Truong (Unlicensed) and @Sergio Mercado Ruiz (Unlicensed) . Look at API documentation (a specific dive into postman to document) @Sergio Mercado Ruiz (Unlicensed) and @Paula Tennent (Unlicensed). Finish off tickets from last sprint. @Jie Chen (Unlicensed)@Jarvis W. (Unlicensed)@Abiram Nadarajah (Unlicensed). Create tickets (Jira task) for a chosen user story. @Tommy Truong (Unlicensed) Efficient ways to collaboratively design @Sergio Mercado Ruiz (Unlicensed) . Look into Github secrets to help set up the STMP server.	Meeting #5
Updates	Everyone	5	What have you been working on? Do you have anything blocking you? What do you plan to work on?	Jarvis - workshop and session form for AdobeXD. Wants to do some more backend coding. Sergio - finished off mailing (integrated and working, fix lingering bug about mailing to deployment emails), swaggo instead of go swagger, nice guide from a repo that has a similar setup and stack. Fixes to the backend API handles-> implementing middleware (helps with authentication). Productivity might be slow because of interviews and university. -> API documentation and design Jie - no blockers, sprint went well everyone did great. Continue working on the frontend. Abiram - JWTs -> authenticating request, have a JWT when accessing db and sponsor test. UNSW authentication -> cookies Paula -> finished tickets from last sprint, testing for that, have been self learning about adobe, vue, go packages. Hope to do design.
Retrospective/Post-mortem	Spinner	30	https://www.atlassian.com/team-playbook/plays/retrospective	Security Deployments and testing Decoupling and refactoring Framework utilisation Documentation Deadlines https://miro.com/welcomeonboard/yLYnWMHRgxF2VnwuUuU7VuSa77zlDfWp84pv96oIYuFaQV9za2nOsDQlQLIBxHxN






Feedback			Questions? Comments? Concerns?

Action items

@Tommy Truong (Unlicensed) . Notification Streamline. Friday 29th May 2020

@Tommy Truong (Unlicensed). Sort out a when2meet. Friday 29th May 2020

@Tommy Truong (Unlicensed), @Paula Tennent (Unlicensed) , @Sergio Mercado Ruiz (Unlicensed) . Plan time to meet to talk about design decisions. 31st May 2020

@Tommy Truong (Unlicensed) . Figure out when the sprint starts after we have the dates for meeting times.

Decisions

Agenda items prepared in advance. Make sure agenda items are necessary items to bring up and who should be involved and used break up rooms on discord to do so.

Game night is a must and will find some time where everyone can attend.

Meetings time will now change based on this trimesters workload. Remove old information on the calendar and discord.

Links to documents when Tommy talks about a specific feature

Meetings will be timed with actual timer instead of just guessing

Story point estimates should never be changed during a sprint for exact statistics and help for later estimations

Notifications need to be streamlined

Code approvals should be at most 3 people anything important that affects the team be brought up in meetings and such. Tommy is always required and can be the only review if necessary.