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.

Sign up for GitHub

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

Jump to bottom

HUU: All Team Agenda and Meeting Minutes #691

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

HUU: All Team Agenda and Meeting Minutes #691

sanya301 opened this issue May 14, 2024 · 26 comments
Assignees
@lola3736
Labels
Complexity: Small Issue has detailed instructions to resolve and the task is simple. Feature: Administrative Administrative chores, etc... Feature: Agenda points: 1 Can be done in 4-6 hours Role: PM
Milestone
w - Ongoing

Comments

@sanya301
Copy link
Member

sanya301 commented May 14, 2024 •
edited by lola3736
Loading

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
---
### Team Attendance
Executive Director - Bonnie Wolf
- Product Managers
  - [ ] Gabriella Dominic
  - [ ] Teja Machabathuni
  - [ ] Jasmine Guraya
  - [ ] Jasika Kalra
  - [ ] Ariel Lasry
  - [ ] Kiyingi Brian
  - [ ] Sanya Nijhawan (Advisory)
  - [ ] Lola Sarumi
-  Designers 
   - [ ] Jon Ilaw
   - [ ] Nicci Van
   - [ ] Amy Li
   - [ ] Priyanka Gupta
   - [ ] Nihan Durmaz
   - [ ] Jiehong Chen
   - [ ] Jaime Cucalon
   - [ ] Julia Echevarria
   - [ ] Michael Gruen
- Researchers
  - [ ] Sam Seyler
  - [ ] Jazmyne Newman
- Developers
  - [ ] Erik Guntner
  - [ ] John Wroge
  - [ ] Paul Espinosa
  - [ ] Tyler Thome
@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 •
edited
Loading

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

@sanya301 sanya301 mentioned this issue May 14, 2024
Open
@lola3736
Copy link
Member

lola3736 commented May 14, 2024 •
edited
Loading

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
Member

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 •
edited
Loading

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 •
edited by lasryariel
Loading

2024-06-04 All Team Meeting

Recurring Items

New Items and Items from Previous Meeting

Actions taken or notes about stuff from the meeting:

@ExperimentsInHonesty ExperimentsInHonesty moved this to Recurring Items in P: HUU: Project Board Jun 7, 2024
@sanya301
Copy link
Member Author

sanya301 commented Jun 12, 2024 •
edited
Loading

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
Member

lola3736 commented Jun 18, 2024 •
edited by lasryariel
Loading

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 •
edited
Loading

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

@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HUU: Project Board Aug 2, 2024
@sanya301 sanya301 moved this from New Issue Approval to Recurring Items in P: HUU: Project Board Aug 7, 2024
@sanya301
Copy link
Member Author

sanya301 commented Aug 7, 2024 •
edited by lola3736
Loading

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 lola3736 mentioned this issue Aug 8, 2024
Open
@lola3736
Copy link
Member

lola3736 commented Aug 13, 2024 •
edited
Loading

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
Member

lola3736 commented Aug 20, 2024 •
edited
Loading

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
Member

@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.

@lola3736 lola3736 assigned lola3736 and unassigned sanya301 Aug 27, 2024
@lola3736 lola3736 added the Complexity: Small Issue has detailed instructions to resolve and the task is simple. label Aug 27, 2024
@lola3736
Copy link
Member

lola3736 commented Aug 27, 2024 •
edited
Loading

2024-08-27 Agenda

Team Attendance

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

Accomplishments

Project Board Status

  • Ongoing

Actions taken or notes about stuff from the meeting:

Project Board Hygiene - Reminders

  • 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)

Summary Meeting Minutes / Notes

  • Boonie shared a design sample that depicts form completion progress, Design team to further review and determine if they can leverage.
  • Guest Profile
    • Boonie's feedback:
    • Revisit design to ensure it caters to personas with cognitive overload.
    • Previous figma may contain a close version to what she is looking for
  • Section 1: Account Creation
    • During demo, noted the following:
      • Updates made to the code resulted in errors during the demo.
  • User Research
    • Boonie provided best practices documentation for Design System currently underway
  • Next Steps:
    • Setup meeting with the Guest Persona team to discuss way forward
    • Engineering to fix bugs in Account Creation, once completed, create demo

Section 1: Account Creation

image

@lola3736
Copy link
Member

lola3736 commented Sep 3, 2024 •
edited
Loading

2024-09-03 Agenda

Team Attendance

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

Accomplishments

Project Board Status

  • Ongoing

Actions taken or notes about stuff from the meeting:

Project Board Hygiene - Reminders

  • 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)

Summary Meeting Minutes / Notes

Section 1: Account Creation

image

@lola3736
Copy link
Member

lola3736 commented Sep 10, 2024 •
edited
Loading

2024-09-10 Agenda

Team Attendance

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

#791 September Goals

Best Practices

Figma - Cleanup, Structure and Setup - Priyanka Gupta

Project Board Cleanup

#354 Weekly label and board check
#769 Project Board Hygiene - Clean Up and Alignment

@lola3736
Copy link
Member

lola3736 commented Sep 18, 2024 •
edited
Loading

2024-09-17 Agenda

Team Attendance

  • Executive Director - Boonie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers / Researchers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Sarah Kwok
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

#791 September Goals

Best Practices

Figma - Cleanup, Structure and Setup - Priyanka Gupta

Project Board Cleanup

#354 Weekly label and board check
#769 Project Board Hygiene - Clean Up and Alignment

@lola3736
Copy link
Member

lola3736 commented Sep 25, 2024 •
edited
Loading

2024-09-24 All Team Meeting Agenda and Notes

Recurring Items

New Items for discussion

  • Label standardization effort for HFLA
  • Recruitment
    • Design
    • Dev / Engineering
  • Develop MVP Roadmap
    • List All Features for the Workflow
      • PM team to provide list of features
      • Design and Dev team to review these features and provide feedback
    • Define the MVP Scope
      • Team - Identify the core, must-have features that are essential for the MVP. These are the features that solve the fundamental problem for users and will allow the software to be usable in a live environment.
    • Prioritize Features
      • Discuss and finalize prioritization methodology - (MoSCow)
        • Must-Have: Essential features for the MVP.
        • Should-Have: Important but not critical for the MVP. These can be delivered after the MVP launch.
        • Could-Have: Nice-to-have features that can be added later without affecting the core functionality.
        • Won’t-Have: Features that are not relevant at this stage but could be revisited later.
    • Validate with Stakeholders
      • Bonnie to review draft features and provide feedback
      • Team to finalize features
    • Create a Timeline
      • Team / Persona leads to work with PM to draft

Next Steps

  • PM team to provide list of features for:
    • Account Management
    • Application and Onboarding

Summary Meeting Notes

- List of features to be provided using google sheet. There is an initial attempt by previous teams, we will be leveraging this format and updating it accordingly.

  • This is an interactive process and level of details will be determined based on information provided and if it enables us to:
    • Identify features that should be included in MVP
    • Determine in and out of scope items
    • Draft an MVP roadmap and timeline

Team Attendance

  • Executive Director - Boonie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers / Researchers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jazmyne Newman
    • Jaime Cucalon
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Sep 26, 2024 •
edited
Loading

2024-10-01 All Team Meeting Agenda and Notes

Recurring Items

New Items for Discussion

Next Steps

  • Jon (Design) to:
    • Mock up design to see if its scalable to include additional questionnaires
    • Incorporate Bonnie's feedback

Summary Meeting Notes

  • Walked Bonnie through the Guest Intake profile to obtain her approval to decouple the guest and host design, given these are two distinct personas and journey.
  • Bonnie provided feedback on Guest
    • While these are 2 distinct personas and journey, the wireframes should be consistent for both, however the visual design can be distinct.

Team Attendance

  • Executive Director - Boonie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers / Researchers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jazmyne Newman
    • Jaime Cucalon
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Oct 4, 2024 •
edited
Loading

2024-10-08 All Team Meeting Agenda and Notes

Recurring Items

New Items for Discussion

Next Steps

Summary Meeting Notes

Team Attendance

  • Executive Director - Boonie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers / Researchers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jazmyne Newman
    • Jaime Cucalon
    • Sam Seyler
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Oct 15, 2024 •
edited
Loading

2024-10-15 All Team Meeting Agenda and Notes

Recurring Items

New Items for Discussion

Team Member Addition - Design

  • Michael Gruen: a is talented UX designer with almost a decade of experience in shipping products. Michael will join us and take on the role of leading design direction for the Guest and Host experience.
  • Julia Echevarria: a junior UX designer with a background in media art. She has some experience in designing for mobile and for parents and caregivers. She will join us and work on the Host experience for now while Jiehong is on vacation.

Project Timeline

  • Create timeline for current work
    • Purpose: understand current work, estimate time to complete and when we can begin to plan next milestones
Next Steps Planning
  • After completing current work, team will collectively review and decide on next priorities
  • Will assess completion of account creation phase before moving to next section
  • Plan to involve dev team in prioritization discussions for efficiency

Next Steps

Summary Meeting Notes

Team Attendance

  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jaime Cucalon
    • Julia Echevarria
    • Michael Gruen
  • Researchers
    • Sam Seyler
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

Open
17 tasks
@sammsey sammsey pinned this issue Oct 22, 2024
@lola3736
Copy link
Member

lola3736 commented Oct 22, 2024 •
edited
Loading

2024-10-22 All Team Meeting Agenda and Notes

Recurring Items

New Items for Discussion

  • Project Structure and Best Practices
    • Significant progress made across teams

HUU Workflow Design and Development - its time

  • Complete October Goals - Are we still on track to complete?
  • Review List of Features and provide feedback
  • Review current status of workflow activities
    • Section 1 - Account Creation
      • Sub-flow 1a -Coordinator Account Creation
      • Sub-flow 1b - Guest Invitation
      • Sub-flow 1c -Guest Account Confirmation
      • Sub-flow 1d - Host Account Creation
    • Status
      • Product - user stories completed
      • Design - Design completed
      • Dev - minor open items
    • Section 2 - Intake Profile & Onboarding Process
      • Sub-flow 2a: Host Intake Profile Proces
      • Sub-flow 2a: Host Intake Profile - Initial Review & Verification
      • Sub-flow 2b: Guest Intake Profile - Review & Verification
      • Sub-flow 2b: Guest Profile: Completion Process
      • Sub-flow 2e: Host In-Person Verification & Training
      • Sub-flow 2ei: Host / Coordinator Interview
      • Sub-flow 2eii: Home Inspection
      • Sub-flow 2eiii: Host Training Session
      • Sub-flow 2f: Host Profile Review & Completion Process
      • Sub-flow 2f: Host Application - Final Review & Verification
      • Sub-flow 2g: Guest In-Person Verification & Training
      • Sub-flow 2gi: Guest Coordinator Interview
      • Sub-flow 2gii: Guest Training Session
      • Coordinator Dashboard
Next Steps Planning
  • After completing current work, team will collectively review and decide on next priorities
  • Plan to involve dev team in prioritization discussions for efficiency
  • Create timeline

Next Steps

  • Complete October goals and remaining infrastructure/best practice tasks
  • Review product team's feature list and provide feedback this week
  • Determine and prioritize next work items in Section 2 (host/guest/coordinator flows)
  • Estimate timelines for prioritized work items, considering December break
  • Prepare for Bonnie's review of guest design feedback next week
  • Tyler to potentially join tonight's recruiting session for backend developer

Summary Meeting Notes

  • Discuss project progress, upcoming workflow design and development, and plan next steps for HUU's development phases.

Key Takeaways

  • Significant progress made in best practices and project structure, especially in design and dev teams
  • November focus: Workflow design and development, starting with section 2 (host/guest/coordinator flows)
  • Account creation (section 1) mostly complete; minor tasks remain (e.g., coordinator account creation flow)
  • Team to review product features and provide feedback this week
  • Bonnie joining next week's meeting to review guest design feedback

Topics

  • Project Structure and Best Practices Progress
    • Design team: Implemented design structure and best practices
    • Dev team: Worked on infrastructure and best practices with PM
    • Weekly label board showing good progress
  • Account Creation (Section 1) Status
    • Product and design perspective: Completed
    • Development:
      • Minor tasks remaining (e.g., edge case with Google signup flow)
      • To-do: Add users to groups for AWS token-based authorization
      • New flow needed: Coordinators not creating their own accounts
      • UI fix required for coordinator to add/create accounts
        Workflow Design and Development (Section 2) Planning

Focus areas

  • Coordinator: Dashboard table layout complete, working on click-through functionality
  • Host intake: Priority to complete for meaningful data population
  • Guest intake: To be worked on parallel or after host intake
  • Team to determine logical sub-areas to work on and estimate timelines
  • Product team to outline work sequence for guest, host, and coordinator flows
  • Dev team input needed on system perspective and sequencing

Technical Considerations

  • Prioritize completing upstream data (e.g., host data) before dependent coordinator functions
  • Consider system dynamics for configurability across different organizations
  • Anticipate potential state management challenges in the application
  • Improve design-engineering handoff to identify specific requirements early

Team Attendance

  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jaime Cucalon
    • Julia Echevarria
    • Michael Gruen
  • Researchers
    • Sam Seyler
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Oct 29, 2024 •
edited
Loading

2024-10-28 All Team Meeting Agenda and Notes

Recurring Items

Summary Meeting Minutes

Meeting Purpose

  • Review and discuss design updates for the guest profile and coordinator dashboard interfaces.

Key Takeaways

  • The guest profile design was approved with modifications, focusing on a button-based layout and avoiding house-building metaphors
  • The coordinator dashboard needs significant rework to improve efficiency and customization options
  • Version history and inline feedback capabilities are critical for MVP and need to be implemented for individual profile sections

Topics

  • Guest Profile Design
  • Approved button-based layout with right-side placement for better responsiveness
  • Removed numbering from buttons to allow for easy reordering
  • Decided against house-building metaphors to avoid false promises
  • Suggest conducting user testing to compare button vs. card layouts

Coordinator Intake Profile, notes and dashboard review

  • See detail review in the Design issue
  • Coordinator Dashboard
  • Current layout approved but needs more information and customization options
  • Emphasis on efficiency and flexibility for coordinators to create custom views
  • Need for searchable notes, ability to hide/show resolved items, and version history for each profile section
  • Discussion on implementing saved filters and shareable views for team collaboration
Feedback System
  • Inline feedback for each profile section is crucial for MVP
  • Need to implement a system to show changes between versions
  • Discussed potential for AI-generated summaries of feedback in the future
Technical Considerations
  • Debate on storing full version history vs. only most recent changes
  • Need to discuss with dev team about URL-based filtering and view saving
  • Potential challenges with implementing shared views and saved filters

Next Steps

  • Refine guest profile design based on feedback and prepare for user testing
  • Redesign coordinator dashboard with focus on customization and efficiency
  • Develop detailed specifications for version history and inline feedback features
  • Discuss technical feasibility of URL-based filtering and view saving with dev team
  • Create prototypes for searchable notes and version comparison features
  • Schedule follow-up meeting to review updated designs and specifications

Team Attendance

Executive Director - Bonnie Wolf

  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jaime Cucalon
    • Julia Echevarria
    • Michael Gruen
  • Researchers
    • Sam Seyler
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Nov 12, 2024 •
edited
Loading

2024-11-12 All Team Meeting Notes

Recurring Items

New Task Items

Team Attendance

  • Executive Director - Bonnie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jaime Cucalon
    • Julia Echevarria
    • Michael Gruen
  • Researchers
    • Sam Seyler
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

@lola3736
Copy link
Member

lola3736 commented Nov 20, 2024 •
edited
Loading

2024-11-19 All Team Meeting Notes

Recurring Items

New Task Items

None

Team Attendance

  • Executive Director - Bonnie Wolfe
  • Product Managers
    • Gabriella Dominic
    • Teja Machabathuni
    • Jasmine Guraya
    • Jasika Kalra
    • Ariel Lasry
    • Kiyingi Brian
    • Sanya Nijhawan (Advisory)
    • Lola Sarumi
  • Designers
    • Jon Ilaw
    • Nicci Van
    • Amy Li
    • Priyanka Gupta
    • Nihan Durmaz
    • Jiehong Chen
    • Jaime Cucalon
    • Julia Echevarria
    • Michael Gruen
  • Researchers
    • Sam Seyler
    • Jazmyne Newman
  • Developers
    • Erik Guntner
    • John Wroge
    • Paul Espinosa
    • Tyler Thome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lola3736 lola3736

Labels
Complexity: Small Issue has detailed instructions to resolve and the task is simple. Feature: Administrative Administrative chores, etc... Feature: Agenda points: 1 Can be done in 4-6 hours Role: PM
Projects
P: HUU: Project Board
Status: Recurring Items
Milestone
w - Ongoing
Development

No branches or pull requests
4 participants
@sanya301 @ExperimentsInHonesty @lasryariel @lola3736