Meeting #5

Date

15/05/2020 - 1300hrs(AEST) to 1430hrs(AEST) - Google Meets

Participants

@Tommy Truong (Unlicensed)

Goals

End our first sprint and updates from all members
Retrospective/Postmortem
Deciding where to go from here

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	Everyone	15 mins	@everyone besides Paula and Sergio. Work on strategies to handle premortem problems. 07/05/2020 @everyone Look at logos in subcomm Slack channel @Tommy Truong (Unlicensed) Project proposal. 6/05/2020 @Tommy Truong (Unlicensed) Documentation in the readme files on Docker files and Jenkins. 01/05/2020 @Tommy Truong (Unlicensed) Add everyone into Range 02/05/2020 @Tommy Truong (Unlicensed) . Integration between Jira, Jenkins and GitHub @Tommy Truong (Unlicensed) . Team mascot @Stories Change the user stories into tickets @Design Team. Look through User Stories, give suggestions to Stories team. 03/05/2020 @Tommy Truong (Unlicensed) Complete documentation for next years team - readmes, vision boards, progress reports	Meeting #4
Updates	Everyone	15 mins	Round robin daily stand up style check in What have you been working on? Do you have anything blocking you? What do you plan to work on?	Jie: > working on: design of the stylescapes, basically done. Created an architecture guide (everyone give feedback) > blockers: - Jarvis: > working on: refining stylespace, thinking about next steps of design > blockers: overloading with work Abiram: > working on: done stylescape > blockers: - Paula: > working on: assigned user stories, finalising tests > blockers: pressure on getting it done Sergio: > working on: finishing up tests for the mailing task > blockers: coding interview on Monday that he needs to prepare for
END OF OUR FIRST SPRINT	Tommy	10 mins	How is everyone feeling at the end of the sprint? Pacing, time commitment, difficulty? What’s one thing you’ve learnt about other team members? What do team members want to do next? e.g. tell Tommy what do you feel like doing and we will change the schedule accordingly	General: > Deadlines are not set in stone and are flexible. They are not strict but would be nice to adhere to. > At this point we should focus more on code (refactoring, testing, etc); towards the end we should focus on design in preparation for deployment. Design: Sitemap and wireframe deadlines could be pushed back Roughly 2 months to complete the design. We need to plan out everything before we do it. The team learns fast and comes up with impressive designs. Coding The team is helpful, enthusiastic and open to learning new things. What do we want to do next: > Abiram: coding > Jarvis: coding > Paula & Sergio: finish current coding ticket and do more creative work > Jie: review people’s code
Retrospective/Post-mortem	Tommy for the first one, Scribe for all subsequent ones	30 mins	https://www.atlassian.com/team-playbook/plays/retrospective	https://miro.com/welcomeonboard/4Jv9WMEcFKIjAvV8IEVjzKaT6cQAswPVGJSLyOnjF3dxdAX4RbpoyKbH6sfjFHWL
Next Steps	Tommy	10 mins	What will our next steps be? Backend Frontend Design	Security Deployments and testing Decoupling and refactoring Framework utilisation Documentation Deadlines > Jira is the point of reference for backend deadlines. > Decoupling and refactoring > Implement OWASP methodologies
Decisions	Everyone	10 mins	What do people want to do?	> Write stories now and review/choose which ones to look into tomorrow.



Feedback			Questions? Comments? Concerns?

Action items

@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.

Decisions

Everything related to coding should be a subtask. Everything else is either a comment or is mentioned in the description. Don’t overuse subtasks!
Have an ‘update’ meeting on the Friday between sprints to offload the content required to be covered at the end of the sprint. Leaving retrospectives for sprints to be left till the end of the sprint. (Pin in this decision in the sense of getting reactions from the whole team about having daily plus two friday meetings during the sprint)
Begin to track security as a feature to our coding and design. Security will now be a part of every coding decision we make and best web security practices and OWASP methodologies implemented.

Every other day standup now will involve everyone as well as be timed to controls ramblings - How to conduct productive standups can be located here https://martinfowler.com/articles/itsNotJustStandingUp.html

Once a go ahead from the directors and execs are given, we gather every page and create a final mockup and site map thinking from the perspective of the user.

Range will be used more frequently by all members to aid in cross team collaboration.

A better utilisation of our frameworks will begin which means reading into echo and vue documentation to better understand their features