You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 12
Next »
Leadership Team
Emma for ops vote
Ayoung stepping down
Team Direction
Comp Focusing all projects
What we don’t want to be
Members need to understand the system before they should be given the go ahead for very technical stuff.
Do we all agree with this? this is big …
This is an interpretation of Team Charter , do we agree?
my examples are mostly ee related but arguements extrapolate to all subteams
Systems Meeting
Next Major Projects
Plane for a while to learn and if it goes well, then VTOL for next AEAC
do AEAC this year (ofc lol) then once more, then SUAS? See how competition goes but
Meeting Notes Organization
No two pages can have the same name in confluence
We should standardize the organization and naming for consistency across subteams
I tried to stealth improve this, but most yall realized it was different and changed it back to what your subteam was doing before lol
I dont care what we do, but we should have a standard across all subteams to avoid the oddities this causes
Asana
Is anyone using this besides Daniel Puratich lol?
Any thoughts on this as a system or has AEAC sync and the director’s memories kind of replaced the need for a ticketing system? Leads kinda do the same thing for their subteams.
Project Managers & Senior Members
Can we give them their own chat and access to the email and such?
Nathan Green Daniel Puratich agreed.
Clear difference between sensior member and PM though?