Remove old Meeting Agendas from Wiki #1636

JackHaeg · 2024-05-16T21:57:01Z

Overview

Currently, we have meeting agendas stored on both the Wiki and GitHub. Old meeting agendas stored on the Wiki need to be moved over to GitHub to centralize our meeting agendas and simplify our Wiki.

Action Items

Copy & paste each meeting as a comment on this issue, with the date as the title (format = YYYY-MM-DD)
Delete old meeting agendas from the VRMS Wiki
Add a link to this issue to the current Agenda issues on HackforLA:
- VRMS: ALL: Monday Meeting Agenda 📝 #1280
- VRMS: PM/Design Lead Meeting Agenda #1519
Delete existing Team Meeting page from Wiki

Resources/Instructions

Team meetings on Wiki can be accessed here: https://github.com/hackforla/VRMS/wiki/Team-Meetings

JackHaeg · 2024-05-20T21:27:14Z

JackHaeg · 2024-05-20T21:31:11Z

JackHaeg · 2024-05-20T21:33:18Z

JackHaeg · 2024-05-20T21:35:39Z

2022-07-21

Design Meeting Agenda

Before the meeting

Team members should update their issues

Who was there?

Judy
Josh
My
Julia
Alex
Bonnie
Shaun
Kat

Things we plan to discuss

Design Systems research findings, how VRMS goals align with HfLA needs
Adam Spar meeting
VRMS v4 goals: HfLA onboarding
New KPIs and success metrics for v4
Google drive clean out
VRMS new team members onboarding and overall organization for the current team

What we actually discussed

Design System
HFLA is implementing a design system that sets the ground rules for every team to follow.
The goal is to make an easy off-boarding process so information will retain continuity.
4 core issues:
1. Documentation / organizational memory
2. Messiness in skills levels, team components, and knowledge.
3. Knowledge gap among different roles
4. Lack of internal resources.
Adam Spar Meeting
Ask Adam how to get editor access to Figma.
What is the next step for V0.4.
Julia and Alex will sit at the next volunteer onboarding meeting.
The onboarding process has been complicated and frustrating.
Bonnie joined the Design meeting
Concerned that VRMS will be so complicated to use that she'd rather go back to the old way of managing onboarding.
Will join the Adam Spar meeting on Friday 7/22/22.
Reminded the Design team that every screen should use components.
Bonnie is the only stakeholder that matters for VRMS.
The app is not running correctly because volunteers should know which project to go to; it should replace Bonnie during onboarding.
There's a document that shows all needed features when Bonnie and Adam met for 2 months to discuss.
Figma files:
- VRMS v1.0 mood board is very important as it explain the need for VRMS to be very plain and simple (stripped down to its basic components.
- Folder "VRMS Mock - AS/BW New Screen" is the most comprehensive page that Bonnie needs.
GitHub:
- PM (Alex) should make sure that there are enough issues.
- The Kanban board needs to be cleaned up so she can recruit new developers.
- Dev Team: clean up V0.3 and V0.4 boards and have actionable issues.
- Each team will prioritize their own issues.

Additional notes

Upcoming Milestones

Action Items

Schedule Zoom meeting with Adam Spar.
Alex and Julia will clean up the Kanban board.

JackHaeg · 2024-05-20T21:36:51Z

JackHaeg · 2024-05-20T21:38:02Z

JackHaeg · 2024-05-20T21:39:24Z

2022-08-01

Team Meeting Agenda

Pre-work to prep for meeting

Update issues

Who was there?

Things we plan to discuss

Assign team members to the following roles
- Note taker - Julia
- Time keeper - Josh
- Facilitator - Alex
PM (10 mins)
- Google Migration Status Update
- Bonnie update: which features are priority
- Dev team request: Needs user stories and user journeys for V3 features prioritized

Priority:

1. Project level admins need to edit and create new meeting times
2. Bonnie needs to be able to edit user access levels to different projects
3. Bonnie needs to be able to add new project
4. Volunteer check-in

Non-Priority:

1. Delete/edit project information
2. events page
3. stats page
4. Add people to roster and search people

dev.vrms.io: share email address to get access.
Dev Team (10 mins)
- Dev recruitment updates
- Demo v4
Design Team (10 mins)
- Figma Permission update

What we actually discussed

We're trying to prioritize which features Bonnie needs to move from v3 to v4 (onboarding)
Alex send an email to Bonnie to ask about features, we’re waiting for response
Shaun will screenshot what v3 features we need to pour over
Dev team will look over the features that are priority and not and confirm them
Shaun is sharing his screen, v4:
- Create an account, enter email and password
- Sign up, get confirmation code from email
- Add first and last name
- Homepage
He will share screenshots of the components that exist for v4
The dev team has two open roles for developers in the SWE CoP
- We need to make sure we have clear issues for us to recruit devs
- We need to clean out the google drive files
Tanya did not get back to us about transferring figma ownership to VRMS
- We will probably need to go over the pages, decide which ones are relevant and duplicate them ourselves
- The design team will meet 08/02 at 7pm to tackle this
We need to sign into the VRMS Figma team project (with vrms email) to be able to duplicate files
Alex and Judy got access of v3 VRMS app

Additional notes

Next meeting:
-Workshop new v0.4 Kanban board on priority features:

1. Project level admins need to edit and create new meeting times
2. Bonnie needs to be able to edit user access levels to different projects
3. Volunteer check-in

Action Items

Design team will go over figma files and duplicate the important ones
Dev team will write specific issues to start recruiting
Dev team look over priority features and confirm them

Upcoming Milestones

JackHaeg · 2024-05-20T21:40:49Z

JackHaeg · 2024-05-20T21:41:52Z

JackHaeg · 2024-05-20T21:43:00Z

2022-08-15

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

Dev team requested breakout session to discuss database structure migration from v3 to v4
Design team to meet to discuss design sketches.

What we actually discussed

Discussed Trillium participation
Can we record meetings for Trillium? Everyone voted yes.
Use Kanban board to assign tickets asynchronously

Dev Team Breakout session

[ ]

Design Team Breakout session

Julia to create a style guide for the design team to follow
Julia over user story flows with team
User story 1: Julia
User story 2: Judy
USer story 3: My
User story 4: Julia

Additional notes

Action Items

Upcoming Milestones

JackHaeg · 2024-05-20T21:44:33Z

2022-08-18

Design Meeting Agenda

Before the meeting

Team members should update their issues

Who was there?

Things we plan to discuss

Going over 'designs for approval'
Continue to build style guide
Issues or pain points we need to address with devs

What we actually discussed

Additional notes

Upcoming Milestones

Action Items

[ ]

JackHaeg · 2024-05-20T21:45:42Z

JackHaeg · 2024-05-20T21:47:23Z

2022-08-29

Team Meeting Agenda

Who was there?

Things we plan to discuss

What we actually discussed

Josh section was moved to another time, he left to talk to Bonnie for a while, instead we’re doing intros.
- Trillium’s a bootcamp grad and self taught developer and it’s his first time meeting with VRMS.
Design team went over their bit
- We have questions for devs and we’ll use the github and kanban board to communicate them
- We have a Figma file with user flows we want to share
  - Figma filed was shared with all the devs so they can follow along the progress in design and access the deliverables they need
Alex is filling Trillium and Tim in with the history of VRMS v3 and v4
- Tim is working on a Slack app that is similar to VRMS feature wise
- We are continuing to work on VRMS with our current technologies but we would love Tim’s help and input during production, while he continues working on his project
Alex went over his slide deck. The purpose is for us to each fill in the cards with our names and to get to know each other and our work styles, etc.
Next Monday, Sept 5h is labor day! WE ARE NOT MEETING. We will resume our meetings the following Thursday Sept 8th
Design team is going to meet on Wednesday at 8pm instead of Thursday and work on finishing IA docs

Additional notes

Action Items

Fill out Team Alignment Deck by Sept. 12th

Upcoming Milestones

Agenda Backup

Things we plan to discuss

What we actually discussed

[ ]

Additional notes

Action Items

Fill in Team Alignment Deck

Upcoming Milestones

JackHaeg · 2024-05-20T21:50:27Z

2022-09-12

Team Meeting Agenda

Who was there?

Things we plan to discuss

What we actually discussed

PM

We want to make sure we prioritize our goals, bias for action we want documentation to let the next cohort know what’s going on when they join. We’ll have 2/3 week sprints and every other Monday we will have a planning meeting to establish what we work on in the next sprint.
New PRD for v.035 to make sure the team understands what is expected for this version.
- We are focusing on a few user stories (see github kanban board) and features first before moving onto v.04 Onboarding.
Let’s thing about metrics and measures about the impact we want to make with VRMS and our time in the team/project. Some metrics:
- Time it takes a user to complete a task
- Increase of active users
- Number of screens and tabs used
TDM calculator shares VRMS link everytime they have meetings but we don’t know if they actually use them
Fill out the team alignment deck by next week, MONDAY SEPT 19! please :)

DEV

People Depot building out the back end so designers can start working on lo/mid-fi wireframes to handoff to devs so they can start creating issues.
We’re talking about Tim being Dev lead and integrating or work on the Slack app he build. Tim and Josh will continue talking about it with the dev team and Bonnie.

DESIGN

The design team will meet on WEDNESDAY, SEPT 14 instead of Thursday.
We will work on User Story 4 which is the volunteer check in first in the next meeting. We’ll work collaboratively to come to an agreement on general layout and look.

Additional notes

Action Items

Upcoming Milestones

JackHaeg · 2024-05-20T21:51:24Z

JackHaeg · 2024-05-20T21:52:22Z

JackHaeg · 2024-05-20T21:54:18Z

2022-09-22

Design Meeting Agenda

Before the meeting

Team members should update their issues

Who was there?

Things we plan to discuss

Discuss flows for US 4 and 5, brainstorm wireframes
Discuss team library
Dashboard

What we actually discussed

Additional notes

Upcoming Milestones

Action Items

[ ]

JackHaeg · 2024-05-20T21:54:57Z

2022-09-26

Team Meeting Agenda

Who was there?

Things we plan to discuss

What we actually discussed

DEV

DESIGN

Additional notes

VRMS site walk through with Bonnie

Josh ( Dev ) went over the check in/admin portal

Task 1: Add new project
Task 2: Assign a user to a project
Task 3: Remove user from a project
Task 4: Edit project meeting time

Bonnie's Feedback
Task 1:

Add set locations to select from in the drop down
No validations in (GITHIB identifier (ID associated with primary repo)
GITHUB URL ( Name of org and primary repo)
Slack URL (https://hackforla.slack.com/archives/CRGH5HM0Q )
Google drive (Url of their shared drive)
Google drive url ( Url of their shared drive needs validation )
HFLA website URL ( Validate )
Video conference link ( remove for the projects) – looking for description (remove this)
```
  Task 2:
```
Assign a user to a project – Home – Admin – User management – Look up User – ( Not sure what to select after ) – Click on name – ( need to update with an edit icon )
Task 3: Remove a user from project – Admin – User management – remove
Feedback
```
  Missing user icons 
```
Task 4: Edit project meeting time – We can only edit events that already exist
Feedback
```
  Need to fix/update this feature
```
Easy to navigate, easy fixes, text seemed small/hard to read.
Judy comments: A lot of fixes, focus on fixing one task at a name, UX perspective- add project has to be specific for the user and less frustrating, etc.
Alex and Judy: Make an issue in GitHub
Go to Issues – New issue – Blank issue - Bold and underline current location for User in Menu - Add a comment under overview, add user POV and experience (the more info the better, add screenshots) - Add Action items – New issue Approval – PMs will prioritize on the back log (make sure the role and size is on there), Sprint planning – Assign, Move to in-progress, etc.
Next team meeting – Have a few issues, as a team go through them and plan for the next sprint
Judy- go through what we need to fix from a UX perspective based on Bonnies comments
Go through metrics / create measures of improvement and reiterate

Action Items

Upcoming Milestones

JackHaeg · 2024-05-20T21:57:11Z

2022-10-03

Team Meeting Agenda

Who was there?

Things we plan to discuss

What we actually discussed

DEV

DESIGN

Additional notes

Action Items

Upcoming Milestones

JackHaeg · 2024-05-20T21:58:07Z

2022-10-17

Team Meeting Agenda

What We Plan To Discuss:

Assign Roles / Recap of Previous Meeting (5 min)
V3 Priorities (high-level priorities by team based on the discussion w/Bonnie) PM/UX/Dev (15 min)
Prioritization Criteria - how we determine top priorities (5-10 min)
Survey to create metrics & measure progress (Judy - 15-20 min)
Next Steps / Action Items (15 min)

What we actually discussed - Notes here:

Team went over Bonnie's feedback from the VRMS website walkthrough.

UI/UX team is looking to prioritize Usability and functionality.
-Validate certain fields in the project form
-Work on user flow
-Events tab ( Too much confusion ) - Very difficult to change a meeting, needs a updated flow + search ability
-Consistent design throughout the site
-User friendly design functions
-Update product pages, features, and capabilities

Julia created a Survey and wants to use it a tool for feedback from Bonnie.
-How do we measure improvements? ( create a rating )
-Team is working on refining questions
-Narrowing down questions
-Divide questions by the 4 key tasks given by Bonnie

Get written feedback from bonnie to prioritize'
Work through CSS issues

Trillium and Josh ( Dev Team ) want to work on a function that allows PMs to share/Invite through the App/Website
-Project level admin access
-Focusing on V3 features
-Edit permissions for admins
-Ability to add and remove projects
-Trillium is work on the coding (site bugs)

Before & after can be found on Dev.VRMS.io

Stephanie/Alex/Amanda ( PM Team )
-Focused on prioritization

Focused on getting the team grounded and consistent on what everyone is working on ( Based on the priorities )
Clean up the board in GitHub , Keep the board updated and relevant to where we are in the project as a team , organize the information.
Find out what Bonnie needs to use the app

Next Meetings:

Thursday - Watch video, discuss issues with design team, jot down the errors and rank them.
Create a go forward plan for design and developers.

Monday - Work through results. And identify what else is preventing bonnie from using the site.

JackHaeg · 2024-05-20T21:58:54Z

JackHaeg · 2024-05-20T21:59:47Z

JackHaeg · 2024-05-20T22:08:10Z

Completed 👍

JackHaeg added role: Product feature: Agenda size: 2pt Can be done in 7-12 hours feature: Wiki labels May 16, 2024

JackHaeg added this to the 03.01 Project Management milestone May 16, 2024

JackHaeg self-assigned this May 16, 2024

JackHaeg mentioned this issue May 16, 2024

VRMS: PM/Design Lead Meeting Agenda #1519

Open

JackHaeg mentioned this issue May 20, 2024

VRMS: ALL: Monday Meeting Agenda 📝 #1280

Open

JackHaeg closed this as completed May 20, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove old Meeting Agendas from Wiki #1636

Remove old Meeting Agendas from Wiki #1636

JackHaeg commented May 16, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

JackHaeg commented May 20, 2024

Remove old Meeting Agendas from Wiki #1636

Remove old Meeting Agendas from Wiki #1636

Comments

JackHaeg commented May 16, 2024 • edited Loading

Overview

Action Items

Resources/Instructions

JackHaeg commented May 20, 2024 • edited Loading

2022-07-11

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

JackHaeg commented May 20, 2024 • edited Loading

2022-07-14

Design Meeting Agenda

Before the meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

Action Items

JackHaeg commented May 20, 2024 • edited Loading

2022-07-18

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

JackHaeg commented May 20, 2024 • edited Loading

2022-07-21

Design Meeting Agenda

Before the meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

Action Items

JackHaeg commented May 20, 2024 • edited Loading

2022-07-25

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

JackHaeg commented May 20, 2024 • edited Loading

2022-07-28

Design Meeting Agenda

Before the meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

Action Items

JackHaeg commented May 20, 2024 • edited Loading

2022-08-01

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

What we actually discussed

Additional notes

Action Items

Upcoming Milestones

JackHaeg commented May 20, 2024 • edited Loading

2022-08-08

Team Meeting Agenda

Pre-work to prep for meeting

Who was there?

Things we plan to discuss

JackHaeg commented May 16, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading

JackHaeg commented May 20, 2024 •

edited

Loading