Team Meeting Agendas 2022 07 18 - hackforla/VRMS GitHub Wiki
Monday, July 18, 2022 Meeting Agenda
Pre-work to prep for meeting
- Update issues
Who was there?
- Julia
- Judy
- Josh
- Shaun
- My
- Alex
Things we plan to discuss
-
Welcoming Alex and My to VRMS! - 10min
-
Go over how to run a team meeting in the wiki, assign responsibilities and agree on the agenda
-
Assign team members to the following roles
- Note taker - Julia
- Time keeper - Judy
- Facilitator - Joooosh
-
Design Team
- Review Google Drive documents - which ones are current and which ones should be archived and how can we maintain? - 15 min
- Alex's big questions - 5min
- Julias problem statement - 5min
-
closing and action items - 5min
-
Dev Team: Review v0.3 project board - 0min
- In progress column
- prioritized backlog
- Make sure that everyone has an issue
- Have a discussion on which issues need to be done before moving to v0.4, and which ones could potentially never be completed
What we actually discussed
- We assigned team roles and time frames to the agenda
- We introduced ourselves to the team and explained how we run meetings and keep track of the wiki page
- Josh shared his screen and showed us how we get to the wiki page
- Dev team: talk about issues on Thursday (they stayed after the meeting to talk about how the app is broken down)
- Julia briefly mentioned the needs of HfLa and the Design systems insights and concerns:
- Retention of volunteers
- Lack of documentation
- Offboarding
- We went over the drive documents and focused on: MVP v0.4 requirements.
- Discussing the scope and goal for v4
- We are designing for desktop first
- We are going over users and their needs focusing on general volunteers
- Dev team should look over the dev folders in the drive to decide what’s still relevant
- Design team will define a new problem statement and create a new user flow to focus on for v4
Additional notes
Next meeting
- demo the current v0.4
Action items
- shaun and josh, look at the broken app
- shaun prep the demo of v0.4
- josh review shaun pr
- josh needs to recruit devs
- finalize problem statement
- develop a new user journey onboarding specific from volunteer point of view