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

EA: Weekly PM Meeting Agenda #432

Open
brandohayes opened this issue Jan 21, 2022 · 99 comments
Open

EA: Weekly PM Meeting Agenda #432

brandohayes opened this issue Jan 21, 2022 · 99 comments
Labels
documentation Improvements or additions to documentation feature: agenda issue level I: request Smallest type of issue; Typically can be completed by one person priority: low role: product management size: 1pt can be done in 6 hours or less

Comments

@brandohayes
Copy link

brandohayes commented Jan 21, 2022

This issue tracks the running agenda for the Internal PM Weekly Meetings

Agenda Template:

## 2024-10-14 Meeting Agenda

### Meeting Facilitator (responsible for Prework):
### Meeting Note-taker:

### Prework to prep for meeting
- [ ] Create agenda
- [ ] https://github.com/hackforla/expunge-assist/issues/1543
- [ ] https://github.com/hackforla/expunge-assist/issues/1621

### PMs Roll Call
- [ ] Maria
- [ ] Rachel
- [ ] Rick
- [ ] Sarina (Runsheng)
- [ ] Vanessa

### Recurring items: Happens on the ________ meeting
 - [ ] review any issues that are in the new issue approval column on the [project board](https://github.com/orgs/hackforla/projects/77)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team
       - [ ] [Content](https://github.com/orgs/hackforla/projects/77/views/6)
       - [ ] [Design](https://github.com/orgs/hackforla/projects/77/views/2)
       - [ ] [Dev](https://github.com/orgs/hackforla/projects/77/views/4)
       - [ ] [Research](https://github.com/orgs/hackforla/projects/77/views/7)
       - [ ] [Product](https://github.com/orgs/hackforla/projects/77/views/8)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic and main labels](https://github.com/orgs/hackforla/projects/77/views/11) 
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ] #

### Friday CoP Meeting - who will be attending this week
- [ ] Maria
- [ ] Rachel
- [ ] Rick
- [ ] Runsheng
- [ ] Vanessa

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

### FYIs
-

### Notes from Meeting

### Task Items
@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Jan 24, 2022

[1/24/22] Agenda and Notes

Attendees

Val, Brandon, Tom

Recurring items:

New Meeting Items

FYI

Notes from Meeting

  • Development updates:
    • new developer officially - Jean; already familiar with the whole structure of HfLA; also Sydney is joining this week; 2 new devs
    • Daniel - working with design, getting some things flashed out
    • Daniel needs to meet with a content writer (Sam), to make last changes about text
  • Research updates:
    • hiring 2-3 researchers and 1 writer
    • writing research plan
  • Discussion:
    • direction of the research team, contextual interviews, marketing and MVP usability; need to start on outreach ASAP, usability study is the next logical step
    • EA 2.0. - where the project is going 6 months after the MVP is done?
    • Is the project even viable? Research across states
    • removing people who are no longer on the team/ add new people, Brandon - knows how to do it on Google Drive, can update roaster first (see task item Turn google doc into issues product-management#1)
    • UX Content Writer - Tom is PM for Sam; circle back with Bonnie to the idea of creating a community of practice for writers; Sam can join any meeting, the issue is the different time zone for her
    • Bridget availability, role, operation PM
    • Possibly bringing QA Tester on the team (Val's contact), mentorship is available, Brandon talked to Daniel; will join Thursday Zoom call

Task Items

  • update roaster - each PM for its own team, then we can update everything across
  • Brandon will follow up with the lead to get a timeframe on MVP (95%, conservative - month)
  • Brandon will create a recurring alert for PM meeting on Slack channel
  • Val will check with Sam about the team she wants to join (e.g., design, PM), Tom as her point of contact
  • Tom will reach out to Bridget on Slack about operation PM tasks/responsibilities

Items for next week's agenda

  • UX Content Writer update, PM, community of practice, which team should be attached to
  • Bridget's role

@jessicaherling
Copy link
Member

jessicaherling commented Jan 31, 2022

[1/31/22] Agenda and Notes

Prework

Roll Call

Recurring items:

New Meeting Items

  • Carry over to next week anything we didn't get covered this week
    • Make next weeks agenda
    • UX Content Writer update, PM, community of practice, which team should be attached to
  • Bridget's role
  • Slowness in the design team/ Bringing in a PM to supervise UI/ design team

FYI

Notes from Meeting

  • 2 new devs join (be a tester and be a dev for the team); need to be added to Github site
  • Progress - questions about Figma design (image has white background behind it - get same image without white background)

Task Items

Items for next week's agenda

@Andan-Eddy
Copy link
Member

Andan-Eddy commented Jan 31, 2022

[1/31/22] Agenda and Notes

Brandon updates
Two new Devs started last week -Igor and Carv (??)
they need access to Github- they are doing new member orientation

Brandon- ask to reach out to Tiernery about asset images

Jessica-

  1. bringing on new researchers (taking up time)
  2. Research coming up with research plans- several options to speed up implementing the research plan
  3. They discussed this with Bonnie
  4. They are meeting with new content writers
  5. Questions about continuing Tuesday meeting
  6. Jessica wants to get a barebones example of pre-MVP to give to research. Andan provides https://expungeassist.org/#/

Andan
mentions Design team has been slow on Figma updates- Daisy (lead designer) has been busy. Tonight Andan will ask what she has time to do with project. A new designer has show interest- if he comes to tonights meeting Andan will assess his experience.

bi-weekly Tuesdays UX/UI meeting will continue with flexibility.

Andan remind team about effort to find a PM to replace him working with UI/ design

@jessicaherling
Copy link
Member

jessicaherling commented Feb 7, 2022

[2/7/22] Agenda and Notes

Prework

Roll Call

Recurring items:

New Meeting Items

  • Can we move the PM meeting at 6 pm EST (3 pm Pacific) starting the following week 2/14? (Andan is leaving, Jess, Val, and Brandon all got full time jobs now)
  • The research team is preparing got usability testing, so we need to talk with design team about what features they want to test? What are the design needs for usability testing?
  • Can lead designer join our research meeting one of these weeks to talk with the team, explain the prototype, so the team can ask all the questions? Or we can join their meeting? Or just set up something up?
  • What type of mvp is it desktop or mobile? In what Format would it be? Functional app? Figma? All the details about that
  • Carry over to next week anything we didn't get covered this week
  • Make next weeks agenda

FYI

Notes from Meeting

  • Design: Utkarsh to take over a PM role; possibly Design - TBD; Tom in Dev right now - could switch or work on these roles together
  • Content Writing: Talking with Tom and others about how to organize it and whether to merge with Design, talked with Daisy too; seeing a need to collab more - questions about whether content needs its own PM; does Daisy have more time to meet with you?
  • Research - updates on research plan, new members, questions about usability

Task Items

Items for next week's agenda

@jessicaherling
Copy link
Member

jessicaherling commented Feb 14, 2022

[2/14/22] Agenda and Notes

Prework

Roll Call

Recurring items:

New Meeting Items

  • Sam to discuss MVP
  • Carry over to next week anything we didn't get covered this week
    • Make next weeks agenda

FYI

Notes from Meeting

  • Research update - usability testing; interview guide; desk research
  • Dev - new MVP date is 28th of February; discussed with Bonnie - Daniel making onboarding and off boarding procedures; Daniel met up with Sam about clear statements
  • Sam updates about MVP- development after MVP to configure the letter generator in the best way (how that works from coding side of things -> Sam structure content); design - questions about how to hand over work from content all the way over to development, haven't figured that out yet; writer coming on board
  • Sam - went and did a test run of website as of right now; form pieces that are done, spits out a letter that is unusable (example: will send screenshot later -> depending on what you put in the letter, then it will give you a sentence - dependent on check boxes you pick - there is a To whom it may concern - there is no this is who I am - grammatical things in background - some words are not what user puts in - might be the introduction just hasn't been coded yet)- question is to market the product to lots of different states and what not - from that point of view need something that is a simple template that is usable - doesn't have to be complex - first sentence starts off with and also (don't do that) - from otherwise of it - research - simplistic product the might not want to partner with it and wouldn't use it if it wasn't simplistic - how to handle the question and let it proceed; from content side do an audit and cosmetic change to change the words so it's structured properly: how to create best MVP possible? (marketing, product, partnering with organizations); Andan's initial thoughts - part of it is the level of emergency about the usability of the tool - we are the people who make these decisions - it's not going to be they do the MVP and we put the letters out - MVP is to get bugs out of software - once doing that we start presenting our project - test with other Hack for LA projects and have partners and be transparent with them that this will not be the thing that you are using - part of initial marketing - can't present outside of project - tell partners we are testing; Sam - noticed it and thought it was something to be aware of - looks quirky? Wait until development is done and we will do a beta test for us and we will notice that - does the problem show up in the figma too?

Task Items

  • Sam create an issue with screenshots and assign to Thomas, Andan. Thomas, Jessica, Val, and Brandon

Items for next week's agenda

@Andan-Eddy
Copy link
Member

Andan-Eddy commented Feb 21, 2022

[2/21/22] Agenda and Notes

Prework

Roll Call

Recurring items:

New Meeting Items

  • Sam to discuss MVP
  • Carry over to next week anything we didn't get covered this week
    • Make next weeks agenda

FYI

Notes from Meeting

  • We begin with how the paragraphs are broken up
  • Sam mention she will attend the Team (all-hands meeting) to discuss MVP problems with the dev team
  • Brandon discusses how to make the input more intuitive
  • Andan- asks how urgent this needs to be addressed
  • Sam- wants to make fixes before usability test
  • Tom suggests getting rid of grey text
  • Sam- says grey text needs to be made
  • Brandon asks if Sam can adjust grey text before MVP
  • Sam says she can change the scripts but getting done by 28th will be exteme.
  • Brandon- says he will push this to Dev tonight and we will go over this with dev in tomorrow nights meeting
  • Sam asks about her new model for the app when should go back to working on that- Andan Suggest do user testing -and have Sam continuing to work on new model - then blend her work and user feedback
  • Internal testing: we can do wire framing and google forms to get internal feedback - before we launch MVP
  • Plan google forms letter before usability testing - finish MVP- compare the google form letter to MVP in usability test
  • Brandon discusses replacing all zoom meetings

Task Items

Items for next week's agenda

@Andan-Eddy
Copy link
Member

[2/28/22] Agenda and Notes

Prework

Roll Call

Recurring items:

New Meeting Items

  • Introduce Mahmoud
  • Carry over to next week anything we didn't get covered this week
    • Make next weeks agenda

FYI

-Brandon reiterates MVP will be pushed back
-Brandon says Sam wants to just do internal testing- after MVP is finished (she couldn't find tools to do A/B testing)
-Daniel already has feedback from 2.22.2022 meeting
-Brandon will be leaving- says we will go through off boarding this Thursday
-Brandon say we NEED to find dev lead- Daniel needs to focus on documentation.
-Andan: Daisy is redoing minor revamp of landing page
-Val: research is creating a research plan- there is a researcher working on expunge assist across states/ Anna is taking over as Research lead. Val will continue with management duties.
-Brando

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Mar 21, 2022

[03/21/22] Agenda and Notes

Prework

Roll Call

Recurring items:

  • review any issues that are in the new issue approval column
  • Accountability and Support Check.
    • Review assignments for each PM

New Meeting Items

FYI

Notes from Meeting

  • New PM - introductions
    • Tom is giving permissions to Google Drive, adding to the roster, etc.
    • Tom explains about the labels on GitHub
    • Jamie will attend design/development meeting
  • Val is giving an update about the research team
    • internal usability study prep will be done by April 1
    • spoke with Sam, will change issues/labels, Val will support her to make changes
  • Tom - MVP is almost ready, minor changes are going on
  • Val - found an issue with research label, review accessibility of app #487, Tom will check with the development
  • Jamie - responsibilities of the PM, design team

Task Items

  • Tom : Make comment for Jamie's onboarding
  • Start putting reminder in the channel and agenda items
    • Timeline of MVP and work across the time
    • Creating GitHub Step by Step
  • Think about changing to once per month?

Items for next week's agenda

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Mar 28, 2022

[03/28/22] Agenda and Notes

Prework

Roll Call

Recurring items:

  • review any issues that are in the new issue approval column
  • Accountability and Support Check.
    • Review assignments for each PM

New Meeting Items

FYI

Notes from Meeting

  • Jamie - need to reach out to Daisy
  • Val - design system discussion, meeting with Daisy
  • Design Meeting - maybe Val can join
  • Going through Kanban board
  • Feature Label - clean up
  • Managing GitHun across the team - adding it to Wiki
  • Usability testing discussion

Task Items

  • Tom : Make comment for Jamie's onboarding
  • Start putting reminder in the channel and agenda items
    • Timeline of MVP and work across the time
    • Creating GitHub Step by Step
  • Think about changing to once per month?

Items for next week's agenda

@ExperimentsInHonesty
Copy link
Member

Please add this to this week's agenda and get it done during the all team meeting, or do separate ones in each meeting. Just be sure to name them to reflect the team name and if it's just the dev team, please say Expunge Assist - dev team.png

@jamiesiu
Copy link
Member

jamiesiu commented May 2, 2022

[05/2/22] Agenda and Notes

Prework

Roll Call

Recurring items:

  • review any issues that are in the new issue approval column
  • Accountability and Support Check.
    • Review assignments for each PM

New Meeting Items

FYI

Notes from Meeting

  • how to handle issues no longer valid - close with a note? delete?
  • Review of the board and backlog together
    • do we want to mark milestones now?
    • Add dependency label when issue has a dependency
    • MC 031 form - how is this used?
    • what needs review with Bonnie? e.g. forms saving progress "continue from before"
  • Internal testing results to be reviewed further by Research team. To talk further on how to present them to team
  • Design system
    • Val needs info on how to manage audit work / what tools
    • ticket needs to be broken out further so work can be split between people
  • Content Team
    • ticket review
    • Sam helping PM duties, Val shared lot of tips
    • Content would like PM support from all PM's, clarification and guidance

Task Items

  • Tom to review icebox issues with Daniel/dev team
  • Jamie to review Design tickets further - missing feature label, reach out with Daisy about older issues
  • Jamie - set up a meeting w/ Val and Serena on Design System (or push for Wed meeting)
  • Create Content label filter view for project board
  • Add clarification on the board columns process to top of columns

Items for next week's agenda

@mariaweissman
Copy link
Member

mariaweissman commented May 13, 2024

2024-05-13 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the new issue approval
  • Accountability and Support Check.
    • Review assignments for each Team
      • Dev
      • Research
      • Content
      • Design
      • Any Ready for Leads Labels?
      • Overall PM or Product Updates/Needs
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review any main issues
  • 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

FYIs

  • New zoom room possibly next week
  • Meeting with Bonnie is this Friday

Notes from Meeting

AUDIT

  • Only 1 missing label: dev issue, added size

NEW ISSUES WAITING FOR APPROVAL
Content

  • Drafts waiting for guidelines to be updated

Dev

Design & Research

  • Nothing on pre-backlog

PM

ASSIGNMENTS FOR EACH TEAM
Dev

  • Sydney updated some screen reader requests: major goal post met

Research

  • UXR glossary and slide deck share out - PM and Lead in discussion about share out
  • How to turn it into actionable tasks with Design and Content
  • Possibly use this as a case study for collab

Content

  • Guidelines: working on making progress

Design

  • Enhancing open sync
  • Working on onboarding documentation

PM

  • Meeting with Bonnie this Friday @ 1pm PT
  • Anyone who would like to join and be added to calendar, let @amejiamesinas know, who will be making agenda. @emmathrash asks to be added to agenda
  • This zoom meeting time -- there is onboarding start 6p on alternating Mondays and a Dev team that has 2 zoom rooms on hold. We may move zoom rooms!
  • Update team wiki? Update Team Wiki / Product Manager Wiki Pages #502. Close issue and create issues per team. Should we create process? Or assign everyone so that everyone is responsible and removes themselves and last assignee closes? Pros and cons of template issues are important, how to integrate into onboarding, easier to create new processes

STAKEHOLDER REVIEW

  • June 14th is June Org-PM meeting -- will stakeholder review be done by then
  • Will Bonnie review LG or the entire site?
  • Sydney thinks that each milestone should be full review, though we should provide her updates on what has changed
  • Bonnie will use June Org-PM meeting, she will go through entire site. Analicia will create issue: each team can provide comments
  • Privacy policy? To discuss with Bonnie this Friday, to add to agenda

ISSUES WITH DEPENDENCIES

  • Any issue with a dependency cannot be worked on until dependent issues are incomplete
  • Closed Research new visual style #1227 because dependency relationship was inverted
  • Possibly create "emergent request" as solution for issues that have task items that come up while working on issue -- let's ask Bonnie. @sydneywalcoff will confirm that this is phrase website team uses

SUMMARY FROM MARIA ON SURVEY FINDINGS
On bandwidth

Issues and GH

  • Any team member can create issue
  • When? Whenever the idea comes up (dev), is it worth it to think of this as parent v child category? Or if protocol is to identify notetaker, then can that person write up issues from meeting? Or split the two -- 1 notetaker and 1 issue maker per meeting
  • When closing the issue, you can add reasoning to comments. Low priority can be left at bottom of backlog
  • Who's responsible for ensuring that there are not duplicates? PMs with Leads

For next week's agenda:

  1. We should prioritize next milestone priorities at next meeting. Should be broad goals, not team specific nitty gritty, large goals
  2. Maria will continue on survey findings
  • And to have that convo in relationship to PM issues

Task Items

On deck for agenda writing:
Analicia on 5/20 @amejiamesinas
Vanessa on 5/27 @vanessaavviles

@sydneywalcoff sydneywalcoff added issue level I: request Smallest type of issue; Typically can be completed by one person and removed issue level: missing This issue is missing an issue level label labels May 15, 2024
@amejiamesinas
Copy link
Member

amejiamesinas commented May 20, 2024

2024-5-20 Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column
  • Accountability and Support Check.
  • 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

  • Note taker
  • Maria presentation follow up
  • Updates from Bonnie Meeting
  • Updates from EA Open Collab/Sync Meeting
  • Next week holiday, meeting?
  • Next meeting agenda and issue audit

FYIs

Notes from Meeting

MARIA'S FINDINGS CONT'D

  • Issue management: note taker versus issue maker, not wanting to create double issues -- responsibility of PMs
  • Big picture questions:
  1. What is the product vision?
  2. What are our priorities? How do we ensure that they're met?
  3. How do we ensure all public-facing info reflects proper levels of expertise? That is, how to put a process in place that research is reflected in website
  4. Team charter - typical in agile, what are goals, to get everyone's buy-in, that is revised each time a new person comes in
  • We can shape product vision based on our sense of PM-Org meeting? Yes
  • MVP is not landing page but LG
  • Design and user is probably 2.0

Do we know who our user is?

  • For Dev (Sydney) the user = petitioner. Does this person already have legal counsel? Assumes no. But should push for legal counsel?
  • IUT findings: unclear who user is
  • It would be easier to have a community partner so that the product is co-built
  • Can we think of it as a B2B tool? Building an app to "sell" it and then to change it, doesn't make sense. Should instead the approach should be to solve a problem that a legal clinic needs to solve.
  • For UXR (Sylvia) thinks that the pitch should be to community partner
  • For future meetings: to pick up questions in Maria's findings for 10 minute every meeting?

STAKEHOLDER 1.0

  • We should assume that Bonnie is doing a full review

PRIORITIES FOR STAKEHOLDER 2.0

  • If user is who we decide, then how to name priorities
  • But also we need Bonnie's feedback
  • What are other things on site that might be helpful

UPDATES FROM BONNIE MEETING

Task Items

On deck for agenda writing:
Vanessa on 5/27 @vanessaavviles
Maria on 6/3 @mariaweissman

Pre-work: review https://accessprojectca.org/rsn/dec/ letter generator

@vanessaavviles
Copy link
Member

vanessaavviles commented May 27, 2024

[2024-06-03] Meeting Agenda

(note: meeting originally scheduled for 2024-05-27, rescheduled for 2024-06-03)

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • finish adding labels to the issue that are still missing them (see audit links above) (role & feature missing Team Updates for Bonnie Review #1410)
  • 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

FYIs

Notes from Meeting

Note taker vs issue maker

  • Note taker will be issue maker
  • Problem with the lack of representation (for ex, no Design team today) if there are problems with how issues are drafted but that team is not here?

Team updates for Bonnie

  • Team Updates for Bonnie Review #1410
  • We told Bonnie that we'd provide her with an agenda with items
  • Important for her to go through entire product
  • To streamline this process, can each team indicate what they worked on, so before you go to LG, review the updates on About Us, FAQs, etc. how to provide feedback, etc
  • How do we build up instruction issues? We can continue to discuss next week
  • Let's build this issue and assign rather than add label (ready for dev or ready for x): once you update your team's update, then check off box, and @amejiamesinas who will create items for Bonnie meeting will close
  • Is there a credits page? Sydney says yes but a few days behind
  • Maria Slacked Design to request updates

Team Rosters Updated

  • Now automated!
  • And doesn't automatically assign, but we can have someone check the roster 1x per month or something
  • But not always included on project board

The Access Project's letter generator

  • Sydney: interesting what kinds of questions they asked, like are you in contact with a lawyer? Debated amongst EA, but could solve a lot of problems, they don't have a letter generator but a typeform, worth understanding privacy questions
  • Analicia: the letter is Step 2 which we don't have; the samples provide examples and legitimacy
  • Sylvia: Design did a mockup of the expungement process, but on internal docs and not public facing. We can use this to supplement redesign
  • Maria: what are some ways to make EA stronger based on our understanding of TAPs tool
  • Analicia: agenda item for post-Bonnie review, with Bonnie's feedback, how to start milestone and goals, TAPs tool can be part of the conversation > what then are our visions and goals for the next milestone

Bonnie Review

  • Hack for LA and Code for America issues not implemented > currently in Design's docket? or is it with Dev? @sydneywalcoff will confirm with Design; Design's bandwidth limited, so can be pushed to Dev
  • Privacy policy -- still waiting for Bonnie's feedback

Missing Labels Bot?

  • Do we want a missing labels bot? For PMs
  • Might as well since we will visit it during this meeting
  • For those leaving off labels intentionally, then fine, but for those who forget, then the bot will help build up the practice of adding labels

GitHub Migration

  • Classic projects are associated with repo
  • New projects are associated with Hack for LA and tied to repo
  • Some teams are using the new project board, but it's not clear now if it's a new board that is added or integrated

Accountability and Support Check
Research

  • Working on Wiki board and onboarding process
  • Currently a team of 3
  • Sara is working on usability in collab with Design
  • Analicia is going to leave Expunge Assist but will finish out June; input for new PM or something else for transition; let's devote time during next meeting
  • Analicia added One Sheet to Product Management repository; can we close those 2 issues? @sylvia-nam and @amejiamesinas will discuss

Dev

  • New 404 page fine

Content

  • Finally starting guidelines, one issue assigned to Claudia, exciting that it is handled collaboratively
  • Focusing on documentation and resources with emphasis to GH
  • Content issue template so that's beginner friendly
  • Can there be a handoff process that is part of the template to streamline processes?
  • Sydney: you can add handoff template as an how to to move ticket forward
  • Since Content does the handoff (not usually the other way), but may be a case where Research does a handoff to Content

June All Teams

  • To discuss master docs? Probably to discuss here first, but we can ask people to think through the terms (Information Architecture, SoT, etc), ask the teams to figure out how and if they define it, etc.
  • Focus on updates? Or handoffs? But where do different teams fit and in the cycle of team collab

Survey from Maria

  • Collab framework discussion -- no ownership ambiguity, to improve product. Ideal is one thing but practically what is next? But how to be present when these conversations are happening
  • Open Sync -- what is the point of it? Seems to cause more confusion. Collaboration can still happen async. PM conversations should not happen in that space (since it wasn't being cycled back)
  • Content teams can create guidelines about how to collab: GitHub is for project management, meeting is for x, and Slack for y
  • Dev meetings restructured: now traditional tech stand-up with avg meeting length in 10 mins, with increase in productivity

Task Items

Agenda Writing:
Vanessa out for June

June 10 - @amejiamesinas
June 17 - @mariaweissman

@amejiamesinas
Copy link
Member

amejiamesinas commented Jun 10, 2024

[2024-06-10] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • 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

  • Friday June 14 Bonnie Review
  • PM Meeting/GitHub Changes GitHub Project Board Migration #1439
  • Follow up from all teams (review/create any additional issues)
  • PM Transition
  • Anything else?
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

  • Design team is adding updates to issues Team Updates for Bonnie Review #1410 after the meeting and will flag @amejiamesinas once done
  • New Issues: Dev created issues that need Design feedback. Sydney will mark the issues "ready for design lead" so that Anita can review. Anita also brought up revisiting the illustrations and requested UXR support. Sylvia mentioned that she would talk to Sara and she could create the issue for that based on the best way we should approach the colors.
  • GitHub project migration: Next PM meeting she will migrate our Project board to the new board. Team impact? we will no longer have cards like the "Start Here" cards but Bonnie shared there is a way to transfer that info over
  • Bonnie meeting is at 1pm but we do not all need to be there for this weeks meeting because Bonnie will demoing our website
  • All Team Issue Creation: In regards to Maria's survey- each team that would come up with a role's and responsibility doc for their team, Maria would work on a team charter, and we would also identify priorities. Question lays on whether we want to do these all together or separately. An issue needs to be made for this which @emmathrash shared she would be making. @amejiamesinas will check in with her on this. We brought up on how these would fit in with stakeholder 2.0 and we agreed that operational tasks can be done in tandem with Stakeholder 2.0 issues.
  • PM Transition: Analicia will be transitioning off the project and we are recruiting a new PM for UXR. Discussion on who will be a UXR PM in the meantime which would include, onboarding/offboarding UXR members. Sylvia will be out of town at the end of June . Sydney mentioned that she can help but would be great for all leads and PMs to learn onboarding. We talked about permission access to GitHub, which Sydney is going to explore whether we can create a group of people who can have permission to give people write access without changing the repo. If we ever need help, we can also ask Sydney to help us add people to GitHub
  • Since Bonnie is reviewing our website, Dev will have a code freeze which means that changes are not published to the live website until after Bonnie's review.
  • Pre-work: check in on Bonnie's recording she does on the live website so we can talk about it next Monday. It is optional to attend a meeting with Bonnie live but Analicia will write out instructions for Bonnie. We will also discuss next milestone during next meeting as well
  • Analicia has ideas for Issues templates: create an issue on including a checklist on templates
  • Each team can start working on their roles and responsibilities but we can also include the responsibilities of a Lead vs member
  • Would be good for our Contributing page to have our roles and responsibilities and code of conduct

@mariaweissman
Copy link
Member

mariaweissman commented Jun 17, 2024

[2024-06-17] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • 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

FYIs

Notes from Meeting

#1439 Project board has been transitioned. Old board has been deleted. A few lingering items

  • New version does not have project board cards—so we needed to paste all the cards into comments of 1439
  • Links throughout the wiki need to be updated
  • Letting the team know the team as a whole now: Slack announcement and in team meetings: Direct questions to slack comment
    -  Determining where to put the cards— audit of the wiki to see what needs to be transferred: Create an issue, and assign one person—Maria will continue to work on this, will also create issues for any broken links

#1445

  • Maria working on this
    o  Need to add open role for Research PM replacement
    o  Bonnie is hosting one more onboarding before July

#1442

  • Interpreting Bonnie's feedback: M is 100 % in the mile stone, S is argument either way, C is low priority
  • Sylvia will take lead on meeting with Bonnie: https://docs.google.com/presentation/d/1WzvnMc6cTzoxKBo3DLqd9-ENex3mXjQZBMHSUXM7yxU/edit#slide=id.g20a56e2c0ec_0_57
  • Maria will take lead on sorting then PM’s will work together, and Sydney will work with Maria to create issues
    o   Next week: 20 min Bonnie, 20 min over all product vision, 20 addition items
    §  Analicia will create product vision issue
    o   Analicia will create issue to offboard herself & recording
    o   AMM will make agenda for next week, Sylvia will be out

@amejiamesinas
Copy link
Member

amejiamesinas commented Jun 24, 2024

[2024-06-24] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • 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

FYIs

  • AMM last day is June 30, 20204.

Notes from Meeting

@emmathrash
Copy link
Member

[2024-07-08] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • 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

FYIs

Notes from Meeting

@emmathrash
Copy link
Member

emmathrash commented Jul 29, 2024

[2024-07-29] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • [Research]
      • [Dev]
      • [Content]
      • [Design]
  • 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

FYIs

Notes from Meeting

HOUSEKEEPING
Weekly label check

  • A few missing size labels: a couple of dev issues, 1 for research
  • Addressed

Automated label check

  • With new board, automation doesn't work
  • Will have to do it manually

BONNIE'S COMMENTS

  • Postpone addressing comments to September - PM/Org
  • And make case for product
  • Emma: Bonnie gave a lot of feedback that is granular, some concerns addressing those comments before product vision and target user conversation with Bonnie
  • Sylvia: agreed, but we must address Bonnie's MUST comments before having that conversation
  • Sydney: should be iterative, if broken things fix that first and quickly, and then have bigger picture questions around standards and guidelines, will save us grace if we bring fixes faster

ALL TEAMS MEETING

  • Sydney will facilitate August All Teams
  • Primary agenda: should it be postponed since we don't know exactly how we will tackle Bonnie's comments

ON COLLABORATION

  • Maria is working on charter
  • Potential PM (product or project) manager

Next week 8/5 - facilitator @vanessaavviles and notetaker @emmathrash

@vanessaavviles
Copy link
Member

[2024-08-05] Meeting Agenda

Prework to prep for meeting

Recurring items:

  • review any issues that are in the [new issue approval column]
  • Accountability and Support Check.
    • Review assignments for each Team member
      • Content
      • Research
      • Design
      • Dev
  • 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
    - [ ] # Christina needs to offboarded

New Items

FYIs

Notes from Meeting

Task Items

@vanessaavviles
Copy link
Member

vanessaavviles commented Aug 12, 2024

[2024-08-12] Meeting Agenda

Prework to prep for meeting

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
      • Content
      • Design
      • Dev
      • Research
  • 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

FYIs

Notes from Meeting

  • We still need to figure out the feature system for the weekly label check as some newer features have not been added to the exclusion list and are being flagged as missing. Emma will try to watch the video so we can go over it together next week and will timestamp it to make it easier to find next time (13:25 / 18:20 / 27:47)
  • We also need to update the "icebox issue w no dependency link" as it has broken since the project board update.
  • On discussing meeting times - the priority is to have at least one member per team present (looks like that's Mondays at 4pm PST). However, we're waiting a couple more weeks to make the change in case a new research PM joins.
  • Another note for future discussion is how to include PMs and leads who are unable to attend meetings and how could that fit into the General Collaboration Framework discussion?
  • A reminder that the next Bonnie meeting is September 6th
  • Content has a plan to push through as many fixes as possible, issues to come.
  • For all Bonnie feedback that is not immediately being implemented, each team to add a note on the excel document as to why.
  • Sydney will look at dev options for the "copy to clipboard" function and shortening the time between the copy and when it expires.
  • How to balance safety concerns and not overloading the user with too many instructions? Extra pop-up? Catch-all phrasing? Fewer security risk options?
  • Next to facilitate: @mariaweissman (Emma on deck)
  • Next notetaker @vanessaavviles

Task Items

@mariaweissman
Copy link
Member

mariaweissman commented Aug 19, 2024

[2024-08-19] Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the [new issue approval column] (https://github.com/orgs/hackforla/projects/77/views/1?filterQuery=new+issues)
  • 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

Make a video for future PM's on weekly label check.
LG Input: Revise word count on LG, maybe add a draft label, something to think about. Revisit in 2-3 weeks.
FAQ link issue will be put in the backlog
Maria's team charter #1404 will be ready next week, in the meantime will reach out to the pm's and leads to eventually show and go over with their individual teams.
Check in with sylvia about meeting time.
#1477 will need design collab
#1481 design collab with research over the illustrations, issue will be done after colors are finished.
#1470 update team roster for individual teams
Ellyna working on the icons issue
Dev lost a developer
Each team to prepare with their issues for bonnie's meeting in September. If can't be done by the time we have meeting with bonnie than explain on spreadsheet.
Next week facilitator @emmathrash and next note taker @mariaweissman

Task Items

@emmathrash
Copy link
Member

emmathrash commented Aug 26, 2024

[2024-08-26] Meeting Agenda

Prework to prep for meeting

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
      • Content
      • Design
      • Dev
      • Research
  • 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

FYIs

Notes from Meeting

Setting expectations
Potential Research PM being onboarded
Reviewing Team Charter
Dedicate meeting time in future weeks to discussing more big picture questions in terms of FAQs
Connecting Team Charter with Roles & Responsibilities

Bonnie meeting next week:

Purpose & Goals:
Reviewing Priority List: https://docs.google.com/spreadsheets/d/1uajit1EJKIKGd6wqQz6XC-GTYTycDo1Ea-fzAiBxCqs/edit?usp=sharing

Asking Bonnie about process of removing Admins from Github

Add Privacy Policy to Agenda

Reviewing #1442

FAQs might need to be deleted, so is it worthwhile spending time on editing it?

Sydney facilitating Org Meeting with Bonnie

Sept 6 all teams - review team charter

Next PMs/ Leads Meeting: Monday Sept 9.
Vanessa writing agenda
Emma taking notes

Task Items

@vanessaavviles
Copy link
Member

vanessaavviles commented Sep 9, 2024

[2024-09-09] Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [x] #

New Items

FYIs

Notes from Meeting

  • We replaced all the missing labels on the weekly label check issue
  • Anything hanging out in the pre-approval column should either be approved or have the draft label
  • Future topic for discussion: what are our processes when we have an issue that we all share as a product management task?
    E.g. We need to determine our own ideas of roles and responsibilities (link issue) - Sydney to come up with 2 options of how to design this issue to make it it’s most efficient version for the team.
  • Team Charter Updates: most teams still reviewing and will discuss, research went through it as a team and left comments with thoughts and suggestions
  • Design updates:
  • Content Updates: Chose AP guidelines as a base for our content guidelines, will be working through it together during upcoming meetings.
  • Dev Updates: Technology migration coming up for Dev in the next couple weeks, moving to use a new program, not going to affect other teams.
  • Research updates: Sara completed research for color system and now looking at illustrations and best practices around how to use them, how to use them with accessibility in mind, hopefully will present at an all teams and create more concrete steps with design team.
  • Future topic for discussion - how to prioritize with multiple milestones
  • Successful org meeting but Bonnie would like better documentation
  • General collaboration framework: perhaps start with hand-off processes and how each team would prefer to receive information and designs etc.

Task Items

@mariaweissman
Copy link
Member

mariaweissman commented Sep 16, 2024

2024-09-16 Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

New Items

  • next week, emma writing agenda & maria taking notes
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Issue with no dependency link now active and working
Content: no new update
Design: no new update
Dev: New dev meeting now changed to Monday's. Sydney working on hackerone program.
Research: Onboarding new research PM on Thursday. Establish on who is the user? Unclear on collab.
Product: Internal teams to take specific sections from team charter and work on them.
Next bonnie meeting on October 4 and all team's meeting that same day too.
Next facilitator @emmathrash and Notes taken by @mariaweissman

Task Items

PM's to help onboard new research PM Rachel.

@mariaweissman
Copy link
Member

mariaweissman commented Sep 23, 2024

2024-09-23 Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [x] #

New Items

  • Content Team Changes
  • Anita: Hi PMs and Leads, since I cant make it to the PM and Lead meetings, I wanted to put an issue on our radar to discuss async. We created an issue to address Bonnie's suggestion on approaching how folks can Contact Us for any questions/concerns. Previously we had a "Contact Us" link that would open the user's mail app and display a placeholder email in our footer and in the FAQ page. Since it was just a placeholder email, PMs reached out to Bonnie on what email we could use and she shared that she would prefer that we create a Contact Form and develop a process on how we would check emails and respond. We created this issue: Create a Contact Form  #1209 to address that and wanted to revisit this to determine if this is how we would like to move forward? At the moment, there is no way for users to reach out since we removed the display of the placeholder email and "Contact Us" link so it would be vital to have a method that folks can reach out to EA/HFLA before we launch this to partners.

Meeting Notes: Step 1: Maria Create issue + Build out Weekly Email Check ; Step 2: Decide on Contact Form

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

FYIs

Notes from Meeting

  • Vanessa writing agendas for PM/Leads meeting, All Teams & Org Meeting next week
  • Bonnie meeting October 4.
  • All Teams meeting October 4.
  • Emma will be leaving the project effective immediately.
  • Sam will also be transitioning off the project within 2 months.
  • How will content change affect our leadership?
  • With the new changes, updating the charter will be effective as we will want to implement on the charter that volunteers can at least contribute 6 hours to the project and pinpoint roles and responsibilities.
  • The new research PM will be joining us next week could not meet this week because she is out of town.
  • With Anita comment on Create a Contact Form  #1209 product isn't live yet. Up to design to determine what the next step is.
  • Maria creating new issue for PM's to go over the email weekly as a new task for PM's.
  • Sydney with being okay in joining design meeting when it comes to input fields opinion.

Task Items

@vanessaavviles
Copy link
Member

vanessaavviles commented Sep 30, 2024

[2024-09-30] Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] Onboarding Rachel @raeraeicky - add to VRMS
    - [ ] Offboarding Emma

New Items

FYIs

Notes from Meeting

Maria can fill in as liaison PM for Content while they’re in the midst of offboarding Emma and eventually Sam (Co-leads/ PMs). Can attend next week’s Thursday Content meeting

EA is currently looking for two new designers as well as

Bonnie meeting this Friday at 1 PM
Major team news: Content leadership offboarding
Maria attending 1 PM, Sydney, Rachel, Vanessa, Sylvia

Vanessa will go this Friday to the Community of Practice

Expectations on Team Charter: Offboarding and Onboarding
A month is idea

#1212 was closed but the correct email address wasn’t put on there
Sydney will create a new development issue to update on the website; directly to development

Design will design a contact us page

Will ask about adding Rachel to VRMS in community of practice friday meeting https://docs.google.com/presentation/d/1bv9QH-d5qKtFCaecgCvsv608IoeLIpHfW7cEEqijHyE/edit#slide=id.g20628192ba7_0_93

All Teams - Design will present colors

Content #1503 moved to in progress

#1564 waiting on Anita to chime in - Vanessa will bring to her attention this week

Dev: let them know if there’s anything wonky on the website

Thinking about what an appropriate handoff could look like for the future Content PMs/ Leads

Smoother process in place

Coming up with different ideas for ways to organize EA

Task Items

@vanessaavviles to make agenda for PM/ ORG meeting this friday.
@vanessaavviles to make agenda for All Teams meeting on friday.

@mariaweissman
Copy link
Member

mariaweissman commented Oct 7, 2024

[2024-10-07] Meeting Agenda

Prework to prep for meeting

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] #

New Items

  • Maria reviewing agenda and label check with Rachel
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

@mariaweissman mariaweissman changed the title EA: Internal PM + Leads Meeting Agenda EA: Weekly PM Meeting Agenda Oct 11, 2024
@mariaweissman
Copy link
Member

Update: per our last Org Meeting with Bonnie #379 EA will be changing meeting structure to having a weekly ALL TEAM meeting on Fridays at 10:30 AM, with the first week of the month being just for Leads/PMs to plan.

The Monday PM/Leads sync will now be just a meeting for PMs moving forward (Leads always welcome to attend though!)

@mariaweissman
Copy link
Member

mariaweissman commented Oct 11, 2024

2024-10-14 Meeting Agenda

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Srishti
  • Vanessa

Recurring items:

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] #

New Items

FYIs

Notes from Meeting

  • Working through the backlog, working through Bonnie feedback
  • Speaking with Org about Project direction - user

Task Items

@raeraeicky
Copy link
Member

raeraeicky commented Oct 14, 2024

2024-10-21 Meeting Agenda

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Srishti
  • Vanessa

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] #

New Items

  • Slack channel updates from CoP
  • Review All Teams format prior to first meeting
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

  • All Teams: first iteration this Friday
    • Similar to a stand up, have everyone discuss what they're doing right now, any open questions
    • Look back to Bonnie's slide deck from last team meeting with her
  • Roadmap / Product vision: discuss with Bonnie at 11/1 meeting with her
  • Issue with dev: not enough to do besides test cases, lower morale
  • Discussed issue flow in GitHub and labeling process

Task Items

  • Rachel to make a Google doc to prep for meeting with Bonnie and share with PMs
  • Rick to make suggestions for process flow updates

@mariaweissman
Copy link
Member

mariaweissman commented Oct 28, 2024

2024-10-28 Meeting Agenda

Meeting Facilitator (responsible for prework): Maria

Meeting Note-taker:

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Runsheng (Welcome!)
  • Vanessa

Recurring items:

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] Oboarding Runsheng
    - [ ] Offboarding Srishti; Maria can do but awaiting confirmation from content lead

New Items

  • Update from PM CoP re icebox vs prioritized backlog: ICEBOX is for issues that have a specific dependency preventing them from being worked on. Items that are low-priority/ not being worked on at the moment should go in prioritized backlog along with the relevant milestone that shows where it belongs. Org is still working on which milestones each project needs to have, TBA.
  • Team Charter PM section blurb set?
  • Prepping for Friday Planning Meeting (Leads/ PMs)
  • Prepping for Friday Org Meeting (PMs & Bonnie)
  • Review unassigned Product Management role issues
  • From Bonnie: The following issues are in the repo and are assigned to people who are marked as inactive on the team roster
    Onboard & Offboard: UX Content Writer #819 (assigned to Emma Thrash), its in the start here column
    Update Team Wiki / Product Manager Wiki Pages #502 (assigned to Jamie Siu) its in the done column, so perhaps it just needs to be closed.
  • Returning to weekly routine of: PM A creates agenda and does prework to prep for meeting. PM B takes notes. The following week, PM B creates agenda and does prework to prep for meeting. PM C takes notes. etc
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

  • New PM Sarina joining the team: potential new content PM?
  • Discussed what the "draft" label means: issue is a work in process and not ready for review
  • Bonnie is working on mandatory milestones that should be applied across all projects
  • Discussed plan to gather lead feedback and how to propose new issue workflow
  • Aligned on goals on meeting with Bonnie: get product vision and high level goals
  • Vanessa will offboard at the end of the year

Task Items

  • add note asking for Bonnie's approval/help implementing an AI summarizer for meetings
  • [RP] make a planning meeting using template, focus on having leads discuss their current workflow and any blockers
  • [RP] add to planning meeting agenda a section about plan for PM/ORG meeting (Bonnie meeting)
  • [VA] clarify with Sydney who currently has offboarding privileges in GitHub and what was the reason for any limits on permissions (i.e. why don't PMs have offboarding permissions)
  • [RI] finalize agenda for PM/ORG meeting

@rcpeng34
Copy link
Member

rcpeng34 commented Oct 29, 2024

2024-11-4 Meeting Agenda

Meeting Facilitator (responsible for Prework):

Meeting Note-taker: Sarina (will facilitate next week)

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Runsheng
  • Vanessa

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] #

New Items

  • review Org Meeting with Bonnie
  • Milestones
  • Information Architecture ownership
  • Momentum after break
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

AI notes - Fathom not working - check with other project teams to see what's worked for them

Add issues have not been added to the project's broad
Weekly email check done
Check the project board:

  1. Make sure the right labels are on the right issues
  2. Draft labels
    Review last week’s meeting with the Bonnie, the added milestone
    Discuss about what are the milestones and need further clarification
    Discuss the momentum after the break
    Information architecture

Task Items

@vanessaavviles
Copy link
Member

vanessaavviles commented Nov 12, 2024

2024-11-11 Meeting Agenda

Meeting Facilitator (responsible for Prework):

Meeting Note-taker:

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Runsheng
  • Vanessa

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] #

New Items

  • GitHub: template per team (from Sam at All Team)
  • GitHub: issue level and ticket scope
  • GitHub: Epic assignee
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Notes:

  • AI Note taker still not working (Fathom) - ask Lola at CoP meeting
  • Sarina: will create agenda for next week
  • Rick: weekly rotation for Friday PM CoP Meetings; updating the template
  • Rachel: updates including possibility of including Fragments
  • Content updates from Friday - PM role filled and determining 2025 Lead
  • Everything "In Progress" needs an assignee: Maria will look through & assign self and also compare to Bonnie's list
  • Determining how to make issues smaller, clearer, and easier to move
  • Milestones: utilizing the ones from Org & getting 2.0 done
  • PMs per each team will update their team's milestones to either stakeholder review (IF part of Bonnie's list), or move to another milestone

Task Items

@mariaweissman
Copy link
Member

mariaweissman commented Nov 18, 2024

2024-11-18 Meeting Agenda

Prework to prep for meeting

PMs Roll Call

  • Maria
  • Rachel
  • Rick
  • Sarina (Runsheng)
  • Vanessa

Recurring items: Happens on the ________ meeting

  • review any issues that are in the new issue approval column on the project board
  • Accountability and Support Check.
  • finish adding labels to the issue that are still missing them (see audit links above)
  • review issues with epic and main labels
  • Review to see if there are any members to Onboard or Offboard
    - [ ] # Offboard Srishti (Content)
    - [ ] # Offboard Amanda (Design)

Friday CoP Meeting - who will be attending this week

  • Maria
  • Rachel
  • Rick
  • Runsheng
  • Vanessa

New Items

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

FYIs

  • Next PM Meeting January 6

Notes from Meeting

  • Last meeting for the year! next one will be the first Monday in January

  • Milestones applied for all teams except Product
    - Reviewed as a group to complete, moved things out of Stakeholder 2.0 that aren't on Bonnie's list

  • Team Updates

    • Content
    • Design: trying to recruit new PM and Brand Designer; work on About Us and Contact form
    • Dev: Oops +. About Us in progress, waiting for design external link styles #1507 from Design so Dev can get started on some of the Stakeholder 2.0 issues
    • Research: working with Content on About Us, updates for prop 36, updating wiki
  • Rachel and Rick out on Friday

  • Fathom AI Notes + Recording

Task Items

  • Vanessa to update roster for November
  • Maria + Sarina to confirm offboarding for Srishti
  • Vanessa to offboard Amanda + set up recruiting for new branding volunteer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation feature: agenda issue level I: request Smallest type of issue; Typically can be completed by one person priority: low role: product management size: 1pt can be done in 6 hours or less
Projects
Status: Start Here
Development

No branches or pull requests