/
Meeting #4

Meeting #4

Owned by Tommy Truong (Unlicensed)
Last updated: May 12, 2020
2 min read

Date

01/05/2020, 1300hrs -> 1500hrs (AEST), Google Meets

Participants

  • @Tommy Truong (Unlicensed)

  • @Abiram Nadarajah (Unlicensed)

  • @Jie Chen (Unlicensed)

  • @Sergio Mercado Ruiz (Unlicensed)

  • @Paula Tennent (Unlicensed)

  • @Jarvis W. (Unlicensed)

Goals

  • Catch up on each teams progress

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

10 mins

  • Strategies for premortem problems

  • How was local deployment? Did anyone have a chance to use the Dockerfiles?

  • Meeting #3

  • Sergio, Paula added some strategies

  • Tommy has configured Dockerfiles, documentation to come

Updates

Everyone

20 mins

  • What have you been working on? 

    • User story updates

    • Mood board and Stylesheets

    • Range

  • Do you have anything blocking you?

  • What do you plan to work on?

  • Jie: Social moodboard, good progress, meeting with team tomorrow (2/5/20)

  • Exams/assignments may block some people

  • Designs expected to be done by June at the earliest

  • Introducing Range - daily check-ins to account for timezones/clashes blocking attendance from standup meetings

  • User stories:

    • Under Content Syndication on Jira

Plan for the sprint

Tommy

20 mins

  • Again we will split into groups of three and this time the roles will be 

    • Sitemap and Wireframes

      • Adobe XD

      • Behance

      • Design principles

    • Implementing user stories for the first sprint

      • Documentation

      • Git workflows

      • Testing - unit, integration and functional

      • Writing code

      • Refactoring

  • Continual testing

    • Next team should have working code

  • Thorough documentation

  • Code for the rest of the sprint after writing tests

  • Commit as often as possible, use Git workflow 

    • PR only if working on your branch into dev branch

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Feedback

Everyone

30 mins

  • Questions?

  • Comments?

  • Concerns?

Questions about Docker

Action items

@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

Decisions

  1. Design team continues to work and plan towards completing sitemap and wireframes by the earliest beginning of June and latest middle of June
  2. Users stories for first sprint were decided -> user stories will be changed into tickets for better workflows
  3. Adoption of Range as a complement to daily stand-ups