Lucky Parking: Team Agenda and Meeting Minutes

[MichelleRT]

Overview

This issue tracks the agenda for our weekly meetings so that all team members can:

• look back on the history
• get up to speed faster
• contribute more effectively

Issue Template

## [Date ]  Meeting Agenda
- (Mondays at 6 PM PST)

### Prework to prep for meeting
- [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

### Recurring items: 
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/lucky-parking/projects/3#column-17941639)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team member
- [ ] 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
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ]  #

### New Items
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items
- Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369 

Links to other agenda issues for your team

(so that you can easily post on their agendas items that come up at yours)

Previous Meetings (link to each comment with the date)

[MichelleRT]

[2022-03-21] Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items: Happens on the meeting

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Show slide during the Monday team meeting https://docs.google.com/presentation/d/1UDHwTQ1C3y01CiNS0mvPjNBHJFlm2Txs/preview?slide=id.gf3a838ce5f_2_0
• [ ] Clarification that our end user is a community activist
• [ ] LP: drive migration invite these people to the next PM/Org meeting
• [ ] Ice Box issues should either be dependencies or issues that must be completed; otherwise, new issues should be in the New Issue Approval column
• [ ] Slack poll for the 2 hour weekend hackathon on Saturday, 4/9 from 12 pm - 2pm PST
• [ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

[tmlin1]

Notes from Meeting

• UX team is done with prototype and needs to meet one last time before user testing (Yen will be testing on friends first)
• UX team will meet on Thursday morning to do final fixes and contact Seymour's contact
• Took screenshot for Hack for LA Homepage link
• Google Drive - can't reach a few folks that are inactive which is why there have been new copies
• Prioritized backlog is higher than ice box - issues that need to work on priority should be in prioritized backlog. New issue approval for issues to get into ice box, they need to go through the New Issue Approval.
• Hackathon session - need to formalize an agenda
• Github Admin rights for Michelle and Tiffany?

[tmlin1]

[2022-03-28] Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] 2FA Kick Out from GitHub access - Go to Onboarding Meeting on 4/12 (45 mins in) or join Thursday PM meeting at 7:30am pst
• [ ] Add LinkedIn to Roster: https://docs.google.com/spreadsheets/d/1OGhwJFgaNhgLfHF19E1e3JuF4wnbtfSo/edit#gid=1607893055
• [ ]

FYIs

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[MichelleRT]

• See if we need to update the team page on the main Hack for LA website https://www.hackforla.org/projects/lucky-parking
• The date part of the page is not fixed yet but the address part is fixed - Matt will try to fix the date this week.
• UX testing their design on Thursday, tentative 1 PM PST
• http://www.luckyparking.org/ is the correct website

[MichelleRT]

2022-04-04 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gregpawin]

2022-04-11 Meeting Agenda

• (Mondays at 6 PM PST)

FYIs

• @gregpawin taking over meeting minutes.

Notes from Meeting

• Will need some time to catch up on board hygiene while new PMs are being recruited
• Collected team title names. Will send ticket for updating project page this week.
• Devs are working on some backend issues and waiting for new design approval
• UI/UX is going to interview a new user
• Data is working on EDA colab notebook
• Discussed moving all tasks to the main board

[gregpawin]

2022-04-11 Meeting Agenda

• (Mondays at 6 PM PST)

FYIs

• @gregpawin taking over meeting minutes.

Notes from Meeting

• Will need some time to catch up on board hygiene while new PMs are being recruited
• Collected team title names. Will send ticket for updating project page this week.
• Devs are working on some backend issues and waiting for new design approval
• UI/UX is going to interview a new user
• Data is working on EDA colab notebook
• Discussed moving all tasks to the main board
• Update zoom link calendar, modifiable by anyone

[gordonruby]

April 18, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Add additional priority items to the agenda

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

April 25, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Add additional priority items to the agenda

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each active team member
  • [ ] Gordon
  • [ ] Greg
  • [ ] Yujin
  • [ ] Marie Li
  • [ ] Matthew
  • [ ] Seymour
  • [ ] Yen Phan
  • [ ] Glen
  • [ ] Diedrich
  • [ ] David
  • [ ] Michael
  • Assigned but not currently active
  • [ ] Tiffany
  • [ ] Michelle
  • [ ] Mrtmrt
  • [ ] Salice
  • [ ] mg78856
  • [ ] Abreeze
  • [ ] Andy
  • [ ] Hyomi
  • [ ] mminamina
  • [ ] Zephman
  • [ ] Aldaws003
  • [ ] pammyworld
  • [ ] parkderick
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard
• [ ] Determine who is communicating with stakeholders and how are they doing it:
  • [ ] Does Greg want mail forwarding?
  • [ ] Do Zach and Yen need to be on mail forwarding
  • [ ] Do we need a UX email as a second email?

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

May 2, 2022 Meeting Agenda

• (Mondays at 6 PM PST)
• https://us02web.zoom.us/j/89121722043?pwd=VFlhSUlzbVhpNVBqQmNWd1lSMWFWZz09

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each active team member
  • [ ] Gordon
  • [ ] Greg
  • [ ] Yujin
  • [ ] Marie Li
  • [ ] Matthew
  • [ ] Seymour
  • [ ] Yen Phan
  • [ ] Glen
  • [ ] Diedrich
  • [ ] David
  • [ ] Michael
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Carry over Items to next meeting that don't get addressed
• [ ] Based on the current updated roster, does everyone have the access they need? https://docs.google.com/spreadsheets/d/1rtou2FkVwKV7-2RKiRDXb2uAq_w0jHakFydzUhoW2dU/edit#gid=1467771315
• [ ] Note the address of the new roster sheet in a Google sheets format.

FYIs

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

May 9, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Issue Bash

• [ ] Following the meeting with Bonnie last week and our video recording for how to add all key details to an issue, let's break into groups and complete all key details for the rest of the issues on the Main Project Board.
  • [ ] UX/UI
  • [ ] Dev
  • [ ] Data
  • [ ] Product
• [ ] Let's finish adding labels to the issues that are still missing them (see audit links above)

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs / Check-ins

-Can we agree that the hypothesis for Hack for LA (and Lucky Parking as well) is that Neighborhood Councils can better advocate for themselves if they have the tools they need (like Lucky Parking) to do informed data analysis? -Can we agree that the main goal of Lucky Parking right now is to build an MVP based on what it would take for Neighborhood Councils to embed the Lucky Parking interface on thier websites? -How close are we to understanding from Neighborhood Councils what it would take? -What is left to do to get them to this point? How do we know? -How would we describe our efforts to use the Transportation Related Committee Members list? -To what extent have we considered using Hack for LA volunteers to do user testing? -Who on the Lucky Parking team (if not Matthew) can work with John from Food Oasis to apply the work he's doing on Districts to the Lucky Parking interface?

Notes from Meeting

-We have a couple of interviews that we need to synthesize and see trends from these user interviews -We could use another UX person -We need more devs, more front end than back end -Neighborhood Councils don't use the citation data and they don't know what they would use it for. Right now, they go to Google and research. -So for now, our goal is to find the ideal spot where they might be able to use it for specific cases. -We need to get LP live and add GA so that we can embed. -We need to finish up our test, then we'll fine tune our high fidelity prototype and then we'll know soon what it would take to appeal more to Neighborhood Councils. -We agreed that we need better documentation -We agree that we are struggling with continuity and we need to find more people to increase our bandwidth. -This week, we will brainstorm ways to find more people to add to the team. We could use more people on Dev (senior), Data (senior) and UX/UI (junior)

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

May 16, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354
• [ ] Workings meetings per team vs larger alignment / strategy meetings

The hours:

• [ ] Breakout rooms for each team (45 mins)
  • [ ] Assign a note taker and someone to share key items after the breakout room
• [ ] Big room summaries from each team (15 mins)
  • [ ] Each team shares key takeaways
  • [ ] Gordon will add them to those below to Notes from the Meeting

New Items

• [ ] Carry over Items to the next meeting that don't get addressed

FYIs

Notes from Meeting

Dev

• Assigned new task #309 that can be worked on without affecting refactor for the new design
• Went over the new project board
• Went over last PR

Data

• Discussed David's EDA notebook
• Discussed recruitment of more data volunteers
• Availability of members for projects/tasks
• Discussed #197

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

May 23, 2022 Meeting Agenda

• (Mondays at 6 PM PST)
• Zoom link: https://us02web.zoom.us/j/89121722043?pwd=VFlhSUlzbVhpNVBqQmNWd1lSMWFWZz09
• Meeting ID: 891 2172 2043

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Format:

-10 mins: Introductions for Yao and Leslie -5 mins: Gordon reports back from Org meeting with Bonnie -20 mins: breakout rooms -20 mins: main room

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

• [ ] Michael: We're making a data tool for public parking
• [ ] Michael: we're at the wireframe stage and we have one person left to interview
• [ ] Greg: Lucky Parking has great volunteers for Guidance and mentorship.
• [ ] Greg is gonna be the new data lead.
• [ ] Greg: Devs meet often during the week. Meanwhile, data meet to brainstorm new direction, but it's not all related to the current project. We need people with the time and skills to do the data engineering side of the project.
• [ ]

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[gordonruby]

June 6, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

• [ ]

Notes from Meeting

Task Items

• Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

[ychu196]

July 25, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Carry over Items to next meeting that don't get addressed

FYIs

• [ ]

Notes from Meeting

• UI/UX team wants to change the name of the project because it causes confusion to users
  • Parking Insights
  • Empower Parking
  • Impact Parking
  • Lucid Parking
• https://www.figma.com/file/R3N7mvDtlFbFgQm4OXcMih/Lucky-Parking
• Chu: Chu and Greg are going through the Project Board to clean up the tickets
• Greg: started posting for volunteer devs and ui/ux
• Michael, Yujin: Talked about rebranding; changing name of Lucky Parking to something more representative. Bonnie has said we can change the Lucky Parking name if we wish to.

Next Meeting:

The below 2 items will be recorded so we don't need to keep repeating ourselves

• History of Lucky Parking

• UX will do a demo of our MVP

• We will begin a Rebranding Exercise

• We will do a Naming Excercise as a 1st step

[ychu196]

Aug 1, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] Review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items:

• [ ] Have we done a demo of our proposed MVP to Bonnie?
• [x] History of Lucky Parking
• [x] UX will do a demo of our MVP
• [x] We will begin a Rebranding Exercise
• [x] We will do a Naming Excercise as a 1st step
• [ ] Formalize and Document Product Vision
• [ ] Update our Product Roadmap - up to MVP

FYIs

• [ ]

Notes from Meeting:

• A recording of Lucky Parking's history, our MVP was completed; Chu will post it on our wiki soon
• A naming exercise was completed; the list of names will be sent out in a survey to the general public and members of HackforLA to determine which one resonates the most; we will not be surveying Council Members or Community users(the 2 personas) as this will take too much time and is not necessary.
• Once the name has been selected, we will begin branding
• Chu will connect with Yen to formalize a 3-4month roadmap and a list of stakeholders
• Greg proposed a new feature; we agreed that it was worth pursuing
• We will continue trying to recruit developers

Next Meeting:

[ychu196]

Aug 8, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] Review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items:

• [ ] Have we done a demo of our proposed MVP to Bonnie?
• [ ] We will do a Naming Excercise 2nd step?
• [ ] Formalize and Document Product Vision
• [ ] Define our stakeholders
• [ ] Update our Product Roadmap - up to MVP

FYIs

• [ ]

Notes from Meeting:

Next Meeting:

[ychu196]

Aug 15, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Update
• [ ] Carry over Items to next meeting that don't get addressed

FYIs

• [ ]

Notes from Meeting

• discussed User Research plans for usability testing and feedback for high fidelity prototype
• discussed user research plans for building team culture, values
• broke out into working sessions for Data
• broke out into working sessins for UX
• 1 dev will be leaving us for full time work
• 1 ux designer will be leaving us for full time work

Next Meeting:

[ychu196]

Aug 22, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Chu - update team re: Q4 Roadmap and Stakeholders

FYIs

• [ ]

Notes from Meeting

• Chu updated the team with the Q4 Roadmap and Stakeholders; they have been approved by Bonnie
• Greg showcased his Data feature idea; requested feedback
• Chu, Greg, Yen will connect to get started on developing team values
• UX team broke out to breakout rooms

Next Meeting:

[ychu196]

Aug 29, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Micheal - 3min upate on progress on high fidelity

FYIs

• [ ]

Notes from Meeting

• Added Jodie to GitHub repo
• Yuting needs access to One Password and GitHub admin access
• UX team is finalizing mid fi prototype; will start on high fi prototype in 2-3 weeks
• UX team to present/record presentation on finalized mid-fi prototype for Bonnie before proceeding to hi-fi
• Yuting wants us to start thinking of Release Planning, Go to Market Strategy at a high level
• Everyone should ask around, ask colleagues, workplaces, etc. on how they do Release Planning; we can copy and paste; add our thoughts to it
• Once we have the high level Release Plan, GTM plan, we can present to Bonnie and get her fedback
• Will not be able to wait for developers before we start on hi-fi, building components, etc. since we are still recruiting for devs

Next Meeting:

• [ ] Yen - 3min update on progress on high fidelity
• [ ] Team - start fleshing out Release Planning/Go to Market strategy on high level, breakout room

[ychu196]

Sept 5, 2022 Meeting Agenda - NO MEETING; Labor day holiday

• (Mondays at 6 PM PST)

[ychu196]

Sept 12, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Yen - 3min upate on progress on high fidelity
• [ ] Team - start fleshing out Release Planning/Go to Market strategy on high level, breakout room
• [x] Mike - Personality/Mood Board Excercise

FYIs

• [ ]

Notes from Meeting

• completed Mike's Personality/Mood Board exercise
• we will need to decide a Codename which will replace Lucky Parking as we move towards building out High fidelity mockup
• removed several people from Mural, changed their statuses as necessary
• Yen will be leaving us as her full time job is taking more time

Next Meeting:

[ychu196]

Sept 19, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Ticket Clean - Chu, Greg
• [ ] GTM - Chu 3min
• [ ] Mike - Update on video demo

FYIs

• [ ]

Notes from Meeting

• Chu updated our Team doc to incorporate a GTM section

Next Meeting:

[ychu196]

Sept 26, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] Ticket Clean - Chu, Greg
• [ ] GTM - Chu 3min

FYIs

• [ ]

Notes from Meeting

Next Meeting:

[ychu196]

Oct 3, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Updated UX with feedback from Bonnie
• [x] Agreed to build Web, Web App-like?
• [x] Devs will research how to build Native Mobile app(iOS, Android, or both?)
• [x] MVP 2 will focus more on data science heavy features and use cases. ie. Thematic map overlays, AI/ML
• [x] UX will develop an A/B Test to identify temporary Code Name to replace Lucky Parking
• [x] UX will now start on High Fidelity

FYIs

• [ ]

Notes from Meeting

• [ ] Chu will confirm with Bonnie re: Maps we can use ie. Google? Mapbox?

Next Meeting:

[ychu196]

Oct 17, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Chu to update the team - 5min
• [ ] a
• [ ] b
• [ ] c

FYIs

• [ ]

Notes from Meeting

Next Meeting:

[ychu196]

Oct 24, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [ ] a
• [ ] b
• [ ] c

FYIs

• [ ]

Notes from Meeting

Next Meeting:

[ychu196]

Nov 7, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Chu will provide update on Research Templates
• [x] Start prepping for End of Year retrospective later in dec
  • [x] Design
  • [x] Data Science
  • [x] Devs
  • [x] New members
• [x] Chu, Micheal to workshop and resolve Mapbox login issues

FYIs

Notes from Meeting

Next Meeting:

[ychu196]

Nov 14, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Chu will provide update on Research Templates
• [x] Start prepping for End of Year retrospective later in dec
  • [x] Design
  • [x] Data Science
  • [x] Devs
  • [x] New members

FYIs

Notes from Meeting

Next Meeting:

[ychu196]

Nov 28, 2022 Meeting Agenda

• (Mondays at 6 PM PST)

Prework to prep for meeting

• [ ] Review PM/Org Meeting Notes https://github.com/hackforla/lucky-parking/issues/354

Recurring items:

• [ ] review any issues that are in the new issue approval column
• [ ] Accountability and Support Check.
  • [ ] Review assignments for each Team member
• [ ] 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
• [ ] Review to see if there are any members to Onboard or Offboard - [ ] #

New Items

• [x] Coduct End of Year retrospective 1 of 2(to suit people's schedules)
  • [x] Design
  • [x] Data Science
  • [x] Devs
  • [x] New members

What went well? What should we improve? What should we keep doing? How can we help your careers? What skills, tech, knowledge do you need for your jobs?

FYIs

Notes from Meeting

• December is officially the end of work; folks can continue on if they wish but resources/support from Hack4LA may not be available

Synthesis and Summary of End of Year Retrospective:

Design:

• The Design/UX team came together really well, strategic direction was clearer/better aligned now that we have stability;
• Earlier in the year we had a lot of change and hiccups, not anymore
• Training on "How to be a Design Lead"
• Need more regular interaction with devs; currently it's too adhoc;

Product:

• Build out our product roadmap in more detail; too high level
• Need to recruit more devs
• Get more aligned on vision, it's getting muddied due to changes

Devs, Data Science:

• Active mentorships/coaching – more personal touch instead of just posting tickets
• More opportunity to do Data science, data analysis, gis, data visualization, data engineering, data cleaning
• Should have documentation on setting up dev environment for PC and Mac
• More tasks for devs to do; not enough tasks for devs
• Devs want to practice by creating javascript projects, sql projects, data sciencey projects
• Learn about software architecture and technical design
• Some want more understanding of the business side of things
• How to lead and manage a dev team
• As a dev team, feels more cohesive than before

General:

• some personal initiative is necessary to develop their own skills but this is hard due to work/personal committments
• we can leave reviews of each other on LinkedIn
• Everyone is supportive and helpful - keep doing this
• Onboarding is good, meetings well organized
• Need to understand where we are at the dev side of things
• When the devs left, we were lost in terms of what they did and why they did it; Where the code is? No dev documentation

Next Meeting: