311 Data Product Planning Monthly Agenda

[ryanfchase]

Overview

This issue tracks meeting agendas for the monthly Product Planning meeting for 311 Data

Agenda Quick-links

August 2, 2023

Agenda Template

## YYYY-MM-DD - 311 Data Product Planning
_[Back to Top](#)_

### AGENDA
_Timezones listed as Pacific Time._

- [ ] 7:00PM _5 min_ - Check-in & announcements
- [ ] 7:05PM _30 min_ - agenda_item_1
- [ ] 7:35PM _5 min_ - agenda_item_2
- [ ] 7:55PM _15 min_ - Q/A + Discussion

### Topic requests/questions:

### Notes:

### Action Items:

### Resources/Instructions


---
### Attendees (PMs + Leads):

- [ ] Cotton
- [ ] Bethlehem
- [ ] Brian
- [ ] Rong
- [ ] Joy
- [ ] Allison
- [ ] Ryan
- [ ] Bonnie
- [ ] London

[ryanfchase]

2023 August 2 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05 30 min - Repo Discussion w/ Bonnie
• 7:35 20 min - Repo Discussion pt 2
• 8:00 10 min - New PM team structure discussion @ryanfchase

Action Items:

• Outline steps for maintaining our remaining issues: Lead Issue Review (Tech Stack Old vs New) #1529

---

Attendees (PMs + Leads):

Product Management

• Jason Flack
• Muhammad Basil
• Sanju Venugopal

UI/UX Research

• Holly Worthen

UI/UX Design

• Joy
• Elizabeth Pose

Engineering

• Edwin J
• Ryan Chase

Content/Marketing/Copywriting

• TBD

UNASSIGNED

• Bonnie

[cottonchristopher]

2023-10-04 - 311 Data Product Meeting

Back to Top

AGENDA

Time zone listed as Pacific Time.

• 7:00PM 5 min - Check-in
• 7:05 20 min - Team announcements + updates
• 7:25 20 min - Project Board Review/ Process document review
• 7:45 15 min - Breakout Rooms
• 8:00 finished

Topic requests/questions:

• Naming the current Version of the product
• Process document review
• RC: V2 launch plans
• Offboarding updates

Notes:

1. Product team will review Configuring Analytics tools in breakout room.

Action Items:

Resources/Instructions

---

Attendees (PMs + Leads):

Product Management

• Jason Flack
• Muhammad Basil
• Sanju Venugopal

UI/UX Research

• Holly Worthen

UI/UX Design

• Joy
• Marissa
• Anna Kim

Engineering

• Edwin J
• Ryan C
• William B

Content/Marketing/Copywriting

• TBD

UNASSIGNED

• nobody

[ryanfchase]

2024-01-03 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - milestone review (see topic requests)
• 7:35PM 25 min - address any pain points / concerns for early 2024
• 8:00PM - finish

Announcements

RC:

• I have removed ALL open role cards from each of the Community of Practice repos
• Open Roles are created when there are more open issues than there are active members

Topic requests/questions:

Milestone Review

• review all milestones in order. Identify "current" milestones. Discuss "due dates".
• go through all issues and confirm they are in the right place
• confirm this is the minimum number of tickets needed to complete the milestone

RC's list of potential pain points for 311 Data

• onboarding new members
• streamlining current members onto new issues
• Clarify contribution guidelines, PRs and review process
• completing technical documentation
• ensuring leadership team is correctly supported

Edwin's Notes

• 2024 data pipeline is not set up properly
• we are waiting on the data.lacity.org to set up their 2024 data API endpoint

Notes:

Action Items:

• Create label "Pre-Launch" to identify which issues are relevant to pre-launch
• Use "Pre-Launch" label to move all "Post-Launch" issues to their correct Post-Launch milestone
• Create spreadsheet for UX Research Action Steps (categorize when we will address each Action Step)
• Create list of tickets to be reviewed for Bonnie's ticket workshop

Bonnie's ticket workshop list:

• Propose new file organization structure #1549
• Set up a cron job via github actions to update data nightly  #1535

Notes on PM Issue Audit:
@bberhane and @ryanfchase think that audits should also check to see if tickets are still being worked on. PMs can check assignee's ETA and follow up with them once the time has elapsed (see notes below).

Notes on ETAs and Size labels:

• Size label should be the initial estimation of time based on the issue creator's assessment
• The assignee will assess the issue and see if the work falls within the Size label's range. The assignee should comment how long they think they will need (e.g. Size label is 1hr and assignee comments, "ETA: 30 minutes to 1hr")
• If assignee thinks it will take longer than the Size label, they should comment and tag the issue owner (e.g. "ETA: 4 hours but Size label says 1 hour"). Assignee updates the size label at their discretion.

Resources/Instructions

---

Attendees (PMs + Leads):

Product Management

• Cotton
• Bethlehem
• Ahmed

UI/UX Research

• Holly Worthen

UI/UX Design

• Anna Kim

Engineering

• Edwin J
• Ryan
• Johnny

Content/Marketing/Copywriting

• TBD

UNASSIGNED

• nobody

[ryanfchase]

2024-02-07 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 12:05 30 min - Topic Requests
• 12:35 20 min - Discussion
• 12:55 5 min - Wrap-up

Topic requests/questions:

• per Bonnie, offboard Sanju: 311 Data Weekly PM Meeting Agenda  #1546 (comment)

Notes:

Action Items:

Resources/Instructions

---

Attendees (PMs + Leads):

Product Management

• Cotton
• Bethlehem

UI/UX Research

• Brian
• Rong

UI/UX Design

• Anna

Engineering

• Ryan
• Johnny

Content/Marketing/Copywriting

• TBD

UNASSIGNED

• Bonnie

[ryanfchase]

Some notes for our next meeting (I will add these items myself based on how high priority they are):

General notes from 2/29 meeting

TODO

• add Allison and Joy to leads group
• we need to compile a few good tickets for Design team to use as reference when making their tickets
• we need to re-organize the epics so that there is 1 epic per feature
• we need to go through Action Steps spreadsheet and start making tickets for Design/Engineering
• there are 3-ish pre-launch Design issues that are ready for hand-off! We need to make sure Dev Lead(s) can see these and act on them see below
• I think we need to update the Pre-Launch Issues spreadsheet with the issues that engineering makes
• consider using PreLaunch labels for all prelaunch items (since members "cant see" epics)
• Design worked on a pre-launch ticket, but the proposed design goes beyond scope (it addresses a post-launch Action Step): Modal Neighborhood Districts #1650

TODO Ryan

• make engineering ticket for Loading Modal (Johnny wants to work on this)
• jot down a note on how to make Dependabot alert changes (Settings > Code Security and Analysis > Enable/Disable)
• prioritize: Update the Twitter logo to 'X' #1691

Ready for Hand Off

• Modal Neighborhood Districts #1650 (comment)
• Update all instances of the old Twitter logo to the rebranded X #1642 (comment)
• Update Loading Modals after Feedback from Bonnie #1655 (comment)
• possibly Add warning for when user tries to load data prior to 2024 #1677

Notes

• Bonnie says that Epics are for PMs only, nobody else should be assigned to epics
• Since members don't see epics, Design Issues should inherently convey all information needed to hand-off to Engineering

Possible Action Items for Design Issues

[bberhane]

2024-05-01 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05 30 min - Update from team leads
• 7:35 25 min - Open floor
• 8:00 _ - fin

Topic requests/questions:

Update from dev: Engineering is working on making final launch tickets
PM team is still working on having more streamlined processes and ticket templates that align with org

Notes:

Action Items:

Resources/Instructions

---

Attendees (PMs + Leads):

Product Management

• Cotton
• Bethlehem

UI/UX Research

• Holly Worthen

UI/UX Design

• TBD

Engineering

• TBD

[ryanfchase]

Adding this to the upcoming agenda:

• PM team wants to know from Bonnie what is needed for GA PRD - Configure Google Analytics platform for 311-Data to gather user interaction data #1592 (comment)

[ryanfchase]

2024-06-05 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 40 min - Topic Requests/questions
• 7:45PM 15 min - Q/A + Discussion
• 8:00PM - fin

Topic requests/questions:

• review progress on ticket audits, team accountability checks
  • Ryan to provide an example of a few dev team tickets as part of an agenda
• review project board updates (need to close old project boards)
  • review Bonnie's slack post
  • possibly attend PM Friday CoP if we need more help on this
• review pre-launch spreadsheet
  • Review Dev tickets / members / estimations
  • Review UXR tickets / members / estimations
  • Review Design tickets / members / es
• Check if UXR team needs GA for usability testing: PRD - Configure Google Analytics platform for 311-Data to gather user interaction data #1592 (comment)
• UXR Usability test status update
  • moderated usability test (do we need to post in more slack channels?)
  • un-moderated usability test (via usertesting.com ?)
  • Data science CoP (awaiting reply from CoP leads iirc)

Questions for Bonnie

• What is our use cases for GA? What are other examples of teams using GA? Do we need to access a GA dashboard: PRD - Configure Google Analytics platform for 311-Data to gather user interaction data #1592 (comment)
• Should we be incorporating our Mailchimp campaign for the Contact Us page? When we send emails to users, which email should be sending that email? (todo - link contact page ticket)

Notes:

Action Items:

• Give Holly access to the 311-data email, add her email to the 311-Data general vault

Resources/Instructions

• THAT product team mega-comment

• pre-launch spreadsheet link: https://docs.google.com/spreadsheets/d/1wy9zp0HLTsCBjPejAJmtLrZPELLGQwTgHhcyx5HpALQ/edit#gid=0

---

Attendees (PMs + Leads):

• Cotton
• Bethlehem
• Holly Worthen
• Anna
• Ryan
• Bonnie

[ryanfchase]

New Tickets

• datepicker should not allow "future months" (e.g. if today is June 6th 2024, do not allow user to advance to July 2024)
• PM team needs a "saved reply" for "please provide ETA, etc" for accountability checks
  • ETA-ing: for a given volunteer, use their update to provide an updated ETA which can be put into the Story Point spreadsheet.
  • add a checkbox for the "saved reply" to update the Story Point spreadsheet with their provided ETA
    ETA can be used to guesstimate how long a milestone / release (e.g. pre-launch) will take
• PM team to use the copy all Start Here cards from project board into our wiki, use this template for relevant info:
  • Completed ticket for copying cards: GitHub Project Board Migration Issue #1751
  • Open ticket for moving contents into wiki: Add comments with card information into 311-Data Wiki after migration #1755
  • shortcut for finding cards that need to migrate
  • look for "description" cards that will end up becoming column headers (keep it concise!)
  • ignore "references" these are not real cards
• PM team to add to FAQ about overlapped boundaries: Add Q&A About Overlapping Boundaries to FAQ Page #1760
  • See comment from a few weeks ago

Notes from 6/5/24

• reviewed Design System Updates: Search/Filter Modal #1600
• GA: use general for general statistics for MVP: PRD - Configure Google Analytics platform for 311-Data to gather user interaction data #1592
  • consider where to add tags on specific actions for future releases
• ETA-ing: for a given volunteer, use their update to provide an updated ETA which can be put into the Story Point spreadsheet.
  • ETA can be used to guesstimate how long a milestone / release (e.g. pre-launch) will take

New Project Board

• what happens when you click migrate?
  • who gets permissions?
  • need to add Teams (311-Data-Write)
• Due end of June

screenshot

[ryanfchase]

2024-08-07 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - welcome back slides
• 7:35PM 5 min -flex time
• 7:55PM 20 min - Questionnaire time, Q/A, Discussion

Topic requests/questions:

• welcome back slides: https://docs.google.com/presentation/d/128WTvjESfaKJ_0MKvJFD5_Q4wwOvSnie-3st1ZD2XDI/edit?usp=sharing
• Check in questionnaire: https://forms.gle/czuZrU7WgYvPBc7G8
• Anonymous feedback form: https://forms.gle/JJ8b7Mtir64nrXZr7

Review...

• Pre-Launch Roadmap
• Post-Launch Roadmap
• Goals for the month

Notes:

Action Items:

Resources/Instructions

• All Epics: https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+label%3AEpic

---

Attendees (PMs + Leads):

• Cotton
• Bethlehem
• Holly Worthen
• Joy
• Allison
• Ryan
• Johnny
• Bonnie

[ryanfchase]

2024-09-04 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - agenda_item_1
• 7:35PM 5 min - agenda_item_2
• 7:55PM 15 min - Q/A + Discussion

Topic requests/questions:

PRIORITY: Review Action Steps spreadsheet (via UXR v1.2 Mod. Usability Test Presentation)

• WIP, see link to presentation and prev. Action Steps spreadsheet in Resources below

Review Proposed Tickets

• UXD - Display NC names on hover via pop-up modal  #1807
• Identify the name of adjacent NCs, if another NC is already selected #1808
• Make date range textboxes clickable in Search and Filters modal  #1806
• Add Mapbox Zoom Controls to Map Page #1793

Meeting Note Recap

• 8/29/24 pm mtg notes
• 8/31/24 dev mtg notes
• uiux design notes on presentation from #311-data-uiux

Notes:

Action Items:

Resources/Instructions

• Usability Testing v1.2 August Presentation (Slide Show)
• Action Steps post bug and usability testing January 2024

---

Attendees (PMs + Leads):

• Cotton
• Bethlehem
• Holly Worthen
• Anna
• Ryan
• Bonnie

[cottonchristopher]

Notes from 9/4/2024
Tickets to be made:
1. Corresponds to Insight 1, address known, but name of NC unknown. Suggestion: address selected, zoomed-in, Add a
Pill(pillbox)-
2. Corresponds to Insight 3 (partial), No option to de-select. Suggested solution, same as above
3. Design ticket: to auto-recenter to all boundaries. Post launch?
4. SR Hover box confusion: Sequence should be- hover, spin and load. Sequence only occurs once. Should occur every
time. Ryan has a ticket?
5. Corresponds to Insight 6, Address entered, and House icon appears. Need or nice to have?
6. Calendar fxn not intuitive: Make date range editable or allow a drop down as well. Area should be clickable.

Post launch: NC council names on hover for unselected areas, however it may present challenges with contrast color
achievement and visibility (per Joy) - Design ticket

[ryanfchase]

New design tickets based on above comment:

• Redesign address search house icon: Redesign address search house icon #1816
• Button for auto-recenter to all boundaries: UXD - Create button to reset selection mode and recenter around all boundaries #1817
• NC council names on hover when unselected: UXD - Display NC names on hover via pop-up modal  #1807
• Search and Filters date range need to be editable: UXD - Redesign date selection in search & filters modal to be type-to-edit #1818

[ryanfchase]

2024-10-02 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - agenda_item_1
• 7:35PM 5 min - agenda_item_2
• 7:55PM 15 min - Q/A + Discussion

Topic requests/questions:

• Discuss UIUX Design contributions to Action Steps Notes (R1)
• ⚠️ New Bug: Bug Hunt & Code Quality Live-Forever Ticket #1726 (comment)
• Documentation
  • prepping for launch by updating Team Wiki
• Slides: https://docs.google.com/presentation/d/1Op1hZsFRC1023Se-MatVROWxkMhkoLvHwIF2oASMzZw/edit#slide=id.g2f9680e244f_0_0

Notes:

Action Items:

Resources/Instructions

• R1: Comments on V1.2 August Usability Test Presentation, Google Doc

---

Attendees (PMs + Leads):

• Cotton
• Bethlehem
• Holly Worthen
• Brian
• Rong
• Joy
• Allison
• Ryan
• Bonnie

[ryanfchase]

2024-11-06 - 311 Data Product Planning

Back to Top

AGENDA

Timezones listed as Pacific Time.

• 7:00PM 5 min - Check-in & announcements
• 7:05PM 30 min - agenda_item_1
• 7:35PM 5 min - agenda_item_2
• 7:55PM 15 min - Q/A + Discussion

Topic requests/questions:

• Updates from each team
  • PM (marketing, achievements, story of 311)
  • Dev (Vite migration, bug fixes)
  • UXUI
  • UX Research
• Q: any updates on recruiting?
  • UXR: Holly plans to return in Jan
  • UXUI: any follow up on Open Roles board?
• What can we achieve in November before break!?!?

Notes:

Action Items:

Resources/Instructions

---

Attendees (PMs + Leads):

• Cotton
• Brian
• Joy
• Allison
• Ryan
• Bonnie

[ryanfchase]

• Closing this issue for 2025 meeting agenda: 311 Data Product Planning Monthly Agenda 2025 #1908