Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Discuss sub-team roll and sub-team/team structure

  • Decide delegation of projects across the SysInt team

  • Identify strategies to handle groundstation

  • Discuss creation of “Knowledge Base”

\uD83D\uDDE3 Discussion topics

Time

Item

Notes

9am

What is the team role

  • PMs for cross team projects

  • Pilot integration & licensing (and training) & knowing the rules for flying so that we can identify regulations that could be of issue. Also to get pilot feedback on the state of the aircraft.

    • Basic license is good for testing

  • Systems level guidance on assembly (probably will happen anyway as we will be cross domain experts)

  • If there are sub-team tasks, we should be at sub-team meetings (But not always)


9:15am


Team structure

  • Sub-team representatives

    • Probably just team leads for high-level stuff

    • other members could be assigned for lower level (project specific) team info

  • Do we do technical syncs during general meetings?

    • Definitely not during weekly team leads

    • SysInt meetings for more specific details after general meeting perhaps

9:35am

Team delegation

  • Aidan to focus on ZP3

  • Andy to focus on FW testing drone

9:40am

Groundstation

9:45am

Knowledge-Base

  • Quick links for new team members as well as guides on PM

  • Andy thinks the “values” and “goals” sound good

9:50am

Avoid burnout - have fun

  • Both of us want to still do “hands on” work… even if that isn’t really feasible

  • In a bid to avoid burn out, we should make sure that we are doing things we enjoy

    • If we are feeling like we are missing out, bring it up, discuss strategies to reduce the burden (e.g. recruiting new team members?)

✅ Action items

  • Affirm the new team structure with the other team leads which is as follows:

    SysInt has representatives on each team that are responsible for being “experts” on any given cross-team project, and Team Leads are responsible for understanding the context behind all projects on their team and frequently discuss the status of (as well as potential dependencies or blockers) these cross-team projects.

    General meetings will include time for these discussions on project requirements, things learned, dependencies, etc. After general meetings, there will be SysInt team meetings where project owners will discuss in greater depth technical details of ongoing projects so as to not take up too much of the general team’s time (although all will be welcome to join and contribute).
  • Start planning on recruitment strategies
  • Develop pilot licensing / bring-up program
  • Develop requirements and project plans/timelines for ground station project
  • Develop Knowledge Base for any interested/new members

⤴ Decisions

  • No labels