311 Data Weekly PM Meeting Agenda

[MBasil03]

Overview

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

Agenda Quick-links

• [ ] TODO add all dates (see example)

2023

• [ ] August 10, 2023

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

## 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

### Accountability Checks

### 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 

[bberhane]

2024-04-04 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 10 min- Recap of product planning meeting
• [ ] 7:15PM 20 min- Updates on new tickets/bugs from last week
• [ ] 7:35PM 25 min- Review pre-launch checklist + action steps
• [ ] 8:00 fin

Topic requests/questions:

Notes:

Use standard map pin over house when typing in address and house shows up, should be pin (do we need to make a ticket for this?)]

Come up with a script for the demo (product task) for testing (future task)

Notes from Ryan & Robert during meeting

New Tickets

Spike: Investigate "dropped clicks"

there might be a correlation between slow-loading map details (when zoomed in) and dropped clicks

as in, I noticed I had dropped clicks while the map detail was becoming more granular

map may be attempting to load data, slowing our app down

Confirm consistent boundary fill when de-selecting a boundary (fix inverted colors)

Robert is working on a ticket for this

Support pre-2024 data (see existing ticket)

Address slow load times for large time spans (no ticket for this yet, see notes from ^^ that ticket)

Bonnie also suggested: large date ranges with few request types VS small date ranges with all request types could we load just one / subset of request types

consider a form on page-load that allows user to pick the initial subset of data

Action Items:

Resources/Instructions

Pre-Launch Checklist

Action Items List

Zoom Link

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem
• [x] Robert

[bberhane]

2024-04-11- 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 20 min- Updates from attendees
• [x] 7:25PM 35 min- Topic requests
• [x] 8:00 fin

Topic requests/questions:

• [x] Audit design tickets?
• [x] Creating new milestones?
• [x] Discuss Holly's research script and updates from Research
• [x] Update on UX/UI design system approach
• [x] Update on dev lead help

Notes:

From Robert: Feedback for testing document:

• Not the correct logo for the questions
• neighborhood council logo - get rid of that
• DO NOT reach out to expunge assist
  • Reach out to the INTERNSHIP and TDM calculator team
    • Ask them how to structure testing
    • https://github.com/hackforla/internship/wiki/Research
• No personal identifying information
• Finalize the research plan
• USE the internship research plan
• Demo is to get people on board, should be interactive
• Review objectives of research plan before providing feedback on questions

General notes:

• Push design team to do updates to design system while dev fixes bugs and research tests
• Audit design tickets (where are things, who’s working on what, how far along are they) (make all tickets up to date)

Action Items:

• [ ] Create tickets for research that are Hack for LA compliant
• [ ] Make research plan Hack for LA compliant
• [ ] Create ticket for design to update letterhead (see instructions/resources below)

Resources/Instructions

Research Q's Product Management Wiki: PMs, please review and reference as needed Research Plan Template: PMs to review Wiki, then provide feedback on current 311 Data Research Plan Design Process Overview: Create ticket for design to update letterhead with up-to-date graphics and remove Empower LA Current Research Plan: Review plan and provide notes based off research Wiki

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem
• [ ] Ahmed
• [x] Robert

[bberhane]

2024-04-18 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [ ] 7:00PM 5 min - Check-in
• [ ] 7:05PM 20 min- Updates from Bonnie/Any other attendee
• [ ] 7:25PM 35 min- Topic requests
• [ ] 8:00 fin

Topic requests/questions:

• [ ] Design audit (thank you, @cottonchristopher!)
• [ ] Insights from our PM and research spike (should we make a ticket for this?)

Notes:

Action Items:

• [ ] Determine whether we have an updated 311 Data letterhead in the Drive; if not, make design ticket request
• [ ] Create tickets for research that are Hack for LA compliant; we'll need to model research ticket templates based off Internship Research ticket

Resources/Instructions

• See also Setup Structure template on GitHub Roadmap

---

Attendees:

• [ ] Ryan
• [ ] Cotton
• [ ] Bethlehem
• [ ] Ahmed
• [ ] Robert

[bberhane]

Meeting was canceled due to scheduling conflicts and illness

[bberhane]

2024-04-25 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [ ] 7:00PM 5 min - Check-in
• [ ] 7:05PM 10 min- Attendee Updates
• [ ] 7:15PM 20 min- Offboard Ahmed
• [ ] 7:35PM 25 min- Topic requests
• [ ] 8:00 fin

Topic requests/questions:

• [ ] Insights from our PM and research spike
• [x] Review demo notes from UX design
• [ ] Recap of research demo
• [ ] Launch discussion

Notes:

TODO:

• [x] Beth to complete - https://github.com/hackforla/311-data/issues/1701 before product planning meeting

Action Items:

• [ ] Determine whether we have an updated 311 Data letterhead in the Drive; if not, make design ticket request
• [ ] Create tickets for research that are Hack for LA compliant; we'll need to model research ticket templates based off Internship Research ticket
• [ ] Update - https://github.com/hackforla/311-data/issues/1693 once previous action item completed

Resources/Instructions

• See also Setup Structure template on GitHub Roadmap

Anna's Screenshot

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem
• [x] Robert

[bberhane]

2024-05-02 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 20 min- Updates from attendees
• [ ] 7:25PM 35 min- Topic requests
• [ ] 8:00 fin

Topic requests/questions:

• Review dev tickets:

• https://github.com/hackforla/311-data/issues/1716

• Review research template:

• https://github.com/hackforla/311-data/issues/1715

Notes:

Action Items:

• [x] Create labels for three research plans

Resources/Instructions

---

Attendees:

• [ ] Ryan
• [ ] Cotton
• [ ] Bethlehem
• [ ] Robert

[ryanfchase]

2024-05-09 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 30 min- Topic Requests
• [x] 7:35PM 25 min- Discussion / Questions for Bonnie
• [x] 8:00 fin

Topic requests/questions:

From Ryan

• [x] New open role in Engineering CoP (do this together??)
• [x] Discuss Research Plan Template w/ Cotton
• [x] Research to utilize usertesting.com, they are prepping questions for Research CoP
• [x] PM team to come up with text for service requests Info popover

Notes:

Action Items:

Resources/Instructions

• usertesting platform link: https://www.usertesting.com/
• research gdrive v1.2 testing folder: https://drive.google.com/drive/u/0/folders/19oXFkecEclzt4HQvL3tMOY4L0N8pqpRa

---

Attendees:

• [ ] Ryan
• [ ] Cotton
• [ ] Bethlehem
• [ ] Robert

[bberhane]

2024-05-16 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 20 min- Updates/Qs for Bonnie
• [x] 7:25PM 35 min- Topic Requests
• [ ] 8:00 fin

Topic requests/questions:

• [x] Review research plan ticket: - https://github.com/hackforla/311-data/issues/1729
• [x] Review current research tickets since many were done retroactively, including - https://github.com/hackforla/311-data/issues/1693
• [x] Any update on new engineering lead?

To Do:

• [x] Offboard Robert :(
• [ ] Weekly label audit: - https://github.com/hackforla/311-data/issues/1134
• [x] PM to get in touch with data science CoP about the demo; can we do a demo with them during regular community of practice meeting?

Notes:

Action Items:

Resources/Instructions

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem

[bberhane]

2024-05-23 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 15 min- Weekly Audit + Updates
• [x] 7:20PM 40 min- Topic Requests + Questions for Bonnie
• [x] 8:00 fin

Topic requests/questions:

• [x] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
• [x] Update on engineering lead
• [x] Update on Data Science CoP
• [x] How to increase engagement in meetings

Notes:

Action Items:

Resources/Instructions

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem

[ryanfchase]

Yes, this is THAT PM meeting notes post

Notes from Meeting

Mid/Low Priority

• next h4la onboarding (6/3), consider recruiting then
• new issue: we need to modify the dropdown list such that it tells you how much data there is
  • e.g. prior year
  • double chevrons on datepicker to fastforward to first month / last month
  • one way to indicate that we have a datepicker: "Custom Date Range"
• add to FAQ: "Why do some neighborhood councils overlap?" A: if they share a park/school/historical site/landmark/public use
  • Link to Full List of shared spaces (EmpowerLA site)
• Accountability and Support Check
  • https://github.com/hackforla/internship/issues/101

High Priority!!

• 311-data.org needs to match messaging of "we are not City of Los Angeles", similar to github pages site
• Loading Modal shows up when visiting non-map url (only show this for map page!!!)
• Download csv for a particular Request Type and Period
  • Just address + number of requests
  • need some messaging that we just want them to select one Request Type
  • importantly: we to give them some suggestions as to what to do with the data (e.g. making use of public services aka bulky item pickup -- let them know what the cost is for using it if any) (this is what you can do with the data, this is one example (bulky items)
• Contact Form: (see Website's Wins AppScripts)
  • consider GithubSecrets
  • embed a Google Forms
  • use a google App Script to open a github issue with label new-contact-submission
  • Example of the Website's Wins page form
  • All tickets (closed) generated by Website team's Wins page bot
  • How the Wins page work
  • perhaps add a dashboard to see if there are any unanswered emails

New project for Design (Lowest Priority)

• visual story / visual case study for "Story of 311-Data"
  • talking to EmpowerLA, invited reps to in-person sessions (use pictures of whiteboards), but then nature of neighborhood involvement changed (zoom mtgs), site wasn't as accessible and prompted us to do user research
  • talk about need to make data and code more accessible
  • possibly interview Bonnie
• design system

Future Ideas

• (wait for Research tests to validate this) possibly show NO data on page load
  • load data in the background, only show loading modal when they ask for data

PM Homework (Try and complete this by next Wednesday)

• prepare to add Weekly Audits to General Meeting agenda (ask team members if we need to recruit, ask about participation)
• we need to create a Story Points and Timeline spreadsheet (we have a version of this, but we need to come up with a way to make it "live")
  • maybe room for us to make an automated version of this, similar to automations in Website team
  • in the beginning, we'll just need to come up with a system for tracking these by hand, and updating them by hand

[bberhane]

Response to add to FAQ: "Why do some neighborhood councils overlap?" A: if they share a park/school/historical site/landmark/public use Link to Full List of shared spaces (EmpowerLA site)

Please note that answer appears on pages 3 and 4 of 27

Link to EmpowerLA PDF

[bberhane]

@ryanfchase I don't have that issue with the loading modal appearing on website pages other than the map page. Can we recreate the issue, or did someone fix it already?

[ryanfchase]

@bberhane I am able to reproduce the issue by directly visiting a non-map url of our site!

e.g. https://hackforla.github.io/311-data/#/about

Screenshot of modal outside of map


[bberhane]

@ryanfchase Thank you! I'll go ahead and make the ticket

[bberhane]

2024-05-30 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [ ] 7:05PM 20 min- Topic requests/questions/updates from attendees
• [ ] 7:25PM 35 min- Review updated pre-launch checklist
• [ ] 8:00 fin

Topic requests/questions:

• [ ] Research update
• [ ] Discussion on accountability check/Should we follow the website team's agenda for general meetings?
• [x] Confirming the date picker isn't limited to 30 days of data
• [ ] TBD tickets on pre-launch sheet (see below for link)
• [ ] Automated system for pre-launch ticket check?

TODO

• [ ] Weekly Audit: https://github.com/hackforla/311-data/issues/1134

Notes:

Action Items:

Resources/Instructions

Pre-Launch Issue Point Spreadsheet V2 Zoom Link

---

Attendees:

• [x] Ryan
• [ ] Cotton
• [x] Bethlehem

[bberhane]

2024-06-06 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:15PM 55 min- Topic Requests + Questions for Bonnie
• [ ] 8:00 fin

Topic requests/questions:

• [x] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
• [ ] Restructuring meetings/agendas
• [ ] Brainstorm/create remaining pre-launch tickets

Notes:

Action Items:

TODO:

• [x] Make ticket to begin board migration process
• [x] Add "ETA" column to story points spreadsheet
• [x] Make date picker restriction ticket (prevent future date selection): https://github.com/hackforla/311-data/issues/1759
• [x] Adjust contact form epic
• [x] Add Bethlehem to product planning meetings
• [x] Follow up with data science CoP and admin

Resources/Instructions

Pre-Launch Issue Point Spreadsheet V2 GitHub Project Board Migration Issue Zoom Link

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem

[ryanfchase]

Ryan's Notes from 6-6-24

• [ ] change 311-data-userinterviews to just 311-data-ux@hackforla.com
• [x] figure out zoom transcription (I think Bethlehem found out this is only available on zoom biz accounts)
• [ ] Experimental Repo (aka "throw everything in the data folder" repo)
  • [ ] create a branch that replaces HuggingFace data source with a local data source
  • [ ] when ready for demo, prepare to fork and port to a new github repo
  • [ ] get jessica chang's website writeup on not destroying git blame on copy repo
  • [ ] prepare to compare load times for each model
  • [ ] Look into React static site bundling

6-6-24 agenda leftovers

• [x] ~Restructuring meetings/agendas~ Add accountability check demo to upcoming general meeting agenda
• [x] Brainstorm/create remaining pre-launch tickets: https://github.com/hackforla/311-data/issues/1674#issuecomment-2164660917
  • [x] Add "ETA" column to story points spreadsheet
  • [ ] RC: I think we could take the pre-launch spreadsheet ticket and turn it into a live-forever ticket where we post comments with the new pre-launch ticket that is created so we know to update the spreadsheet
  • [ ] (just an idea) if we move forward with bot automations (like internship team?) we can automate this so we don't have to manually do it. But in the meantime we'd have to maintain this ourselves
• [x] Make ticket to begin board migration process <-- started a draft tix for you
  • [x] Draft ticket: https://github.com/hackforla/311-data/issues/1751
  • [x] @bberhane wanted to spearhead this. go Bethlehem!
• [x] Make date picker restriction ticket (prevent future date selection)
• [x] Adjust ~contact form~ csv export epic, @cottonchristopher is assigned: https://github.com/hackforla/311-data/issues/1738
• [x] Add Bethlehem to product planning meetings
• [x] Follow up with data science CoP and admin

[ryanfchase]

Notes from PM CoP

Note: no need to copy this into next agenda, but perhaps these can go into a wiki one day

• watched some teams go through their migration. I made the migration ticket for us to track this
  • Use this filter to see all non-issue cards: https://github.com/hackforla/311-data/projects/10?card_filter_query=-is%3Aissue+-is%3Apr
• we need to ensure "Teams are migrated correctly" when we finally do the migration
  • make sure that only 311-data-write, 311-data-maintainers gets migrated, all others are removed
  • Check to see if PMs have correct access here: https://github.com/orgs/hackforla/teams
• new Views feature
  • all boards start with a default view, make sure this view has all the "required fields" bc duplicate views (e.g. for individual teams) will inherit these features
  • all views are public bc they belong to the org
  • we'll want to create views for each team (PM, DEV, UXR, UIUX)
  • Note for everyone when creating Views for your team: you can add the filter "assignee:@me" to any view to turn it into a "My Issues" version of that view, so the signed in user only sees issues they are assigned to in that view.
• new Table view
  • figure out what they do
  • basically it's just different ways to organize the same project data

Links / Resources

• https://docs.github.com/en/enterprise-server@3.9/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board
• GitHub docs for Projects filters (current): https://docs.github.com/en/enterprise-server@3.9/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects

[ryanfchase]

For next week's agenda

Bonnie Action Items

• [ ] Bonnie to show us how to prune the 311-data-write team (there were 112 members, high priority!)
• [ ] Question about project board:
  • [ ] What do we do with "extraneous" boards
  • [ ] I think it was advised that we could just migrate the board OR throw it away

[ryanfchase]

For tomorrow's agenda. Let's try and follow up with UIUX team on this comment on base designs affecting new feature designs -- to me this feels like an urgent problem that we need to fix on the design team.

[ryanfchase]

Adding some TODO items for tomorrow's agenda, based on Bonnie dropping into dev room. Whoever makes the next agenda, please grab all comments up until the previous agenda post ... it seems my comments are starting to pile up.

Action Items

Consider adding these steps here: https://github.com/hackforla/311-data/issues/1753

• [ ] 311-Data bot, do these by next week (OR at Bonnie 1 on 1 interview)
  • [ ] PMs come up with a human name (bot names might get flagged by github)
  • [ ] Admin makes a hackforla email address
  • [ ] PM team adds credentials to 1Password
  • [ ] PM team creates github account
  • [ ] Bonnie/Admin adds bot's github to HackForLA org
  • [ ] PMs to add team permissions to this bot
  • [ ] finish automation implementation, as outlined in this dev ticket and this PM ticket

Consider adding these steps here: https://github.com/hackforla/311-data/issues/1757

• [ ] Scheduling a meeting with Bonnie for the Story of 311 Data page
  • [ ] use the Bonnie scheduling sheet to pick a time
  • [ ] pick one PM to conduct the interview

Trying to close old tickets...

• https://github.com/hackforla/311-data/issues/1737#issuecomment-2154210860

[ryanfchase]

Computer is running out of battery, but if we wanted to be really prepared for tmo, we should finally look through last week's product planning meeting notes and copy over...

Bullet points that are empty AND they do not have a ticket associated with them.

Because those bullet points means someone (usually Bonnie) has asked for that, and we are not currently tracking it.

[ryanfchase]

2024-06-13 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [ ] 7:05PM 10 min- Weekly Audit
• [ ] 7:15PM 45 min- Topic Requests + Questions for Bonnie
• [ ] 8:00 fin

Accountability Checks

• [x] Ryan
• [x] Bethlehem
• [x] Cotton

Topic requests/questions:

Firstly...

• [x] Review PM Team project board

Then...

• [x] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
• [x] Resolve Bethlehem can't edit wiki: https://github.com/hackforla/311-data/issues/1755#issuecomment-2163917858
• [x] review expanding action items: https://github.com/hackforla/311-data/issues/1758#issuecomment-2164076054
• [x] close ticket: https://github.com/hackforla/311-data/issues/1754
• [x] expand action items (from reference): #1753
• [x] review expanded action items: https://github.com/hackforla/311-data/issues/1757
• [x] review export button: https://github.com/hackforla/311-data/issues/1695#issuecomment-2166876925

Finally...

• [x] Review Design Team design system, latest status (last status update here)

Notes:

Action Items:

Bonnie Action Items

• [ ] Bonnie to show us how to prune the 311-data-write team (there were 112 members, high priority!)
  • [ ] Use this ticket: https://github.com/hackforla/311-data/issues/1494
• [ ] Question about project board:
  • [ ] What do we do with "extraneous" boards
  • [ ] I think it was advised that we could just migrate the board OR throw it away

PM Team

• [ ] 311 PM member needs to attend tomorrow's PM CoP, see Bonnie's slack message
  • [ ] we will be covering how recruitment will change since the project board were migrated
• [x] PM team needs a "saved reply" for "please provide ETA, etc" for accountability checks
  • [x] ETA-ing: for a given volunteer, use their update to provide an updated ETA which can be put into the Story Point spreadsheet.
  • [x] add a checkbox for the "saved reply" to update the Story Point spreadsheet with their provided ETA

Resources/Instructions

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem

[bberhane]

Investigate why @bberhane and @cottonchristopher don't have "Settings" for 311 Data project repo

[ryanfchase]

Investigate why @bberhane and @cottonchristopher don't have "Settings" for 311 Data project repo

Per the last bit of our meeting, I think we need to add ya'll to the admin and maintainers teams for 311

• https://github.com/orgs/hackforla/teams/311-data-maintainers
• https://github.com/orgs/hackforla/teams/311-data-admins-admin

[ryanfchase]

Meeting notes from PM CoP

Open Roles Issues

• Open Roles Template on h4la wiki
• we have to make sure that they are formatted/labelled THE SAME....
  • basically when creating an open role, we add the issue to BOTH
  • h4la open roles board (under the correct CoP's view)
  • 311 Data board
  • we all use a primary issue as an epic
  • PMs will likely always stay assigned (bc its an epic, and to periodically check on it)
  • website's example: https://github.com/hackforla/website/issues/7005
  • 311 Data's primary issue: https://github.com/hackforla/311-data/issues/1765
• create a template for making the "New issue Open Role Issue post" (?)

FAQ

• Q: as we're using this template, why don't we just make our own customized version?
  • A: volunteers/teams will start asking for or offering more information
  • e.g. a link to all open issues for that role

Homework (NEXT WEEK)

Preliminary...

• [ ] Go to open roles boards and look for any post from your team.

For each open roles boards and for each of your team's open role cards...

• [ ] Communicate with team leads to confirm that this role is still open
• [ ] Copy the link to that open role card and paste it as a comment on your Recruit volunteers for team open roles issue/epic

Then for each of those comments...

• [ ] Edit comment to utilize the template from Resource 1.01 Community of Practice WIKI, Open Roles Templates, Secondary Issue
  • [ ] modify to utilize relevant info from within the open role card
  • [ ] modify to include any team specific requirements
  • [ ] take note of how you're modifying it -- I think Bonnie wants to keep this info so we can adapt the secondary template to serve all team's recruitment needs in the future
• [ ] Follow instructions from - [ ] Open a new issue by using the Open Role template (Resource 1.02) onwards...

Let me know if this is accurate!

Screenshots

Labels for parent issue  Labels for child issues 

[bberhane]

Add to 6/20 PM meeting: Research needs access to Figma Review new milestones

[bberhane]

2024-06-20 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [x] 7:05PM 05 min- Weekly Audit
• [ ] 7:10PM 50 min- Topic Requests + Questions for Bonnie
• [ ] 8:00 fin

Accountability Check

• [x] Ryan
• [x] Bethlehem
• [x] Cotton

Topic requests/questions:

• [x] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
• [x] Review PM Team project board
• [x] Research needs access to Figma: https://github.com/hackforla/311-data/issues/1777
• [x] Review updated milestones
• [x] Data Science CoP demo (6/24/2024 Monday 7pm Pacific) – who's going
  • [x] Ryan
  • [x] Bethlehem
  • [ ] Cotton
• [x] Update on open roles

Notes:

Action Items:

• [x] Add Bethlehem + Cotton to admin and maintainers: https://hackforla.slack.com/archives/C01Q24YF56J/p1718940475802799
• [x] Bethlehem to generate Qs for oral history: https://github.com/hackforla/311-data/issues/1757

Re-check accountability checks

Design

• [ ] Anna
• [ ] Paul
• [ ] Shu
• [ ] Angela
• [ ] Allison

Research

• [ ] Holly
• [ ] Brian
• [ ] Rong

Resources/Instructions

Updated milestones Current Milestones

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem

[bberhane]

2024-06-27 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

• [x] 7:00PM 5 min - Check-in
• [ ] 7:05PM 10 min- Weekly Audit
• [ ] 7:15PM 45 min- Topic Requests + Questions for Bonnie
• [ ] 8:00 fin

Accountability Checks

• [ ] Ryan
• [ ] Bethlehem
• [ ] Cotton

Topic requests/questions:

• [ ] Weekly Audit: https://github.com/hackforla/311-data/issues/1134
• [ ] Review PM Team project board
• [x] https://github.com/hackforla/311-data/issues/1753

Notes:

• https://github.com/hackforla/311-data/issues/1605: Anna wrote user interaction for info icon, type setting on info icon differs, investigate post-launch

Action Items:

• [ ] Create last two tickets for https://github.com/hackforla/311-data/issues/1463

Resources/Instructions

---

Attendees:

• [x] Ryan
• [x] Cotton
• [x] Bethlehem