Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HUU: All Team Agenda and Meeting Minutes #691

Open
sanya301 opened this issue May 14, 2024 · 14 comments
Open

HUU: All Team Agenda and Meeting Minutes #691

sanya301 opened this issue May 14, 2024 · 14 comments
Assignees
Labels
Feature: Administrative Administrative chores, etc... Feature: Agenda points: 1 Can be done in 4-6 hours Role: PM
Milestone

Comments

@sanya301
Copy link
Member

sanya301 commented May 14, 2024

Overview

This issue tracks the agenda for the HUU: All Team meetings for the HomeUniteUS project

Resources/instructions

Copy template and comment on issue for each week's meeting.

Minutes Template

## 2024-05-1 All Team Meeting Notes

### Prework to prep for meeting
- [ ] Team leads/members provide updates on issues in GitHub before Tuesday
- [ ] Team lead adds to agenda topics before Tuesday
- [ ] PM Reviews #890 
  - [ ] Icebox column
  - [ ] Prioritized backlog column

#### Recurring Items
- Monthly goals (add link to this month's issue)
- Review https://dev.homeunite.us/ in engineering section
- [Project board check](https://github.com/orgs/hackforla/projects/62/views/1?filterQuery=is%3Aopen+)
- Open questions for the team
- Any demos for the team? (fill in planned demos or remove bullet)

#### New Items and Items from Previous Meeting

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

#### New Task Items
@sanya301 sanya301 self-assigned this May 14, 2024
@sanya301 sanya301 added this to the x- Continuous milestone May 14, 2024
@sanya301 sanya301 changed the title HUU: All Agenda and Meeting Minutes HUU: All Team Agenda and Meeting Minutes May 14, 2024
@sanya301
Copy link
Member Author

sanya301 commented May 14, 2024

Created this new issue to separate out agendas for different meetings. Copying last few meetings here for context. These were prior all in #364 with the title
yyyy mm dd All Team Meeting Notes

January 2024:

Key items summary

February 2024:

Key Items summary

  • February 2024 goals #653
  • API authentication (cognito + IAM) is complete!
  • Signature: checkbox sufficient for MVP
  • Rename application to something else (like profile), Combine application and profile
  • "Signature" - agreement that instead of at the end of the application signature, we will do an acknowledgement when they sign up for their account
  • Data model HMIS: vendor who Bonnie wanted to collaborate us with is no longer helping us
  • Mobile Guest Application Figma demo

March 2024

Key Items summary

  • March 2024 goals #664
  • Design demo: coordinator dashboard last demo from Kayla
  • Final Naming decision for application and viewable profile - Intake Profile (fka application) and Matching Profile
  • Auto save: As a Team we decided that may be a pop up box will be shown if the user tries to move from one section to another without completing all fields. Pop Up will provide warning that the info will be lost if moved to another section. Design needs to come up with Pop up design and PM team to work on wording
  • Guest section 2 Figma demo (dashboard + application) shown to team

April 2024

Key Items summary

  • April 2024 goals #673
  • Matching guest view page story shown to team
  • Homeowners/renters insurance needs to be added to Host + re-review for host needed
  • Update labels/milestones/projects for all issues
  • Board cleanup meeting: May 28

@sanya301
Copy link
Member Author

2024 05 07 All Team Meeting Notes

Agenda

  • May goals May 2024 Goals #689
  • Section 1 demo: sign up/sign in process for Guest, Host and Coordinator
  • Open questions/board check
  • Update labels/milestones/projects for all issues
  • Board cleanup: May 28

Notes

@lola3736
Copy link

lola3736 commented May 14, 2024

2024-05-14 All Team Meeting Notes

Recurring Items

  • Monthly goals May 2024 Goals #689
  • Review https://dev.homeunite.us/ in engineering section
  • Open questions for the team
  • Any demos for the team?
    • Section 1 demo: sign up/sign in process for Guest, Host and Coordinator - when can we schedule?

New Items and Items from Previous Meeting

  • Engineering questions from PMs: Create a dev questions issue, post that in slack (confirm status)
  • @baipai did we ask TDM calculator team to do a demo for filters (Yiran) Design Mockup: Redesign the My Projects Filtering UI tdm-calculator#1578 (confirm status)
  • Reminder:
    • Update labels/milestones/projects for all issues
    • Project Board cleanup: May 28
    • Smaller engineering user stories - add all to monthly goals

Actions taken or notes about stuff from the meeting:

New Task Items

Notes

@lola3736
Copy link

2024-05-21 All Team Meeting Notes

Recurring Items

New Items and Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

@lasryariel
Copy link
Member

lasryariel commented May 24, 2024

2024-05-28 All Team Meeting Notes

  • Bonnie will be conducting a training on Project Hygiene. It is unlikely we will have time for any of the items below.

Recurring Items

New Items and Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

@sanya301
Copy link
Member Author

sanya301 commented Jun 4, 2024

2024-06-04 All Team Meeting

Recurring Items

New Items and Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

@sanya301
Copy link
Member Author

sanya301 commented Jun 12, 2024

2024-06-11 All Team Meeting Notes

Recurring Items

New Items and Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

  • Ice box items need to be updated by next team meeting
    • Add a heading dependency
    • Describe what the dependency issue, or link issue under the header
    • Add label:dependencies
    • Whatever doesn't have a blocker or dependency, goes into new issue approval
    • Engineering: @tylerthome @erikguntner
    • Design/Research: @edela0015
    • PM: @sanya301
  • Section tickets so that it is scoped to one person and one team working on it

New Task Items

  • If we want to have user testing then we want to have user journeys for coordinators. High level flow for A to Z in our minds
  • Coordinator epic (user journey) needs to be updated and presented to the design team. Define by end of this section, coordinator needs to do this @lasryariel
  • @lasryariel update filter user story to define name filter requirements if any, and use cases for search bar
  • Create a listing for a user researcher? @edela0015
  • Check with engineering on acknowledgement placement

@lola3736
Copy link

lola3736 commented Jun 18, 2024

2024-06-18 All Team Meeting Notes

Recurring Items

New Items

  • Migrate and update open roles to new/upgraded system with new protocol

Items from Previous Meeting

  • Status of Project Hygiene cleanup
    • Completed: Label Role split for UI/UX - updated with "Design" or "Research" role
    • Home Unite Us Team Roster - please provide information for missing items highlighted in "pink" (PM to review and determine if missing items are critical)
    • Project board check please review and close accordingly, leads please assist.
      • Engineering: @tylerthome @erikguntner
      • Design/Research: @edela0015
        • Ice box items need to be updated by next team meeting
        • Ice Box 3/3 do not have dependency label
          • Add a heading dependency
          • Add label:dependency
          • Describe what the dependency issue, or link issue under the header
          • Whatever doesn't have a blocker or dependency, goes into new issue approval
        • Add points to this issue Implement Forms API #636
      • Section tickets so that it is scoped to one person and one team working on it (status?)
  • Create a listing for a user researcher? @edela0015
    • Create role issue for role research (to include upcoming / future research to be performed)
  • Check with engineering on acknowledgement placement
    • Confirm where tracking is placed
      • At point when guest invite link is clinked? temporary password is generated or before?
      • Are there multiple points of tracking?

Actions taken or notes about stuff from the meeting:

  • PM: completed updated PM related Ice Box issues
  • Design: replaced UX/UI with "Research" or "Design" for all open issues

New Task Items

@lasryariel lasryariel added the points: 1 Can be done in 4-6 hours label Jun 19, 2024
@lasryariel
Copy link
Member

lasryariel commented Jun 25, 2024

2024-06-25 All Team Meeting Notes

HackforLA takes off for July, no team meetings throughout July. Next Meeting 8/6

Recurring Items

New Items

  • Open roles need to be posted before the break

Items from Previous Meeting

  • Status of Project Hygiene cleanup
    • Home Unite Us Team Roster - please provide information for missing items highlighted in "pink" (PM to review and determine if missing items are critical)
    • Project board check please review and close accordingly, leads please assist.
      • [ ]Add points to this issue Implement Forms API #636
      • Section tickets so that it is scoped to one person and one team working on it (status?)
  • Create a listing for a user researcher? @edela0015
    • Create role issue for role research (to include upcoming / future research to be performed)
  • Check with engineering on acknowledgement placement
    • Confirm where tracking is placed
      • At point when guest invite link is clinked? temporary password is generated or before?
      • Are there multiple points of tracking?

Actions taken or notes about stuff from the meeting:

New Task Items

@sanya301
Copy link
Member Author

sanya301 commented Aug 7, 2024

2024-08-06 Leads Meeting Notes

Suggested agenda for leads (none of this we got to)

Items from Previous Meeting

  • Status of Project Hygiene cleanup
    • Home Unite Us Team Roster - please provide information for missing items highlighted in "pink" (PM to review and determine if missing items are critical)
    • Project board check please review and close accordingly, leads please assist.
      • [ ]Add points to this issue Implement Forms API #636
      • Section tickets so that it is scoped to one person and one team working on it (status?)
  • Create a listing for a user researcher? @edela0015

Actions taken or notes about stuff from the meeting:

New Task Items

  • Nothing in prioritized backlog should be assigned to a person
  • Have design issue created for each issue, then add design issue as a dependency issue for product issue. Last checkbox in design issue should be to put it as ready for:product, Ready for review
  • Priotitized backlog readiness
    • Engineering need to look at all issues in prioritized backlog to make sure they are ready for work
  • New Issue approval readiness
  • Everyone to look at their issues, see if there are a lot of issues assigned, and assign labels for specific skillsets needed. One person should be assigned to only one issue (besides epics, agendas), everything else to go back to prioritized backlog

@lola3736
Copy link

lola3736 commented Aug 13, 2024

2024-08-12 Agenda

Suggested agenda for leads

Team Introduction and Structure

  • Product Manager
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Lola Sarumi
  • Design
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
  • Developers
    • Tyler Thomas
    • Erik Guntner
    • John Wroge
    • Jose Padilla
    • Paul Espinosa
  • Monthly goals August Goals 2024 #739 planning
    • Status of Project Board Hygiene cleanup (https://github.com/orgs/hackforla/projects/62/views/1?filterQuery=is%3Aopen+). Are there any issues that are no longer relevant/applicable, review and close.
      • All issues should have the following 5 labels assigned (assign labels for specific skillsets needed):
        • Complexity
        • Milestone
        • Role
        • Feature
        • Points
      • Nothing in prioritized backlog should be assigned to a person
      • Have design issue created for each issue, then add design issue as a dependency issue for product issue. Last checkbox in design issue should be to put it as ready for:product, Ready for review
      • Prioritized backlog readiness
      • Engineering need to look at all issues in prioritized backlog to make sure they are ready for work
    • New Issue approval readiness
      • Review issues to ensure there is only 1 issue per person - this will assist in understanding project needs and status. One person should be assigned to only one issue (besides epics, agendas), everything else to go back to prioritized backlog.
    • Home Unite Us Team Roster - please provide information for missing items highlighted in "pink" (PM to review and determine if missing items are critical)

Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

New Task Items

@lola3736
Copy link

lola3736 commented Aug 20, 2024

2024-08-19 Agenda

Team Attendance

  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Sarah Kwok
  • Developers
    • Erik Guntner
    • John Wroge
    • Jose Padilla
    • Paul Espinosa
    • Tyler Thome

Proposed Templates / Workflow

Project Board Status

  • Ongoing

Actions taken or notes about stuff from the meeting:

Project Board Hygiene - Reminders

  • August Goals 2024 #739
  • All issues should have the following 5 labels assigned (assign labels for specific skillsets needed):
    • Complexity
    • Milestone
    • Role
    • Feature
    • Points
  • Nothing in prioritized backlog should be assigned to a person
  • Have design issue created for each issue, then add design issue as a dependency issue for product issue. Last checkbox in design issue should be to put it as ready for:product, Ready for review
    • Prioritized backlog readiness
    • Engineering need to look at all issues in prioritized backlog to make sure they are ready for work
  • New Issue approval readiness
    • Review issues to ensure there is only 1 issue per person - this will assist in understanding project needs and status. One person should be assigned to only one issue (besides epics, agendas), everything else to go back to prioritized backlog.
  • Home Unite Us Team Roster - please provide information for missing items highlighted in "pink" (PM to review and determine if missing items are critical)

Items from Previous Meeting

  • Focus on project board hygiene cleanup
  • Breakdown MVP-6 milestones

New Task Items

@lasryariel
Copy link
Member

Please add these items to tomorrow's agenda:

General:
Discuss sub-milestones #741 (comment)

Design/PM
review design issue template with design
https://github.com/hackforla/HomeUniteUs/pull/743/files?short_path=09c92e2#diff-09c92e22f47f8fbb2b54ae29bbacec68bc94a46036f97fbe14cea1759e236dfe

Engineering:
Discuss adding more high commit volunteers (12+ hours)
get dev meeting moved to homeuniteus calendar and add to vrms to show on website - https://vrms.io/login

review engineering issue template
#745

@lola3736
Copy link

@lasryariel
See my comments in #741, we need a bit more work on determining the milestones before discussing further with the team.
Engineering - Tyler will come back with his team structure. I need to look into whether we can ask more time from Engineer commitment given everyone is at 6.5hrs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Administrative Administrative chores, etc... Feature: Agenda points: 1 Can be done in 4-6 hours Role: PM
Projects
Status: Recurring Items
Development

No branches or pull requests

4 participants