Meeting #8

Date

29/06/2020, Discord, 1500-1600HRS

Participants

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

Goals

Retrospective and Sprint Planning
Current Trajectory

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	@Tommy Truong (Unlicensed)	1 minutes	@Tommy Truong (Unlicensed) . put site map in creative folder @Tommy Truong (Unlicensed) . Update directors on the state of project (feedback from slack)	Meeting #7
Updates	Everyone	5 minutes	What have you been working on? Do you have anything blocking you? What do you plan to work on?	Jarvis: Working on menu design -> came up with two solutions. Blockers: lab Sergio: Finished the about page ticket. Not much over the weekend. Docker secrets and how to use them in our code -> realise that the repo is public. Security wise we need to check if anything that can compromise our system. Blockers: Thursday interview. Abiram: Started writing structs for json -> time format is weird from fb api. Access tokens expire after 60 days -> forget and server goes down. Blockers: Next week is pretty free. Paula: Finished sponsors page. Figure out a way to add the text without cluttering the layout. Contact us /engage page. Blockers: uni work done -> assignment not due for another two weeks. Jie:
Retrospective/Post mortem	Jarvis by virtue of spinner	30 minutes	https://www.atlassian.com/team-playbook/plays/retrospective	Since last retrospective wasn’t really remembered because of how rushed it was we are going back to 30 minutes as well as the Miro boards. Some things to reflect on: how was the sprint planning this time around. Chosen by the team instead of me.
Current trajectory	Everyone	20 minutes	Since we have overcome our most trialling period so far, I think we all deserve a break so the upcoming road trip will be a good chance for us to rest on our laurels. Thank you to Paula for getting the poll out and if we could get on that as soon as possible that would be great. For the tickets we have left in content syndication, let us review that together. This sprint will be about tying up lose ends and finishing everything off. After this we can have a discussion on next steps. Are pure layouts done? When can they be finished by? Do you need help? When can we start implementing by? Maybe start looking into creating tickets on Jira for these. How is Facebook API going? How will posts look? Keep in mind they are separate pages and as of right now we can have some information about the events in those post pages. Those are quite large tickets left. Since we still have a month left for the planned content syndication. Now is the time to look back at the epic story and see whether we have met requirements. CMS wise looks like it will be pushed back to original start date of August. Next sprint we may want to begin discussing CMS architecture.	Team formations? Team formations? Pure layout for all pages by end of sprint. Write tickets. Post moved into CMS epic story. Facebook API (hopefully a week and can start on security tickets again) Facebook API can be completed by the end of the first week -> at least will try. Sergio will look into working with the epic story requirements and seeing whether we have fulfilled this. Good to have because of his interview on Thursday. Will start CW-108 after thursday. Jie update so we know where he is at. A good thing for him to do now would be to look into the cms architecture and be ready to brief the team on what to do next. Design team will look into completing pure layouts for all pages into the next week. Next sprint we will look into working with how to get pure layouts implemented before the end of July. I think it will also give us a clearer picture of what people need to do in relation to the final showcase.





Feedback			Questions? Comments? Concerns?

Action items

@Tommy. Schedule a meeting with Leesa and Gordon about the need for facebook api permissions. Wednesday July 1st 2020.

@Tommy. Screenshot of retrospective and put in google drive resource folder.

@Abiram. Join Tommy to brief the directors on how to use the API.

@Sergio. To review requirements from the content syndication epic story and see whether the current system fulfills them.

@Jie. Will look at finishing off tickets and look into cms architecture.

@Paula and @Jarvis. Finish pure layout for an eventual move to implement such designs.

Decisions

Tickets and Estimation for Design Task will be recorded on Jira
Walking the board will be heavily enforced for daily standups.
Tickets with a sprint estimation of more than 2 points will now either be broken into separate tickets or subtask (depending on the size of the individual components)
At the end of every week design artefacts on adobe xd will be cleansed/refactored to keep only those that are relevant and introduce structure into the design process.
Reach out earlier on if stuck.