311 Data Weekly PM Meeting Agenda

MBasil03 commented 1 year ago

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 
- [ ] London

ryanfchase commented 1 year ago

2023-08-10 - 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- Intros + Review Agenda
[x] 7:15PM 30 min- Review #1529
[x] 7:45PM 15 min- Establishing Road Map
[x] 8:00 fin

Topic requests/questions:

finish cleaning up Design + PM issues and close out #1529
Graem has notes for Github issues + new issue assignment moving forward
come up with rules for new issues
- close all Tech Stack: Missing + Tech Stack: Old
- remove label Tech Stack: New
- enforce roles and sizes for new issues
- come up with New Issue Approval column rules (e.g. sign off from 1 PM)

Attendees:

[x] Ryan
[x] Sanju
[x] Muhammad
[x] Graem
[x] Anna

ryanfchase commented 1 year ago

2023-08-24 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 10 min- Updates from the week
[ ] 7:15PM 30 min- Project Board Review
[ ] 7:45PM 15 min- Discussion
[ ] 8:00 fin

Topic requests/questions:

Still need to clean up labels on new issues. It looks like engineering tickets are continuing to use Tech Stack: New, I suggest simplifying our system so we can disregard those holdover labels.

Proposed Steps

close all Tech Stack: Missing + Tech Stack: Old
remove label Tech Stack: New

Other suggested rules

enforce roles and sizes for new issues
come up with New Issue Approval column rules (e.g. sign off from 1 person on PM team)

Attendees:

[x] Ryan
[x] Sanju
[x] Muhammad
[x] Graem
[ ] Anna
[x] Cotton
[x] Holly
[ ] Edwin

ryanfchase commented 1 year ago

2023-08-31 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[ ] 7:05PM 15 min- Project Board Review + Create issues for outstanding PM team tasks
[ ] 7:20PM 15 min - @sanjumv reviews his latest updates to our groundwork doc
[ ] 7:35PM 25 min- Discussion*
[ ] 8:00 fin

*All discussion is tentative bc Bonnie WILL have things to say

Topic requests/questions:

[ ] Ask About HunggingFace team

Attendees:
[ ] Ryan
[ ] Sanju
[ ] Muhammad
[ ] Graem
[x] Anna
[ ] Cotton
[ ] Holly
[ ] Edwin

ExperimentsInHonesty commented 1 year ago

Add to our agenda

[ ] BW: Reviewing the zoom setup spreadsheet. To talk about the 1st week planning meeting Wednesday. You currently have an all meeting scheduled every week.
[ ] BW: Creating a Weekly Label Check issue https://github.com/hackforla/product-management/wiki/Weekly-Label-Check
[ ] BW: review references to CfA https://github.com/search?q=repo%3Ahackforla%2F311-data%20%22code%20for%20america%22&type=code

ryanfchase commented 1 year ago

2023-09-07 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 25 min- @sanjumv Product Vision discussion
[ ] 7:30PM 20 min- general discussion + discuss if Thurs meetings are required
[ ] 8:00 fin

Topic requests/questions:

[x] BW: Reviewing the zoom setup spreadsheet. To talk about the 1st week planning meeting Wednesday. You currently have an all meeting scheduled every week.
[x] BW: Creating a Weekly Label Check issue https://github.com/hackforla/product-management/wiki/Weekly-Label-Check
[ ] BW: review references to CfA https://github.com/search?q=repo%3Ahackforla%2F311-data%20%22code%20for%20america%22&type=code
Notes:

Goals:

[ ] Record Sanju's notes on Product Vision(?) OR come up with feedback form

Action Items:

Resources/Instructions

Attendees:

[ ] Ryan C.

bberhane commented 1 year ago

2023-09-13 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 20 min- Address topic requests
[ ] 7:25PM 20 min- Project management updates from Bonnie?
[ ] 7:45PM 15 min- Product vision discussion?
[ ] 8:00 fin

Topic requests/questions:

From PM breakout room

[x] Milestones
[x] Which teams should we reference when considering how to proceed with V3?
[x] Are there any other teams that have pivoted?

RC

[x] Vote on new time for weekly PM meeting
[x] What Google Drive permission level should be giving new members (non PMs)
[ ] Fix contents for this issue's original post
[x] Check Engineering Onboard & Offboard issue #1578
[x] Where do we put never-closing issues on the Project Board

Notes:

Action Items:

Resources/Instructions:

Groundwork on project - https://docs.google.com/document/d/1aQqAn_OOBZhpyHZcAklTqgdH8SDWAMmDep12v64k324/edit

Attendees:

[x] Ryan
[x] Sanju
[x] Anna
[x] Cotton
[x] Bethlehem
[ ] Muhammad?
[x] Graem?

ryanfchase commented 1 year ago

Add as TODO for next meeting:

remove outdated slack channels
@ryanfchase needs to review Privacy Policy Update #1581
@bberhane & @cottonchristopher makes an issue for Milestones Spike

annaseulgi commented 1 year ago

Please add to agenda for 9/21 meeting:

Design would like to go over the team count/clarify from previous meeting

luca-navarrete commented 1 year ago

Add to the next agenda:

- [ ] Review with Bonnie 
  - [ ] Slack channels (active/dormant/archived)
  - [ ] Slack channel pins and bookmarks

bberhane commented 1 year ago

2023-09-21 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[ ] 7:05PM 30 min- Topic Requests
[ ] 7:35PM 15 min- Design request: team count clarification
[ ] 7:50PM 10 min- Update on milestone spike/discussion
[ ] 8:00 fin

Topic requests/questions:

Design would like clarification on determining team count per last week's discussion
Slack channels, pins, bookmarks (see #1589)
@ryanfchase needs to prepare #1581 and then hand off to engineering

Notes:

Goals:

Action Items:

Resources/Instructions:

Attendees:

[x] Ryan
[x] Sanju
[x] Anna
[ ] Cotton (will be out)
[x] Bethlehem
[ ] Graem
[x] Bonnie
[ ] Luca

bberhane commented 1 year ago

2023-09-28 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 25 min- Updates from Bonnie/Any other attendee
[ ] 7:30PM 20 min- @sanjumv to lead discussion on proposed project prioritization process
[ ] 7:50PM 10 min- Feedback on updated milestones
[ ] 8:00 fin

Topic requests/questions:

RC

[x] Review FAQ page engineering ticket
[x] Check weekly audit
[ ] Review with team Offboarding (UI/UX member just recently left)
[ ] Log into Contentful so we can complete #1581
Notes:

Goals:

Align the team on prioritization and processes
Agreement on milestones

Action Items:

Resources/Instructions:

Milestone review: https://docs.google.com/document/d/19ERCz8CAQhTVO_nyjezXRaOvyZ7wUDrbkeDhb4o4uUg/edit?usp=sharing
Weekly Audit: https://github.com/hackforla/311-data/issues/1134#issuecomment-1740208440

Attendees:

[x] Ryan
[ ] Sanju
[x] Anna
[x] Cotton
[x] Bethlehem
[ ] Graem
[x] Bonnie

bberhane commented 1 year ago

2023-10-05 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[x] 7:05PM 35 min- Updates from Bonnie/any other attendee
[ ] 7:40PM 20 min- @sanjumv to lead discussion on project prioritization process
[x] 8:00 fin

Topic requests/questions:

[x] @annaseulgi @ryanfchase to discuss landing page homepage with Bonnie
[x] @cottonchristopher/@bberhane to get sign-off on updated milestones

Notes:

Action Items:

Resources/Instructions:

Milestones doc: https://docs.google.com/spreadsheets/d/1kc7Fh-zxKvmpGN5ru4n3Ra9QskYofh1-dc-LjsmL84M/edit?usp=sharing

Processes doc: https://lucid.app/lucidspark/f7b63b6a-8200-40e0-863e-48913b505e9c/edit?viewport_loc=-2650%2C114%2C9129%2C4425%2C0_0&invitationId=inv_94435f55-0724-4c39-b361-ff35bca32a60

Zoom link: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[x] Ryan
[ ] Sanju
[x] Anna
[x] Cotton
[x] Bethlehem
[x] Bonnie

bberhane commented 1 year ago

2023-10-12 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 30 min- Updates from Bonnie/Any other attendee
[ ] 7:35PM 25min- @sanjumv to lead discussion on project prioritization process
[ ] 8:00 fin

Topic requests/questions:

[ ] Bonnie to sign-off on remaining milestones
[ ] Onboard Ahmed Awadalla

Notes:

Action Items:

Resources/Instructions:

Zoom link: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[x] Ryan
[ ] Sanju
[x] Anna
[x] Cotton
[x] Bethlehem
[x] Bonnie

bberhane commented 1 year ago

2023-10-19 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 35 min- Updates from Bonnie/Any other attendee
[ ] 7:40PM 20 min- @sanjumv to go over proposed prioritization process
[ ] 8:00 fin

Topic requests/questions:

Review of label audit

Notes:

Action Items:

Discuss orgs. to invite to X-Mas party

Resources/Instructions:

Org. sheet (note, it is View Only): https://docs.google.com/spreadsheets/d/1hUVPBpbovc4M5Bxo-rlCOOThsmtuJtRJmTg55mP6R3s/edit#gid=0

Link to issue: https://github.com/hackforla/311-data/issues/1597#issue-1941130072

Link to Zoom invite: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[ ] Ryan
[ ] Sanju
[ ] Anna
[ ] Cotton
[x] Bethlehem
[ ] Ahmed
[ ] Bonnie

bberhane commented 1 year ago

2023-11-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 05 min- Updates/announcements/recap
[x] 7:10PM 40 min- Design/engineering best practices + handoff discussion
[ ] 7:50PM 10 min- Misc.
[ ] 8:00 fin

Topic requests/questions:

[x] RC: Come up with steps to unblock Research from starting internal user testing (i.e. begin Map Bug Bash milestone)

For Next Time:

[ ] RC: Get caught up on discussion around FAQ page and document it
[ ] RC: Come up with steps to unblock Engineering from starting FAQ page changes (do we need to modify Graem's designs)
[ ] Determine scope of map page design updates (Anna to clarify)
[ ] RC: Determine if we can start new map page (discuss with Edwin creating a Release tag to fall back on stable app version)

Notes:

Goals:

Allow PM team to assign a milestone, and Design Lead to understand when to prioritize the issue

[ ] Come up with a New Feature Request (optional engineering demo) Github Issue template
[ ] new ticket to update Map Page milestone with static list of required visuals and behaviors
[ ] cross team lunch & learn: follow a feature from Design team to Engineering team to Research team

Action Items:

Resources/Instructions:

Link to Monthly Team Leads meeting recording: https://drive.google.com/drive/folders/1fmh02Nlg0t1SOf-wXXpFclKWuSyhZwBb?usp=drive_link Zoom link: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[x] Ryan
[ ] Sanju
[x] Anna
[x] Cotton
[x] Bethlehem
[x] Ahmed
[x] Edwin

ryanfchase commented 1 year ago

2023-11-09 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[ ] 7:05PM 40 min- Review Topic Requests
[ ] 7:45PM 15 min- Q&A
[ ] 8:00 fin

Topic requests/questions:

From RC

[x] "What happens when design needs to modify MVP (e.g. pre-launch Accessibility)?"
[x] "What happens if Engineering has feature candidates for MVP (e.g. data export button)?"
[x] Does "Content pages are delivered in a set" discussion need to be resolved?
[x] Review Map MVP, clarifying #1613
[x] Review Proposed Design-to-Engineering ticket

Notes:

Action Items:

[ ] complete weekly issue audit

Resources/Instructions

Attendees:

[x] Ryan
[x] Anna
[x] Cotton
[x] Bethlehem
[x] Edwin
[x] Ahmed

bberhane commented 12 months ago

Recap of 2023-11-09 Meeting:

Immediate concerns:

Remove dashboard from website menu
Replace Code for America with Civic Tech Structure on landing page
Remove research page
Update Privacy Policy
Remove "2-3 days" from contact form
Contact form needs to open an issue
No design/functionality changes to FAQ page

Accessibility Post-Launch:

Accessibility needs to be high priority after launch
Note: Dark mode is not accessible
Add plus and minus sign to map (suggested)
Toggle to dark mode for map will be CRUCIAL
Add ZIP code, state representative, jurisdictions on map

bberhane commented 12 months ago

2023-11-16 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[ ] 7:05PM 35 min- Updates from Bonnie/Any other attendee
[ ] 7:40PM 20 min- Clarification on items to be completed to launch
[ ] 8:00 fin

Topic requests/questions:

[x] Ask Bonnie location of Civic Tech Structure logo
[x] Review Design-To-Engineer Handoff Template
[x] Analytics setup, any guides we should be using to inform us on what to collect?
[x] Should PMs meet next week? (Rc thinks No)

Notes:

Recap of 2023-11-09 Meeting:

Immediate concerns:

[x] Change map color scheme to light mode (@ryanfchase )
[x] Remove dashboard from website menu (@ahmedsalah0130)
[x] Replace Code for America with Civic Tech Structure on landing page (@cottonchristopher)
[x] Remove research page (@bberhane)
[x] Update Privacy Policy (doesn't need new ticket)
[x] Remove "2-3 days" from contact form (@ahmedsalah0130)
[x] Contact form needs to open an issue (there's already an engineering issue for this)
[x] No design/functionality changes to FAQ page (doesn't need a new ticket)
[x] Update loading modal to emphasize 311 is not la city (@bberhane)

Accessibility Post-Launch:

[ ] Accessibility needs to be high priority after launch
[ ] Note: Dark mode is not accessible
[ ] Add plus and minus sign to map (suggested)
[ ] Toggle to dark mode for map will be ~CRUCIAL~ prioritized based on its value to accesibility
[ ] Add ZIP code, state representative, jurisdictions on map

Goals:

Action Items:

Resources/Instructions

Attendees:

[ ] Ryan
[ ] Anna
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed
[ ] Bonnie

bberhane commented 11 months ago

2023-11-30 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 25 min- Updates from Bonnie
[ ] 7:30PM 30 min- Update on pre-launch items + epics
[ ] 8:00 Thanks, everyone!

Topic requests/questions:

Pre-launch checklist (confer with Bonnie):

1637

Post-launch checklist:

TBD -- need to complete #1619

Anna wants to know...

[ ] increasing engagement in breakout rooms (how to combat the crickets)

Notes:

Action Items:

[ ] Have a great holiday break

Resources/Instructions:

Link for Zoom meeting: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[x] Ryan
[x] Anna
[x] Cotton
[x] Bethlehem
[x] Ahmed
[x] Bonnie
[ ] Edwin?

ryanfchase commented 11 months ago

For all teams:

review open roles on the HackForLA team to get ready for 1st onboarding of the year

Potential engineering workshop

teach all engineers, thru the process of creating tickets based on requirements (figma, behavioral)

FAQ eng issue

needs to go back to New Issue Approval as "Draft". We need to get into contact with the assignee and confirm it's not in progress

General Note

RC needs approval on a PR

Issue making workshops

Overview section needs to be shorter. Review 'User Story' formula that Sanju made vs X-for-Y
we'll probably need to do a session with Bonnie
After Bonnie's workshop, discuss design and engineering issue templates.

On the fly

ask someone knowledgeable to fix it
describe the workflow

ryanfchase commented 10 months ago

2024-01-04 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 25 min- Go over PM issues
[ ] 7:30PM finish!

Topic requests/questions:

[ ] Go through open PM issues
[ ] Create issue for creating the Pre-Launch label

Notes:

Questions About Action Steps Spreadsheet

Problem, # Users, relevant quotes are empty. Was this cleared out so we can use this page as a template?
suggestion for Priority: enumerating the level of importance to the team (e.g. 1-10)
suggest we do a side-by-side w/ Research on 1/17/2024 (joint breakout room)

Action Items:

Resources/Instructions

Attendees:

[ ] Ryan
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed

bberhane commented 10 months ago

2023-01-11 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 15 min- Review of launch items
[ ] 7:20PM 30 min- Recommendations for action steps doc improvements [to facilitate prioritization]
[ ] 7:50PM 15 min- Open floor
[ ] 8:00 fin

Topic requests/questions:

Go over some prioritization methods Should we rank action steps? Add importance category?

Notes:

Design to compile list of minor yet important accessibility bugs

Action Items:

[x] Assign a PM to https://github.com/hackforla/311-data/issues/1646

Resources/Instructions

Action steps based on research: https://docs.google.com/spreadsheets/d/1y_8xUCxEU83adN2GjEIOt3F-wILJ1_c2KdgISFRN5cU/edit?usp=sharing
Research results deck: https://docs.google.com/presentation/d/1NBMnS8_znCnYNDNNQrN2Jh5GQZhZmX56rtHME-EewBY/edit?usp=sharing

Attendees:

[ ] Ryan
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed

ExperimentsInHonesty commented 10 months ago

Please discuss this requested change with me at the next meeting I attend https://github.com/hackforla/website/issues/6114

ryanfchase commented 10 months ago

Need to add to tonight's agenda (now organized by category):

Emergent Requests

we should look into implementing the Emergent Request issue template, example here
@Skydodle comment about updating our PR template: https://github.com/hackforla/311-data/pull/1653#issuecomment-1898029041

Design-To-Engineering Hand Off

Updating the Loading Modal Epic by assigning to to Design team. Since Bonnie requested updates.
Update the "remove dashboard" ticket to just be an engineering ticket: https://github.com/hackforla/311-data/issues/1627#issuecomment-1899166686
we need to modify the Design to Engineering Hand Off github issue template
- do we still need to adjust roles/labels?
- review Bonnie's hide picture technique
we need to undo Bonnie's change of milestones in Design to Engineering Hand Off (she moved it to Launch, which Beth and I decided is incorrect)

Other

we still need to make the "pre-launch" label?? we should review the pre-launch epic: https://github.com/hackforla/311-data/issues/1637

bberhane commented 10 months ago

2023-01-18 - 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- Takeaways from ticket-making workshop
[x] 7:25PM 35 min- Topic requests
[x] 8:00 fin

Topic requests/questions:

Emergent Requests

[ ] we should look into implementing the Emergent Request issue template, example here
[ ] @Skydodle comment about updating our PR template: https://github.com/hackforla/311-data/pull/1653#issuecomment-1898029041

Design-To-Engineering Hand Off

[x] Updating the Loading Modal Epic by assigning to to Design team. Since Bonnie requested updates.
[x] ~Update the "remove dashboard" ticket to just be an engineering ticket:~ closed ticket as duplicate https://github.com/hackforla/311-data/issues/1627#issuecomment-1899166686
[ ] we need to modify the Design to Engineering Hand Off github issue template
- do we still need to adjust roles/labels?
- review Bonnie's hide picture technique
[ ] we need to undo Bonnie's change of milestones in Design to Engineering Hand Off (she moved it to Launch, which Beth and I decided is incorrect)

Other

[x] ~we still need to make the "pre-launch" label??~ we should review the pre-launch epic: https://github.com/hackforla/311-data/issues/1637

Notes:

Action Items:

Resources/Instructions

Zoom link: https://us06web.zoom.us/j/87979035538?pwd=ZGtiU1FJeTN0V3BFNXYyMDYvN08yUT09

Attendees:

[x] Ryan
[x] Ahmed
[x] Cotton
[x] Bethlehem

ryanfchase commented 9 months ago

For next PM meeting

@Skydodle also suggests adding the /Details command to the Blank Issue template

ExperimentsInHonesty commented 9 months ago

Please add to the next agenda

[ ] talk to Bonnie about this image: https://github.com/hackforla/website/issues/6114 and extra points if the PMs can tell me why this image is not ok to use (from a product voice of the customer perspective/product alignment).
[ ] The data is for 2024 is available. It started being available on 2024-01-18 https://data.lacity.org/City-Infrastructure-Service-Requests/MyLA311-Service-Request-Data-2024/b7dx-7gc3/about_data

ryanfchase commented 9 months ago

2024-02-01 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 30 min- Topic Requests from Bonnie
[ ] 7:35PM 25 min- Topic Requests from Ryan
[ ] 8:00 fin

Topic requests/questions:

Bonnie

[x] talk to Bonnie about this image: https://github.com/hackforla/website/issues/6114 and extra points if the PMs can tell me why this image is not ok to use (from a product voice of the customer perspective/product alignment).
[x] The data is for 2024 is available. It started being available on 2024-01-18 https://data.lacity.org/City-Infrastructure-Service-Requests/MyLA311-Service-Request-Data-2024/b7dx-7gc3/about_data

Ryan

[ ] Briefly cover Action Items spreadsheet: https://github.com/hackforla/311-data/issues/1649
[ ] Cover timeline for creating guides from Issue Workshop: https://github.com/hackforla/311-data/issues/1651
[ ] (IMPORTANT) covering new issues that arise during the week -- how to spot them and how to address them

Action Items:

Resources/Instructions

Attendees:

[ ] Ryan
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed
[ ] Bonnie

ExperimentsInHonesty commented 9 months ago

Please offboard Sanju https://github.com/hackforla/311-data/issues/1561

bberhane commented 9 months ago

2024-02-08 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 10 min- Offboard Sanju https://github.com/hackforla/311-data/issues/1561
[ ] 7:15PM 30 min- Pre-launch issues story points count
[ ] 7:45PM 15 min- Product planning monthly meeting recap
[ ] 8:00 fin

Topic requests/questions:

Notes:

Action Items:

[ ] Calculate how long launch will take
[x] Offboard Sanju
[ ] Create handoff epic for in-eligible date feature (info button + greyed out calendar dates?)
[x] review this ticket and determine pre-launch actions: https://github.com/hackforla/311-data/issues/1673
[x] prepped for assignment: https://github.com/hackforla/311-data/issues/1652
[x] Updated: https://github.com/hackforla/311-data/issues/1648

Resources/Instructions

Todo

[ ] Add this as a reference to the Blank Issue Template: https://www.hackforla.org/guide-pages/github-issues.html#member-analytics

Attendees:
[ ] Ryan
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed

bberhane commented 9 months ago

Notes from 2/7 meeting:

Make a ticket to make labels in legend consistent
Add I to date range with error message saying we’re working to make past data available from 2018 to 2023
Add LinkedIn hack for LA to the I?

bberhane commented 9 months ago

2024-02-15 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 10 min- Update from breakout rooms by team
[ ] 7:15PM 45 min- Regroup on project time to completion
[ ] 8:00 fin

Topic requests/questions:

Prelaunch Issues Points Spreadsheet

https://github.com/hackforla/311-data/issues/1624

Notes:

Action Items:

Estimating Time to Launch

Resources/Instructions

Attendees:

[ ] Ryan
[ ] Cotton
[x] Bethlehem
[ ] Ahmed

bberhane commented 8 months ago

2024-02-22 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[ ] 7:00PM 5 min - Check-in
[ ] 7:05PM 15 min- Updates from PMs
[ ] 7:20PM 20 min- Discuss updated story points spreadsheet
[ ] 7:40PM 20 min- Topic requests
[ ] 8:00 fin

Topic requests/questions:

[ ] Discuss two research tickets: - https://github.com/hackforla/311-data/issues/1463 and https://github.com/hackforla/311-data/issues/1555
Notes:

Action Items:

Resources/Instructions

Pre-launch checklist

Attendees:

[x] Ryan
[x] Cotton
[x] Bethlehem
[ ] Ahmed

bberhane commented 8 months ago

Notes for 2/22 Meeting:

Make label for cookies and other components on the screen, e.g., footer
Look through closed cookies issues concerning accessibility
Create issue to check accessibility of the current cookie notice; if it’s not easy to dismiss through a screen reader, then it’s problematic

cottonchristopher commented 8 months ago

Notes for meeting 2/22/24

Explanation page: the limitations of the amount of data that can be loaded
usability testing: internal (HaxkforLa), diff people from diff communities, (20)
issue 1680 is a good practice issue: issues need clear objective definition of done, before and after screenshots, more specific screenshots,
Project Board: Question Column added
Design issues: accessibility - What are the accessibility standards? What standards are used? Resource? (Resource will prove necessity and completion)
Make an issue for accessibility – check accessibility of current cookie notice, if not easy to dismiss by screen reader or the tools used if visually impaired then its problematic, the info is covered by cookie notes
( pages on the site) Update the image for the FB, make an issues, Same Hero, new Image Check twitter,

bberhane commented 8 months ago

Notes for 2/22/24 meeting:

Need cookies ticket; make label for cookies and other components on the screen, e.g., footer
Create issue to check accessibility of the current cookie notice, if it’s not easy to dismiss through a screen reader, then it’s problematic
Ask design team what standard they used to understand accessibility #1456? #1458? [couldn't recall the issue, but it began with 14]
Before we launch ask hack for LA (ask pool from communities of practice, 20 participants, “dog fooding”) to do internal test of the app
Ask John Ritchy, Seymour, lucky something project, former NC [external testers]
Moderated testing
Good number of people to test with, 5 to 10 [external testing]
We need to mention that because the site has a low-cost infrastructure, we’re restricted to data for this version; place at the bottom somewhere = make ticket for this
Add external testing to epics of epics, and pare down testing ticket

ryanfchase commented 8 months ago

Notes from 2/22/24 meeting: Adding to Epic template

remove too many checkklists
snapshot must be really zoomed in (don't include too much info, and Bonnie hates this)
really should have a before and after of the requested change + the change

New Issues

make an update to the facebook team
should use the same hero we give to the website team
check the twitter to ensure it exists (have to sign in, etc)
The Low Cost architecture Visualization
- have to explain why only 1 month of data at a time is good (no backend, using public data)
- could maybe add this to the about page

Epics

closing 1624!
we really need to consolidate the epics so that there is one epic per feature

About Page

change the word "us" to "community members/organizations"
maybe look up and find out what exactly the mayor was encouraging us to do (we forgot)
take off "files to export", cus we're not exporting data

Loading Modal

the person working on it must be assigned
need to move it back to prioritized backlog
if they have something to show, they need to attach a screenshot

Light Mode

not a good way to compare before and after yet
otherwise, we'll just have to see if Design team's accessibliity tool passes off on this

Notes

need a really clear definition of done so that we know it's completed

Initial questions for Bonnie (will send you more if I think of some):

How soon after launch shall we do usability testing?
With whom are we going to do testing?
What would be a good number of people to test with initially?

Final notes / roadmap

dog-food testing, bug-hunt within Hack for LA (only work on grotesque things) ~20 people (eng vs data science vs pm vs design, multiple CoPs)
we should test with users right after launch, depending on who we think are users: John Ritchey, former NC members (see lucky parking project @ Seymore -- ask who this person thinks we should ask), maybe ask in #general
test the testing, do the moderated usabiity tests with some normal people first ~10
moderated usibility tests: reach out to Women in data, introduce ourselves and see if their members can weigh in (and see if they'd like to partner on our continuing development on it)

cottonchristopher commented 8 months ago

Agenda Items (Added for meeting 2/29/24 from meeting 2/28/24)

https://github.com/hackforla/311-data/issues/1677
- we need to check if we need to change messaging around 30 days of data
We need to come up with a good design issue, a good example
Review: should we have a guide or just review tickets LIVE with the team
For Action Steps, PM can make tickets ( PMs make a ticket, and then ready for design)

bberhane commented 8 months ago

2024-02-29 - 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/questions/review action steps checklist
[ ] 8:00 fin

Topic requests/questions:

https://github.com/hackforla/311-data/issues/1677
We need to check if we need to change messaging around 30 days of data
We need to come up with a good design issue, a good example
Review: Should we have a guide or just review tickets LIVE with the team
For Action Steps, PM can make tickets (PMs make a ticket, and then ready for design)

Notes:

Action Items:

Resources/Instructions

Attendees:

[ ] Ryan
[ ] Cotton
[ ] Bethlehem
[ ] Ahmed

cottonchristopher commented 8 months ago

Meeting 2/29/24 (NOTES)

Export Button- Post launch. Design can weigh in on the Button for after launch – make a ticket. (per Bonnie)
Product Planning meeting- Joy and Allison add to the meeting?.
EPICs are for PM, Issues are for the team
Tickets – ready for hand off give instructions for how to format the tickets
3 tickets need format correction. PM Homework/responsibility. (Action Items)
Research testing EPIC - 1563

ryanfchase commented 8 months ago

TODO for next meeting:

[ ] review and try to close https://github.com/hackforla/311-data/issues/1651#issuecomment-1970043982

bberhane commented 8 months ago

2024-03-07 - 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- Updates from Bonnie/Any other attendee
[x] 7:15PM 20 min- Topic requests
[ ] 7:35PM 25 min- Review of pre-launch checklist
[x] 8:00 fin

Topic requests/questions:

[x] Review and try to close https://github.com/hackforla/311-data/issues/1651#issuecomment-1970043982
[ ] Get clarification on testing, dog food vs moderated, to better inform new issue creation for external user testing epic

Notes:

Research will leave comment on tickets documenting what they worked on

Action Items:

Resources/Instructions:

Pre-Launch Checklist Action Items List

[ ] Record meeting with bonnie tomorrow for research

TODO

[ ] Make label for cookies and other components on the screen, e.g., footer
[ ] Look through closed cookies issues; create issue to check accessibility of the current cookie notice; if it’s not easy to dismiss through a screen reader, then it’s problematic
[ ] We need to mention that because the site has a low-cost infrastructure, we’re restricted to data for this version; place at the bottom somewhere = make ticket for this (Did we do this already? Popover?)
[ ] Create a ticket for this first round of dog food testing and different for externals (will proceed once we get clarification from Bonnie)
[ ] Make labels for each feature and add to existing pre-launch issues

Attendees:

[ ] Ryan
[x] Cotton
[x] Bethlehem
[x] Holly

bberhane commented 8 months ago

@cottonchristopher Will create labels for each feature, then notify Product so that we can begin adding pertinent labels to existing issues
@bberhane Will dive into cookies issue(s) and see whether we have the ticket for low-cost infrastructure
We're holding on the research tickets until we get clarification from Bonnie

ryanfchase commented 8 months ago

@bberhane

We need to mention that because the site has a low-cost infrastructure, we’re restricted to data for this version; place at the bottom somewhere = make ticket for this (Did we do this already? Popover?)

We have started a version of this popover on this epic: https://github.com/hackforla/311-data/issues/1680

Screenshot of popover

![image](https://github.com/hackforla/311-data/assets/6414668/bb120a6b-fd7f-4642-9fa3-a244c2b39883)

But based on the convo we had on Wednesday, this wording will change once we are able to incorporate multi-year data. We have a ticket in draft that will address this: https://github.com/hackforla/311-data/issues/1666

I think this is slated for post-launch, unless Bonnie thinks we need to prioritize it as a pre-launch item.

bberhane commented 8 months ago

Thank you for clarifying, Ryan!

bberhane commented 8 months ago

2023-03-14 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[x] 7:05PM 40 min- Review of action items and pre-launch checklist
[x] 7:45PM 15 min- Updates from attendees
[x] 8:00 fin

Topic requests/questions:

[x] Determine the names of labels for pre-launch features, if we haven't done so (should we lift from categories section in action items list?)

Notes:

Moved the following ticket into prioritized backlog after removing draft label during Wednesday's general meeting:

https://github.com/hackforla/311-data/issues/1666 If this is incorrect, I can move back!

TODO:

[x] kick back: https://github.com/hackforla/311-data/issues/1666
[x] Create ticket for "Searching for an NC or an address" in action items
[x] Go over design ticket template with design in next week's general meeting
[x] Make a ticket to make a list of ten fun facts for loading modal
[ ] Update pre-launch checklist to reflect closed tickets

Action Items:

Resources/Instructions

Pre-Launch Checklist Action Items List

Attendees:

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

bberhane commented 7 months ago

2024-03-21 - 311 Data PM Weekly Meeting

Back to Top

AGENDA

Timezones listed as Pacific Time.

[x] 7:00PM 5 min - Check-in
[ ] 7:05PM 35 min- Review of pre-launch checklist and action items
[x] 7:40PM 20 min- Topic requests
[x] 8:00 fin

Topic requests/questions:

Did we resolve whether we need to update the Twitter logo to X icon? @ryanfchase Discuss creating another milestone for immediate post-launch issues

Goals:

[ ] Provide more solid tentative launch timeline for next general meeting

Action Items:

Resources/Instructions

Pre-Launch Checklist Action Items List

Attendees:

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

bberhane commented 7 months ago

Notes from 2024-03-21 meeting on testing:

Dog-fooding: unmoderated with list of activities for a site (so survey task)
Some people will do bug hunt, some will do "here’s what you do on the site"
Subset: check accessibility, make a list of features of things people should test (ex. Look things up by district type, looking things up within boundaries, choosing date ranges, anything that will trigger a new experience, any new features, etc.)
Talk to data scientist CoP; send Holly to them, and have them all play with it; have them ask questions of Holly [different kind of testing]Fix data range popup language
DO THIS FIRST THEN REACH OUT TO CoP: You want ppl to submit a Zoom recording of themselves: create a form and it has to be uploaded to 311 Data my drive (use the email address for the project to make the form to avoid losing storage space)
Unmoderated testing where they record themselves and make comments as they use the website
There’s a neighborhood council lookup feature on Empower LA website; type in your address
Need to do a back story before testing for one of the below modalities (dog-food testing: demo)
Ask questions in a number of different ways, one moderated, one is let ppl do what they want with action items (record themselves), one is a demo and you get live feedback (shouldn’t use leading questions)
Come up with a script for the demo (product task)
Please remind Holly that when ppl are demoing, only have ONE tab open because of loading issues

Misc. notes

Fix data range popup language
We need to add ALL THE DATA
We need to write tickets to fix visual bugs
Dev is brainstorming how to fix long loading time issue; solutions, not all of the data can be shown at all the time
Found a bug, clicking out and then into another district doesn’t focus on clicked on district
Use standard map pin over house when typing in address and house shows up, should be pin
We need to onboard Robert before next meeting (or during general meeting)

cottonchristopher commented 7 months ago

Notes for Meeting 3/21/24 DogFood Testing Three (3) columns: (one is a bughunt? I think the unmoderated)

An unmoderated with a list of activities – like user stories for the site, I want to look this up, that up and then they can be encouraged to llk up other stuff, but not everyone. Submit recordings Form: Create a form, put in your own mydrive - use the email address for the project. mydrive for 311 data There is a lookup tool on the NC site – ( EmpowerLA- webstie click NC, and then enter address ) PM team can create a script:
Moderated: - do an explain and a demo and then get live feedback with questions, demo shouldn’t be too leading
Subset tests things that we are unsure about- accessibility, if color blind

Calendar: needs previous years Users will only choose certain# of filters ( should help with the load time) APP data driven analysis ( view patterns)

Bugs found during meeting: Should the location ICON be a house. It may cover data points. Standard map pin for houses Boundaries not highlighted when clicked May need a loading screen, when loading data Post launch ticket – to find your NC name with your address

bberhane commented 7 months ago

2024-03-27- 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 30 min- Bug review and ticket making
[ ] 7:45PM 15 min- Topic requests
[ ] 8:00 fin

Topic requests/questions:

Action Items:

[ ] Make tickets to address visual bugs
[ ] Update pre-launch checklist with new items

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

Resources:

Attendees:

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

hackforla / 311-data