Overview

This is the general structure of Autonomy meetings.

Updates

General WARG announcements (e.g. events, general meeting, social).

• Add to meeting notes before meeting occurs

• 5 minutes

Autonomy announcements (e.g. new hardware, program changes, goals, action items for members, deadlines, flight tests).

• Add to meeting notes before meeting occurs

• 5 minutes

Each project manager goes through their project. Updates and plans (e.g. architecture and design decisions, priority changes).

• Add to meeting notes before meeting occurs

• 5 minutes

Breakout

The subteam splits into each project group in Discord VC and in the same room in-person. The Autonomy leads visit each breakout meeting to get information about the project’s progress.

• Order of visit is from least number of attendees to most.

Project managers make sure that Asana is always up to date.

Work session

The meeting is a work session while the Autonomy leads are not in attendance.

Unassigned tasks

For each unassigned task, provide a summary of:

• What the task is about

• Why it is desired (why should anyone care about completing it)

• Assign the task to any volunteers

More information on task assignment: DRAFT Task workflow

Progress

The Autonomy leads

Assigned tasks

For each assigned task, get a summary of:

• Progress

• Blockers

Each assigned task is at most 1 minute long. Do not discuss implementation detail.

Blockers are recorded in Asana and the task progress column set to Waiting.

Follow up and miscellaneous

TODO: Try for next meeting, possibly remove

Focus on topics that affect the entire subteam, projects, and/or a significant number of members.