We need to generate requirements better and assign ownership. imo best way to do this is generating system-wide requirements that break down into subteam requirements.
* We need to define sources of truth for the aircraft, i.e what's going on the aircraft, what is the aircraft going to do etc. This ties into the above.
* We need to shift teams to focus more on iteration, as well as integrating iteratively as early as possible. How should this look?
* How do we want to track progress and changes? We don't really use asana consistently now, not sure how consistent confluence use is. I want to know if we should shift systems or just use these more.
* What "rituals" do we want to adopt to make the above happen? I know going back to old gen meeting format (updates + discussion rather than just updates) might be popular, and I'm open to that. I think ticket grooming was a useful exercise for CV but unsure how y'all will feel about that.
* Checklists, we really need to document how this team works, this is more of an admin/team lead thing.
Manage space
Manage content
Integrations