311-data icon indicating copy to clipboard operation
311-data copied to clipboard

Published 20 hours ago • verified publisher icon hackforla

311: PM Team Meeting Agenda and Notes

Open EchoProject opened this issue 3 years ago • 33 comments

Overview

Meeting Agendas for PM/Org meetings

Action Items

To create a new agenda

  • [ ] Copy the template below into a new comment
  • [ ] Edit the text you pasted with new items for your agenda
  • [ ] Add the link to the new comment with its date under Resources/Instructions

Resources/Instructions

  • #1407
    The prework should be done before the meeting so that it can be discussed during the meeting. It usually takes about 5 min, if your team reaches all issues being labeled and milestones setup. During cleanup it usually takes about 30 min weekly.

Template for next meeting agenda

## [Date] Agenda and Minutes

### Prework
- [ ] label audit #1134
- [ ] Review the icebox to make sure that if dependencies have been met, the issue is moved to new issue approval column

### Roll Call

#### Recurring items: 
 - [ ] review any issues that are in the columns
   - [ ] [new issue approval](https://github.com/hackforla/311-data/projects/10#column-15704782)
   - [ ] Icebox
      - [ ] [issues with no dependency](https://github.com/hackforla/311-data/projects/10?card_filter_query=-label%3Adependency#column-11518033)
 - [ ] Accountability and Support Check
    - [ ] Review assignments for each PM
       - [ ] [Bonnie](https://github.com/hackforla/311-data/issues/assigned/ExperimentsInHonesty)
       - [ ] [Eric](https://github.com/hackforla/311-data/issues/assigned/EchoProject)
       - [ ] [Alexandra](https://github.com/hackforla/311-data/issues/assigned/alexulven)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label](https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+label%3AEpic) and define how to break down further

#### Items carried over from last meeting

#### New Items

#### FYIs

#### Actions taken or notes about stuff from the meeting:

#### New Task Items

Meetings Past and future

2021-09-28 2021-10-12 2021-10-19 2021-10-26 2021-11-02 2021-11-09 2021-11-16 2021-12-06 2021-12-17 2021-12-20 2021-12-27

EchoProject avatar Sep 29 '21 16:09 EchoProject

2021-09-28

  1. Bonnie and Eric reviewed the Shared Google Drive migration issue. Found subfolders missing from the New Drive within the Data Analysis and UI/UX folders. Next step: Eric will complete the folder recreation.
  2. Updated 311-Data team meeting schedule issue and sent a request to VRMS to update the project page. PM team meeting changed to Tuesdays at 11:00 AM, All team meeting unchanged to Thursdays at 6:30 PM, and deleted Data Science team meeting. Next step: Share with the team.
  3. Jason (VRMS engineer) gave a demo on his last day. David (VRMS engineer) will be back from vacation soon. Next step: None.
  4. Quick look at Elizabeth's Menu contrast issue. Question for UI on request type change to checkboxes. Next step: Review during the weekly team meeting.
  5. Bike and Pedestrian data request issue has been sent to the Data Science team board and closed for 311-Data. Next steps: None.
  6. Bonnie created a new issue for District Types. This is outside of the 311-Data scope right now. Sent to John(?)... Next step: None.
  7. Neighborhood Council relationship management needed. Typically handled by PMs. Next step: Eric will gather contact information (names, addresses, phone numbers, emails, etc.), create CRM in Google Sheet to track last communications.
  8. Discussed long-term planning to utilize shapefile to allow stakeholders to view 311-Data by different district types and compare different district types. Next step: Eric will evaluate each issue on the Project Board to identify issues outside the scope of the 311-Data team and relabel Move to Data Science for Bonnie to review. This will create space allowing the team to focus on the v2 launch and prioritize our roadmap for the next 3 - 6 months.

EchoProject avatar Sep 29 '21 17:09 EchoProject

2021-10-12

  1. The automated feature of "Stale" posts was requested to be removed from the Project Board.
  2. Bonnie and Eric reviewed "In Progress" Issues on the Project Board and commented for an update on Issues past 7 days without any update.
  3. Bonnie closed the "Document 311-Data Meeting Times ..." Issue.
  4. Bonnie updated the Project Board automation setting to move Issues to the "Done" column once Closed.
  5. Bonnie unassigned Issues in the "Prioritized Backlog" column.
  6. Reviewed Issues in the "Done" column that was still Open. Moved Issues with incomplete comments to the "Review" column.
  7. Created new Issues for requests made by UI/UX https://github.com/hackforla/311-data/issues/1139 , https://github.com/hackforla/311-data/issues/1140 , https://github.com/hackforla/311-data/issues/1141 and moved to the "Review" column for additional feedback from Design.

EchoProject avatar Oct 12 '21 23:10 EchoProject

2021-10-19

  1. Moved https://github.com/hackforla/311-data/issues/1126#issue-998871147 to Backlog for Frontend work.
  2. https://github.com/hackforla/311-data/issues/1132#issue-1006016055 Will create a spreadsheet of names and emails of users that need to transfer files and give them content management access.
  3. Closed https://github.com/hackforla/311-data/issues/706#issue-645962740 since a new issue was created in the Data Science repo.
  4. Moved UI/UX REPORTS issues to closed since a new issue was created in the Data Science repo.
  5. Eric will get access to web analytics and create instructions if they do not exist.
  6. Created Milestones for Project Management, Project Impact, and Stakeholder Projects.
  7. Applied Milestones to Prioritized Backlog.
  8. Updated Feature label colors.
  9. Need to go through Ice Box and check for dependencies.

EchoProject avatar Oct 19 '21 21:10 EchoProject

2021-10-26

  1. Google Drive migration #1132: 1.1. Create video tutorial on how to move files from the old drive to the new drive 1.2. Collect and store URLs of folders for each member to find their files quickly 1.3. Draft email template with directions, including URLs 1.4. Review with Bonnie before contacting. 1.5. May require 1 on 1 time with persons owning a lot of files
  2. Spent time testing the LA City service request URLs to see how we might create a bookmarking feature. #959 2.1. Has this ever been brought up by a user? 2.2 Don't duplicate services - does LA City already offer or will offer a notification system? 2.3 Use Case Guess - show as evidence for requests that are marked closed when they haven't actually been serviced

EchoProject avatar Oct 27 '21 01:10 EchoProject

2021-11-02

  1. Quick run-through of the Review column on the Project Board. Made a note to discuss with the team the PR review process. Commented on a FrontEnd issue for additional discussion details in the comments.
  2. Reviewed line items from https://github.com/hackforla/311-data/issues/801#issue-692620071 mainly regarding some UX notes from v1.
  3. Based on one of the line items from the above: Eric will create an issue to have "How to Submit a Service Request" added to the FAQ.
  4. After some design review, suggest a change to the about page using an Analysis Page color palette.
  5. Eric will reach out to Dana Chen to schedule to re-discover intelligence from prior user testing and research.
  6. Eric will reach out to Adam Kendis to confirm scheduling in regards to new developer onboarding.
  7. Reviewed Google Drive Migration video tutorial and File Owner Sheet.
  8. Eric will make some edits to the video for another review before reaching out to File Owners.

EchoProject avatar Nov 02 '21 23:11 EchoProject

2021-11-09

  1. Discussed having a suggestion box for new features that are not derived directly from research. We can possibly create a new label that states if the Issue is research-based. We can create a spreadsheet that maps ideas and research.
  2. The Peer Review documentation will be added to the Wiki once the Wiki is ready to be worked on. At this time, we are waiting for the completion of the Google Drive migration so that we can own and work with the existing files.
  3. Discovered existing Figma account for 311-Data. We will be migrating all previous designs to this new account. Bonnie will work with Dana and Nate on the migration. Eric will invite current active team members to the new account at the team meeting.
  4. Icebox clean up.

EchoProject avatar Nov 12 '21 00:11 EchoProject

2021-11-16

  1. PM Team meeting will be changed to Tuesdays at 3 pm.
  2. 311-Data Team meeting Zoom link has been updated and the host key is available in the 311-Data 1Password vault.
  3. Bonnie set up a meeting request with Dana to discuss Google Drive and Figma migrations.
  4. Updated the #808 to include further details on dependency, dev tickets, and testing.
  5. Moved #1154 and #1155 to the Review Board from Icebox to confirm status.

EchoProject avatar Nov 16 '21 22:11 EchoProject

2021-12-6

  1. Changed PM Team meeting scheduled for Dec. and Jan. 12/17 will be on Friday at 4pm. 12/20 and 12/27 will be on Monday at 3pm. Starting in January, the meetings will remain on Fridays at 4pm.
  2. Reviewed label audit issue #1134 and added another set of links for auditing.
  3. Discovered 311 MVP project board that has been closed. Went through open issues. These issues will need to be reviewed with Adam and moved to the current board as necessary.

EchoProject avatar Dec 11 '21 00:12 EchoProject

Agenda and Minutes 2021-12-17

(this was original posted on 12-17 on another issue https://github.com/hackforla/311-data/issues/1161#issuecomment-997103445

Prework

  • [ ] label audit #1134

Roll Call

Bonnie, Lexi, Eric

Recurring items:

  • [x] review any issues that are in the new issue approval column
  • [ ] Accountability and Support Check
  • [ ] finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] review issues with epic label and define how to break down further

New Items

  • [ ] Icebox review to see what is going on with the issues with no dependency
    • pushed to next meeting

Actions taken or notes about stuff from the meeting:

  • We performed the audit during the meeting. There was no significant change since last week.
  • Brought back a job posting from the filled column and edited it. To recruit for designer

New Task Items

  • [ ] Add to next weeks agenda, scheduling next steps for driving the labels missing count down, if it has not changed.
  • [ ] Lexie to Follow up with Chelsey to see all the issues she is currently assigned to that affect the project and prioritize what we need to know. https://github.com/hackforla/311-data/issues/1137
    • [ ] Has she worked on this at all (including just writing documentation https://github.com/hackforla/311-data/issues/699) and can she estimate size
  • [ ] Eric will review the icebox for the issues that don't have a dependency to see what we need to do next https://github.com/hackforla/311-data/projects/10?card_filter_query=-label%3Adependency
  • [ ] Make roadmap issue and add links
  • [ ] Eric to combo these two issue together (this agenda issue and issue #1136)

ExperimentsInHonesty avatar Dec 20 '21 23:12 ExperimentsInHonesty

Agenda and Minutes 2021-12-20

(this was original posted on 12-20 on another issue #1161 (comment)

Prework

  • [x] label audit #1134

Roll Call

Bonnie, Eric

Recurring items:

  • [x] review any issues that are in the new issue approval column
  • [x] Accountability and Support Check
  • [ ] finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] review issues with epic label and define how to break down further

New Items

Actions taken or notes about stuff from the meeting:

  • Lexie has not yet left any notes on her issue to follow up with Chelsey. Bonnie asked for update. Issue will be carried into next meeting
  • Answered Erics questions about how to combo the agenda issues and meeting notes
  • We combined these two issue together (this agenda issue and issue #1161 )
  • Moved #829 to the review column to find out what Adam meant by the original issue
  • reviewed ice for the dependencies and there was no issues to release

New Task Items

  • [x] scheduling next steps for driving the labels missing count down, if it has not changed.
  • [x] Lets see if Lexie to Follow up with Chelsey to see all the issues she is currently assigned to that affect the project and prioritize what we need to know. https://github.com/hackforla/311-data/issues/1137
    • [ ] Has she worked on this at all (including just writing documentation https://github.com/hackforla/311-data/issues/699) and can she estimate size
  • [x] Eric will review the icebox for the issues that don't have a dependency to see what we need to do next https://github.com/hackforla/311-data/projects/10?card_filter_query=-label%3Adependency
  • [x] Did a roadmap issue get made - Yes it did https://github.com/hackforla/311-data/issues/1162
  • [x] Did Eric to combo these two issue together (this agenda issue and issue #1136)

ExperimentsInHonesty avatar Dec 20 '21 23:12 ExperimentsInHonesty

Agenda and Minutes 2021-12-27

Prework

Roll Call

Recurring items:

  • [x] review any issues that are in the
  • [ ] Accountability and Support Check
  • [ ] finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] review issues with epic label and define how to break down further

Items carried over from last meeting

  • [x] see if Lexie to Follow up with Chelsey to see all the issues she is currently assigned to that affect the project and prioritize what we need to know. https://github.com/hackforla/311-data/issues/1137
  • [ ] scheduling next steps for driving the labels missing count down, if it has not changed.

New Items

Actions taken or notes about stuff from the meeting:

Numbers from label audit went up by one issue, we did not spend any time reducing the numbers over the last two weeks.

New Task Items

Next agenda

https://github.com/hackforla/311-data/issues/1137#issuecomment-1007108249

ExperimentsInHonesty avatar Dec 20 '21 23:12 ExperimentsInHonesty

Agenda and Minutes 2021-01-10

Prework

Roll Call

Eric Bonnie Lexie

Recurring items:

  • [ ] review any issues that are in the
  • [ ] Accountability and Support Check
  • [ ] finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] review issues with epic label and define how to break down further

Items carried over from last meeting

  • [x] see if Lexie to Follow up with Chelsey to see all the issues she is currently assigned to that affect the project and prioritize what we need to know. https://github.com/hackforla/311-data/issues/1137
  • [ ] scheduling next steps for driving the labels missing count down, if it has not changed.

New Items

Actions taken or notes about stuff from the meeting:

Numbers from label audit went down by one issue, we did not spend any time reducing the numbers over the last 4 weeks.

Notes From Meeting

  • Decided to bring in new dev to focus on Plotly to decide if we will continue using the tech
  • Bonnie contacted remaining persons on the Drive Migration contacts list
  • Eric is taking over Wiki update

New Task Items

  • [ ] Make multiple issues for devs around Plotlydash configurations

    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features

  • [ ] Eric will create an issue for the v1 site not rendering for some users

  • [ ] Eric will create a Sheet that lists out Wiki page titles and a description

Next agenda

EchoProject avatar Jan 10 '22 23:01 EchoProject

Agenda and Minutes 2021-01-21

Prework

Roll Call

Eric Bonnie Lexie

Recurring items:

Items carried over from last meeting

  • [ ] scheduling next steps for driving the labels missing count down, if it has not changed.

New Items

Notes From Meeting

  • Bonnie recorded 311-Data project overview
  • Bonnie emailed Adam and Arnold to see if they are still working on the project
  • Reviewed In-Progress column and requested updates
  • Connected Kristen's PR to her In-Progress issue #1159

New Task Items

Next agenda

  • Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
  • Be sure to talk about #1137. Tabling due to time, but need to address Plotly Dash.

EchoProject avatar Jan 22 '22 01:01 EchoProject

FYI for next meeting I updated this card, its still had the old PMs name on it. https://github.com/hackforla/engineering/projects/2#card-54125928,

Item for meeting we should look over all the open roles posts we have and make sure they are up to date

ExperimentsInHonesty avatar Jan 27 '22 07:01 ExperimentsInHonesty

Agenda and Minutes 2021-01-28

Prework

Roll Call

Recurring items:

Items carried over from the last meeting

  • [ ] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
  • [ ] Be sure to talk about #1137. Tabling due to time, but need to address Plotly Dash.
  • [ ] We should look over all the open roles posts we have and make sure they are up to date
  • [ ] Make multiple issues for devs around Plotlydash configurations
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features

New Items

  • Meetup event to recruit engineers - first draft
  • Josh Bubar intro'd Eric to David Song (engineer) after onboarding to join 311-Data

Notes From Meeting

  • Bonnie provided feedback on the Meetup event draft.
  • Created new feature label "Roadmap" to add issues to be considered for the roadmap.
  • Ended the meeting early because Bonnie was on the road.

New Task Items

  • [x] Eric will schedule meet & greet this weekend with David Song (engineer)
  • [x] Eric will update Meetup event details - work on second draft
  • [ ] Eric will work through issues from v1 launch project board to add to post v2 roadmap

Next agenda

EchoProject avatar Jan 28 '22 02:01 EchoProject

next meeting https://github.com/hackforla/access-the-data/issues/34#issuecomment-1027350641

ExperimentsInHonesty avatar Feb 01 '22 22:02 ExperimentsInHonesty

Agenda and Minutes 2021-02-04

Prework:

Roll Call

  • [x] Bonnie
  • [x] Eric
  • [ ] Lexie
  • [ ] Pras

Recurring items:

Items Carried Over From the Last Meeting:

  • [ ] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
  • [ ] Be sure to talk about #1137. Tabling due to time, but need to address Plotly Dash.
  • [ ] We should look over all the open roles posts we have and make sure they are up to date
  • [ ] Make multiple issues for devs around Plotlydash configurations
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features
  • [ ] Work through issues from v1 launch project board to add to post v2 roadmap

Items to Discuss at This Meeting:

  • [ ] Finalize/ publish Meet Up event
  • [ ] Create slide presentation for Meet Up event
  • [ ] From Bonnie's comment above: Q: Use cases of the 311 data visualization tool A: I have added this to the 311-data PM meeting agenda, we will answer it here

Notes From This Meeting:

  • Pinged Pras for the issue: https://github.com/hackforla/311-data/issues/960
  • Pinged Lexi for the issue: https://github.com/hackforla/311-data/issues/710
  • Worked through Prioritized Backlog and updated milestones New Milestones
    • z.v2 Launch
    • 04-v2: Feature bugs
    • 05-v2: New features
    • 06-v2: User Testing
    • 07-v2: Proposals
    • Security & Compliance
    • Data/ Build Pipeline

New Agenda/ Task Items for Next Meeting:

EchoProject avatar Feb 05 '22 00:02 EchoProject

Agenda and Minutes 2021-02-11

Prework:

Roll Call

  • [x] Bonnie
  • [x] Eric
  • [ ] Lexie

Recurring items:

Items Carried Over From the Last Meeting (Try to keep this list empty):

  • [ ] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
    • [ ] Have a model now, go through history, 311 interactions with NCs

v2 Data visualizations

  • [ ] Make multiple issues for devs around Plotlydash configurations
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features
  • [ ] Work through issues from v1 launch project board to add to post v2 roadmap
  • [ ] Be sure to talk about #1137. Tabling due to time, but need to address Plotly Dash.

Dev Recruiting

  • [ ] Clean and queue up development tickets for new engineers joining the team
  • [ ] We should look over all the open roles posts we have and make sure they are up to date
  • [ ] Finalize/ publish Meet Up event
  • [ ] Create slide presentation for Meet Up event

Items to Discuss at This Meeting:

  • [ ] From Bonnie's comment above: Q: Use cases of the 311 data visualization tool A: I have added this to the 311-data PM meeting agenda, we will answer it here - Dependent on Eric completing the digging up on the original research.
  • [ ] Create issues for missing features in the v1 vs. v2 Feature Comparison

Notes From This Meeting:

New Agenda/ Task Items for Next Meeting:

EchoProject avatar Feb 12 '22 00:02 EchoProject

Agenda and Minutes 2021-02-18

Prework:

Roll Call

  • [x] Bonnie
  • [x] Eric

Recurring items:

  • [ ] Review any issues that are in the
  • [x] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
    • [x] Have a model now, go through history, 311 interactions with NCs
    • [ ] Progress update
  • [ ] Accountability and Support Check
  • [ ] Finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] Review issues with epic label and define how to break down further

Items Carried Over From the Last Meeting (Try to keep this list empty):

v2 Data visualizations

  • [ ] Make multiple issues for devs around Plotlydash configurations; need to know which issues require a data scientist and which need an engineer. Some issues are posted here for DS team to self-assign.
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features
  • [x] Work through issues from v1 launch project board to add to post v2 roadmap
  • [x] Be sure to talk about #1137. Tabling due to time, but need to address Plotly Dash.

Dev Recruiting

  • [x] Clean and queue up development tickets for new engineers joining the team
  • [x] We should look over all the open roles posts we have and make sure they are up to date
  • [ ] Finalize/ publish Meet Up event
  • [ ] Create slide presentation for Meet Up event

Items to Discuss at This Meeting:

  • [ ] From Bonnie's comment above: Q: Use cases of the 311 data visualization tool A: I have added this to the 311-data PM meeting agenda, we will answer it here - Dependent on Eric completing the digging up on the original research.
  • [x] Create issues for missing features in the v1 vs. v2 Feature Comparison

Notes From This Meeting:

New Agenda/ Task Items for Next Meeting:

EchoProject avatar Feb 19 '22 00:02 EchoProject

Please add to our next agenda Let's discuss you adding this CTA to your team agenda

ExperimentsInHonesty avatar Mar 16 '22 19:03 ExperimentsInHonesty

Agenda and Minutes 2021-02-18

Prework:

Roll Call

  • [ ] Bonnie
  • [x] Eric

Recurring items:

  • [ ] Review any issues that are in the
  • [x] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571
    • [x] Have a model now, go through history, 311 interactions with NCs
    • [ ] Progress update
  • [ ] Accountability and Support Check
  • [ ] Finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] Review issues with epic label and define how to break down further

Items Carried Over From the Last Meeting (Try to keep this list empty):

v2 Data visualizations

  • [ ] Make multiple issues for devs around Plotlydash configurations; need to know which issues require a data scientist and which need an engineer. Some issues are posted here for DS team to self-assign.
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features

Dev Recruiting:

  • [ ] Eric will create issues for recruiting for roles
  • [ ] Finalize/ publish Meet Up event
  • [ ] Create slide presentation for Meet Up event

Items to Discuss at This Meeting:

  • [ ] Wiki directory topology

Notes From This Meeting:

New Agenda/ Task Items for Next Meeting:

EchoProject avatar Mar 18 '22 23:03 EchoProject

Agenda and Minutes 2022-03-25

Prework:

Roll Call

  • [x] Bonnie
  • [x] Eric

Recurring items:

  • [ ] Review any issues that are in the

  • [ ] Accountability and Support Check

  • [ ] Finish adding labels to the issue that are still missing them (see audit links above)

  • [ ] Review issues with epic label and define how to break down further

  • [x] Bonnie working with Bernard from Open Community Survey. He is adding all the NC logos and we need to add to the figma the names of the NCS we have had relationships with and link a document with details to the figma #571

    • [x] Have a model now, go through history, 311 interactions with NCs
    • [ ] Progress update

Items Carried Over From the Last Meeting (Try to keep this list empty):

v2 Data visualizations - (Eric's note: Should we pass this to Anupriya as an initial area to research?)

  • [ ] Make multiple issues for devs around Plotlydash configurations; need to know which issues require a data scientist and which need an engineer. Some issues are posted here for DS team to self-assign.
    • [ ] Legends on the charts SCSS
    • [ ] SCSS to make it look the same as the rest of the product
    • [ ] List of features

Dev Recruiting:

  • [ ] Eric will create an Epic that encompasses 311-Data recruiting practices for all relevant teams

(Eric's Note: We may want to look internally with the Org for eng looking to build leadership skills. I think the below the is a less effective path to finding a driven TL)

  • [ ] Finalize/ publish Meet Up event
  • [ ] Create slide presentation for Meet Up event

Items to Discuss at This Meeting:

  • [ ] Role specific time commitments - e.g. research
  • [ ] Product meeting structure - prioritization - Highest Level needs first
    • [ ] Define (write down) product mission and vision (all decisions must map back to these statements)
      • [ ] Strategy - Encompasses our standard practices
    • [ ] Project clean up
      • [ ] New Google Drive - Eric is working on issue
      • [ ] Wiki update - Eric is working on issue
      • [ ] Recruiting practices - Eric is working on issue
      • [ ] Find TL - Can Bonnie find support from other teams
      • [ ] Project Board prioritization
    • [ ] Consider MVP (rather than mapping features from v1) for v2
    • [ ] Frame roadmap around monthly sprints - Eric will create supporting Miro documents
      • [ ] 1-3 issues/ week/ member
      • [ ] 1 peer review/ month (only eng activity for 1 week)
      • [ ] 1 launch/merge/ month

Notes From This Meeting:

New Agenda/ Task Items for Next Meeting:

EchoProject avatar Mar 25 '22 23:03 EchoProject

Agenda and Minutes 2022-04-18

EchoProject avatar Apr 18 '22 19:04 EchoProject

Agenda and Minutes 2022-05-06

Updates:

  • [x] 1. Josh is working on a first draft of the Reports Dashboard on BI Tool because of the load on his system to run Plotly and the complexity of writing the code. Need to create an issue for this so we can track progress and have history.
  • [x] 2. May run into scaling issues using pandas library given dataset size. We'll need to revisit this with Nich before v2 launch.
  • [x] 3. Nich fixed the build pipeline and merged Edwin's last Hover Contrast PR.
  • [x] 4. Eric created an Issue for backfilling missing data from the pipeline.
  • [x] 5. Eric informed Nich of the v1 contact us form bug.
  • [x] 6. Eric will be meeting with Melissa next week to discuss design onboarding to prepare materials for updating the Wiki and consolidating Google Drive. We'll also be reorganizing the Figma to read more clearly.

Needs to get done today:

  • [x] 1. First Thursday product planning meeting confirmation - Eric setup Calendar invite for Leads
  • [ ] 2. Determine priority Issues (5-10) for eng team to launch v2 MVP (phase 1 of the v2 roadmap) see below
  • [ ] 3. If time permits:
  • [ ] - Define product vision in writing (i.e. Democratize service request data and improve community data literacy)
  • [ ] - Define North Star metric (i.e. Number of exported Reports)

Needs to get done this month:

  • [ ] 1. Schedule tutorial/ Q&A with Matt Webster (or other prior dev) to fill knowledge gaps on eng team. Target date: Late May, early June.
  • [x] 2. Eric will work with Melissa to start harmonizing the design of informational pages on v2 for launch.
  • [ ] 5. Eric will prepare a user-research plan; needs contact info and would be nice to have a UX researcher
  • [ ] 6. Eric will create a v2 roadmap via Miro - wants to remove old contributors
  • [x] 7. District shapefiles - Eric create an Issue for adding shapefiles to the map (search, data, design)
  • [ ] 8. Recruiting pipeline - Democracy Lab Hackathon

EchoProject avatar May 07 '22 00:05 EchoProject

Agenda and Minutes 2022-05-20

Updates:

  1. Eric met with Design Team on Figma housekeeping and onboarding improvements
  2. New Issue for the frontend to create https://github.com/hackforla/311-data/issues/1202
  3. New Issue for the frontend to create https://github.com/hackforla/311-data/issues/1200

Needs to get done today:

  • [x] Create Project Boards to manage Recruiting and Roadmap - Don't make new boards
  • [ ] De-escalate Data Scientist onboarding - Scheduling meeting with Ryan, Sophia, Abe, Nich, Bonnie, Eric
  • [ ] MVP launch roadmap prioritization a. Menu: Expand down, district types, query crash b. Reports: Initial summary statistics page - Single page, remove subpages - Wait until after meeting with DS Leads c. About Us: Replace Blog page with About Us - Not a priority d. Contact Us: Sends tickets to Github project - Not a priority - [ ] District shapefiles - Several existing issues a. https://github.com/hackforla/311-data/issues/849 b. https://github.com/hackforla/311-data/issues/941 c. https://github.com/hackforla/data-science/issues/141 d. https://github.com/hackforla/311-data/issues/1203

Needs to get done sooner than later:

  • [ ] Schedule tutorial/ Q&A with Matt Webster to fill knowledge gaps on eng team. Target date: Mid June - Waiting for response
  • [ ] Eric will prepare a user-research plan; needs contact info and would be nice to have a UX researcher - Not started
  • [x] Update node from 12 to 18[?] at some point **Just Note

EchoProject avatar May 14 '22 00:05 EchoProject

Please open a new issue on hackforla website repo to update the hack for la website with the team members

ExperimentsInHonesty avatar May 28 '22 21:05 ExperimentsInHonesty

We need to ask Nich to create a doc like this https://github.com/hackforla/tdm-calculator/wiki/Software-Architecture-and-Development And also include a list of all the technologies used.

ExperimentsInHonesty avatar May 30 '22 15:05 ExperimentsInHonesty

@ExperimentsInHonesty @nichhk and I were just talking about something similar in that the team should spend time, moving forward, improving the code quality of our codebase.

As of now, the soft plan is to have devs work on documentation of certain parts of the system while they complete tickets. I agree that having a single source of truth document for our architecture and system design is valuable and important.

It may take some time as our devs ramp up. For now, we can start a Wiki document and have Nich make the contributions as the team makes progress.

Does this sound like a good enough plan? I'm open to suggestions.

EchoProject avatar Jun 03 '22 00:06 EchoProject

Agenda and Minutes 2022-06-03

Updates:

Needs to get done today:

  • [ ] Issue transfer from DS to 311

Needs to get done sooner than later:

  • [ ] Review and revise, if necessary, DS issue related to Plotly
  • [x] Schedule tutorial/ Q&A with Matt Webster to fill knowledge gaps for the Eng team. Target date: Late June - Waiting for response
  • [ ] Eric will prepare a user-research plan; needs contact info and would be nice to have a UX researcher - Not started
  • [ ] Create Plotly tutorials

EchoProject avatar Jun 04 '22 00:06 EchoProject

  • https://github.com/hackforla/311-data/issues/1134#issuecomment-1159201206

ExperimentsInHonesty avatar Jun 17 '22 20:06 ExperimentsInHonesty