Skip to content

311 Data: Weekly Meeting Agenda 2026 #2064

@Rabia2219

Description

@Rabia2219

Overview

This issue tracks meeting agendas for the weekly 311 Data member meeting 2026

Agenda Quick-links

Quick link to bottom of page

Agenda Template

## YYYY-MM-DD - 311 Data Weekly Meeting
_[Back to Top](#)_

### AGENDA
_Timezones listed as Pacific Time._

- [ ] 7:00PM _5 min_ - Check-in
- [ ] 7:05 _5 min_ - Team announcements + updates
- [ ] 7:10 _20 min_ - Topic Requests
- [ ] 7:30 _30 min_ - Breakout Rooms
- [ ] 8:00 finished

### Topic requests/questions:

### Notes:

### Action Items:

### Resources/Instructions


---
### Attendees

####  Product Management
- [ ] Cotton
- [ ] Krystal
- [ ] Ryan

#### UI/UX Research
- [ ] Justyna
- [ ] Koorosh

#### UI/UX Design
- [ ] Joy
- [ ] Peter
- [ ] Shu
- [ ] Grace

#### Engineering
- [ ] Danielle
- [ ] Dorian
- [ ] Efren
- [ ] Lynn
- [ ] Melissa
- [ ] Joe

#### Content/Marketing/Copywriting
- [ ] TBD

#### UNASSIGNED
- [x] nobody

Resources

Previous Agenda Issues

PM Instructions For Board Review

PM will go through each team (engineering, design, research, product management) and check with the team lead that "all issues are in their right place". This will give team leads a chance to make simple board adjustments. Team lead can opt to do these adjustments within breakout rooms.

  1. Open up the 311-Data project board
  2. In the "Start Here" column, find the "Issues by role" card. This card has links that will filter the board based on each team. You will need to filter the board per each team to do the below steps.
  3. In "New Issue Approval", ask the lead if there are any issues that have been reviewed and can move out. Also ask if the lead needs someone to review issues here, try to delegate this to unblock movement of the issue.
  4. In "Icebox", review with the lead that all tickets here are indeed blocked, or unable to progress.
  5. In "Prioritized Backlog", go through and ensure nobody is assigned to these issues. Also try to ensure that they are properly ordered (from top to bottom) by milestone (once we have milestones set up)
  6. In "In Progress", make sure each issue has an assignee. Review issues with the lead that issues are indeed in progress, ask the lead to unassign and move back to "Prioritized Backlog" if there have been no updates on this issue.

PM Instructions for Opening Breakout Rooms

PM will need to manually open breakout rooms each session. This is done via the Host Key (do not share this!!!)

  1. Log into 1Password and access the HackForLA Zoom vault
  2. Select the relevant Zoom entry (to quickly check, open your google calendar invite, it should say "CTS Zoom3 is inviting you to a scheduled Zoom meeting", indicating you should use the Zoom 3 entry)
  3. Copy the Host Key into your clipboard
  4. Once you have joined the Zoom meeting, go to Participants > Claim Host
  5. Enter in the Host Key, and confirm that you are now the Meeting Host
  6. Find the Breakout Rooms option (iirc, More > Breakout Rooms)
  7. Create 4 breakout rooms and select "Let participants choose room"
  8. A window called "Breakout Rooms - Not Started" appears with the 4 rooms, unlabeled.
  9. Hovering over each row, you can click "Rename". Rename each row to be Engineering, Design, Research, and Product Management.
  10. Click Open All Rooms

Metadata

Metadata

Labels

Complexity: Smalltickets that are prescriptive, easily understood and executableFeature: agendatickets associated with recurring, weekly, monthly or scheduled agendas for documentationRole: Product Managementsize: 1ptCan be done in 6 hours

Type

No type

Projects

Status

Start Here

Relationships

None yet

Development

No branches or pull requests

Issue actions