September 14th, 2022 - Sync Up

Key Deadlines

• All M1 tasks due by Nov 20, 2022

  • Sub-team leads have discretion to adjust due dates for individual M1 tasks → please assign due dates to individual tasks by Sep 19, 2022

  • Open

    

    Any task in Milestone “M1” needs a rough deadline entered before Nov 20, 2022

     

  • Even for tasks that might take longer, we should aim for aggressive deadlines and push back if required

• Please send Austin your google (preferred) or school emails ASAP so I can add you as a contributor to the PM tool. Viewer link: https://docs.google.com/spreadsheets/d/1imf_OKjGeVF7BAd0x7Hlz-e45I1U33sTOc7G1meOANw/edit?usp=sharing

PM Tool Ticket Fill-out

• Skeleton tickets for all M1 tasks have been created

• Please fill out your tickets. See the following mech examples: https://uwaterloo.atlassian.net/l/cp/aL4qxzf1

• Open

  

  Note: If you have a ticket describing a task currently in progress, please fill out to the best efficacy possible (i.e. current status of CAN receiver, current status of new PDB design, etc.)

Electrical Tickets

Science Tickets

Software Tickets

Business Tickets

Firmware Tickets

@Jahnavi Thota please schedule a meeting with @Chanpakorn Chaiklahan and @Austin Tailon Huang to plan firmware term tasks and projects

General Meeting

• First general meeting of the term is on Sep 20, 2022 from 6pm to 7pm in E5-2004!

• Goal of this meeting is to achieve the following:

  • Review who we are and what we do (~3min)

  • Discuss competition roadmap and rough term timeline (~5min)

  • Review team structure (subteam break down, what does each subteam do) (~25min, 4-5min per subteam)

    • Main scope of work

    • Current projects

    • Past projects

    • What kind of tasks a new member could expect to work on

    • Note: I’d like subteam leads to fill in present this information during the general.

  • New members - how to get started? (training links)

  • New Member Q&A

• Chan and Austin will create slide format and DM when it is ready to fill

Leads Meeting Rescheduling

• It is critical that we find a meeting slot where all team leads can meet

• Most importantly, we need to find a time where at least one of the leads from the following subteams can meet and discuss weekly priorities and integration work:

  • Software

  • Science

  • Electrical

  • PM

  • Team Lead

  • Mechanical

• Note: Business and science are still incredibly important! That being said, integration and communication for the engineering subteams is inherently critical to get our rover up in running

• Ideally I want to meet with all leads weekly, but if that is impossible a common meeting slot with the groups mentioned above will be prioritized and a secondary meeting in smaller form factor with remaining leads will be scheduled separately.

• Please fill out your availability on the lettuce meet (one last time, i swear). Please note that this will represent your general weekly availability for the whole term, not this specific week.

Rules

• Rules for next years comp have been posted.

• Please read these by Sep 19, 2022

Action Items - Review

Here is a reminder for the action items from tonight's meetings for each sub team lead: