2022-05-31 Leads Meeting
Topics
Voting in new leads for fall
Follow up on last week’s new org structure
Onboarding templates
Notes
New Leads:
CV and FW need to find co-leads to replace their missing leads
New org structure:
FW: Looking into how to divide tasks up into PMs, still in discussion stage, lot of tasks are backlogged. Haven’t gone through senior member discussions.
EE: Don’t see real role for PMs and SMs, but looking at projects, update next week.
CV: Meeting to discuss assigining tasks, will solidify if they’ll be used. Update next week.
Mech: Will just continue PM role for phoenix.
SysInt: likely will not use PM
Ops: Unlikely this term
Onboarding:
FW: After bootcamp, add them to Asana, Github, follow a document to get environment setup. Do currently have a document with architecture written down in confluence. Get pointed to document but it’s not really codified. No onboarding sessions. Often friction w dev environment, people have to ask questions often and devs help them out.
EE: Assigining bootcampers to research tasks right now. Bootcamp is almost done. Confluence access given, altium access not given yet. EE has knowledge base.
CV: Onboarding doc to get dev environment setup, access to Asana, Confluence and Github, codified project selection stage. CV has a fairly weak knowledge base w outdated documentation. Friction w dev environment, some friction w knowledge.
Mech: Once bootcamp is reviewed, give them solidworks licenses, get them on grabcad, confluence. In confluence there’s onboarding documents for guidelines, documentation. No knowledge base to date.
Ops: Personally get to know everyone, conversation on what they want to work on, onboarding package provides organization for the resources, rundown of structure, allows for selection for projects.
Proposed onboarding framework:
Joining the team
Systems Access
Dev Environment Setup
Knolwedge Base
Project Selection
Onboarding Guide
Â