311 Data Weekly PM Meeting 2025

[ryanfchase]

Overview

This issue tracks meeting agendas for the weekly 311 Data PM meeting (every Thursday at 7pm PST)

Agenda Quick-links

Agendas by Date

Instructions

Accountability Checks

For each member, add them as assignee in search criteria and paste as a link over their name:

Use this as a base URL

https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+-label%3A%22Feature%3A+agenda%22+-label%3AEpic+-label%3A%22Feature%3A+GitHub+Board%2FOnboarding%22

e.g.

• Ryan Chase

---

Template

Base agenda template

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

### AGENDA
_Timezones listed as Pacific Time._

- [ ] 7:00PM _5 min_ - Check-in
- [ ] 7:05PM _10 min_- Weekly Audit
- [ ] 7:15PM _45 min_- Topic Requests + Questions for Bonnie
- [ ] 8:00 fin

### Recurring Agenda Items
- TODO: replace with link to comment

### Topic requests/questions:
- [ ] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
- [ ] Review PM Team [project board](https://github.com/orgs/hackforla/projects/63/views/1?filterQuery=label%3A%22Role%3A+Product+Management%22)

### Notes:

### Action Items:

### Resources/Instructions

---
### Attendees:
- [ ] Ryan
- [ ] Cotton
- [ ] Bethlehem 

Pre-Work Checklist Template

### YYYY-MM-DD Recurring Agenda Items
- [ ] Update [311 Team Roster](https://docs.google.com/spreadsheets/d/1OsLDl7Ciwj7WjtzbgDz38g4kpOMNlUhdjlgzQxtQTvM/edit?gid=0#gid=0)
  - [ ] Open views and check if any members need action, see: https://github.com/hackforla/311-data/issues/1494
    - [ ] `check on website team member changes`
    - [ ] `inactive remove from website`
    - [ ] `Permissions to update-drive to viewer`
    - [ ] `Permissions to update-remove write`
   - [ ] Review all onboarding issues and see if any onboarding tracking comments are missing checkboxes
     - [ ] https://github.com/hackforla/311-data/issues/1561
     - [ ] https://github.com/hackforla/311-data/issues/1578
     - [ ] https://github.com/hackforla/311-data/issues/1580
     - [ ] https://github.com/hackforla/311-data/issues/1854
- [x] Weekly Label Check: https://github.com/hackforla/311-data/issues/1134
- [ ] Review each issue in the [Project Board Icebox (temporary view)](https://github.com/orgs/hackforla/projects/63/views/1?filterQuery=status%3A%22Icebox+%28on+hold%29%22)
  - [ ] Determine if the issue is still blocked. If unblocked, see if it's blocking ticket has a "Releases" section
  - Q: should we make an issue for Icebox Review weekly audit?
- [ ] All issues in New Issue Review/Approval have either: 
    - [ ] The `ready for...` label:  [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
      - If this link shows any issues in New Issue Approval, they need to be given the appropriate "ready for..." label
    - [ ] The `draft` label and assignee
- [ ] All issues in Questions column have a `ready for...` label [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
  - If this link contains any issues in Questions, they need to be given the appropriate `ready for...` label.
- [ ] All issues in Review column have a `ready for...` label [Project Board: Missing Ready for Labels](https://github.com/orgs/hackforla/projects/63/views/22)
  - If this link contains any issues in Review, they need to be given the appropriate `ready for...` label.
- [ ] Review the issues on [Project Board: Ready for Product](https://github.com/orgs/hackforla/projects/63/views/19)
  - [ ] address them now or add to this agenda to discuss. 
- [ ] For each issue in Questions that has `on agenda:` label, add a link to the question-asking comment from each new issue to the the agenda below
- [ ] Review any open Action Steps spreadsheets and keep up-to-date
  - https://github.com/hackforla/311-data/issues/1819#issuecomment-2655252608
  - https://docs.google.com/spreadsheets/d/14otyz2v-vYOnW9zJxpWTLSySTK4sJ2pDRO5wfre7e4Q/edit?gid=0#gid=0

[ryanfchase]

2024 Agenda

• 311 Data Weekly PM Meeting Agenda  #1546

[ryanfchase]

2025-01-27 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 3:00PM 5 min - Check-in
• 3:05PM 15 min- Questions from the team
• 3:20PM 40 min- Board Review, Topic Requests
• 4:00 fin

Topic requests/questions:

Questions about the project board (WIP)

• can we review our project board

Notes:

Action Items:

Resources/Instructions

• Epic of Epics: Pre-Launch and Post-Launch Assessment #1862
• Epic: About Page and Story of 311-Data #1756
  • Record Oral History of 311 Data #1757
  • Write copy for 311 Data Story #1758
  • PRD - Review PM Email Communications from 2020 to 2021 #1898
  • make a short-list of all data organizations doing meetups on a sheet

---

Attendees:

• Ryan
• Cotton
• Tracy

[ExperimentsInHonesty]

Product Manager Duties and Responsibilities

Regular PM Duties/Responsibilities:

• Weekly label check (weekly, before meeting, monthly, as needed, etc.)
• Add who each item is done with (alone, with PM team, etc.)

• Some that might be included:
  • Weekly issue audit (weekly)
  • Check/respond to questions (before meetings)
  • Review/respond to issues in question/review (weekly)
    • Respond to blockers/questions OR close completed issues (as needed)
  • Approve new issues (as needed)
  • Test issues (as needed)
  • Update product one-sheet (annually)
  • Update product roadmap (annually)
  • Setup meeting agendas (before meetings)
  • Update program process overview (as needed)
  • Onboard/offboard PM team members (and any other team members that don't have a lead) (as needed)
  • Request updates on issues (as needed)

Product Manager Duties & Responsibilities Sheet

[ExperimentsInHonesty]

• You want people to update their issue the day before the meeting
• you want to check the issues the day of the meeting, to ask for updates if they haven't updated
• add to pm agenda Check questions Review the Questions and Review column to make sure that every issue is tagged with a ready for... label (e.g., ready for product)
• you want to clear the questions' column, if at all possible, multiple times per week. It usually works best if you do it two days before the meeting (helps people do their updates) and the day of the meeting (reduces time during the meeting).
• You want to unassign anyone who has not given you an update in two weeks (unless you decided they could keep it when they went on a defined break).
• do new issue approval at same time as questions issues
• meeting minutes should be added to the agenda in real time.
• At the end of the meeting, make a new agenda from the template and carry forward any items that you didn't get to. (items should have checkboxes, so you know which ones get talked about).

[ryanfchase]

Bookmarkable links in SPAs: https://www.hackforla.org/?technologies=AWS