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: Dev / Design Sync Meeting Agenda #717

Closed
jamiesiu opened this issue Oct 17, 2022 · 18 comments
Closed

EA: Dev / Design Sync Meeting Agenda #717

jamiesiu opened this issue Oct 17, 2022 · 18 comments
Assignees
Labels
documentation Improvements or additions to documentation feature: agenda priority: low question Further information is requested role: design anything related to design role: development anything related to code role: product management size: 1pt can be done in 6 hours or less

Comments

@jamiesiu
Copy link
Member

jamiesiu commented Oct 17, 2022

This issue tracks the running agenda for our weekly Dev / Design / Product Sync

# [Date] Agenda and Notes
### Attendees
- 

### Recurring items: 
- [ ] Accountability and Support Check 
- [ ] Blockers Support / Help Needed 
- [ ] Progress Share / Feedback Requests 

### New Meeting Items 
- [ ] 
- [ ] 
- [ ] 

### FYI / Announcements
- [ ] 

### Notes from Meeting
- [ ] 
- [ ] 
- [ ] 

### Action Follow-up
- [ ] Review previous action items
- [ ] @ 
- [ ] @ 

### Items for next weeks agenda
- [ ] 
- [ ] Carry over to next week anything we didn't get covered this week
   - [ ] Make next weeks agenda
@jamiesiu jamiesiu added documentation Improvements or additions to documentation question Further information is requested role: development anything related to code role: design anything related to design priority: low role: product management feature: agenda labels Oct 17, 2022
@jamiesiu jamiesiu added this to the Team Workflow milestone Oct 17, 2022
@jamiesiu
Copy link
Member Author

jamiesiu commented Oct 17, 2022

[2022.10.17] Dev / Design Meeting Agenda

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Content Question on Something Else Category Flow
  • Questions about IUT2 Requests from Design/Content
  • [ ]

FYI / Announcements

Notes from Meeting

  • Content Question on Something Else Category Flow
    • could we do a slack chain to help ease communication? Sam can't attend this meeting and would like to verify this is doable
  • Inspect - where is the break point for Mobile
  • Questions about IUT2 Requests from Design/Content
    • none atm
  • Parenting Flow
    • Serena DM'd Daniel/Sydney - Dev confirmed the simpler version with grammar changing for child vs children in auto-generated text is possible.
    • Will finalize design and have ready by EOW
  • Public-Facing Wiki
    • Tom working on finding a no-dev solution and should be able to present by next Team Planning meeting
  • Sheron joined the team as a PM for Research
  • All-Team Meeting Questions
    • anything we need to prepare? general recap of what we're working on for each team. Meant more as an open forum for team to ask questions and get to know one another. Product has considered a more formal agenda, yet is mindful of encouraging more of the team to attend
    • does open-ended format work? David likes it as our other meetings are a lot more structured/objective and it's a good change of pace

Action Follow-up

  • Content to start up a Slack thread in main team channel regarding Something Else Flow

Items for next weeks agenda

  • [ ]

@jamiesiu
Copy link
Member Author

jamiesiu commented Oct 24, 2022

[2022.10.24] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Check-in on IUT2 changes implementation - prioritization, timing, feedback
  • Questions about the FAQ page: moving & breaking up text boxes
  • [ ]

FYI / Announcements

  • Team Planning next week
  • Jamie will be out Friday 10/28

Notes from Meeting

  • Priorities / Timing for IUT2 Implementation
    • Design shared priorities for implementation - dynamic items for flows most important
    • UXR timing and our timing. UXR has been preparing for IUT2 for few weeks and should likely be ready soon in few weeks (faster due to previous IUT1 experience, but may also need time to recruiter test users). They did not have explicit timing. Dev hoping to avoid us having to prototype things
    • Judging from the last mvp changes, dev team would need a month to implement all the changes. Dev has enough from Design/Content to be able to implement at this point and is now about exectuion
    • Daniel will start a job in a week (congrats Daniel!). His bandwidth will likely be low, which also affects timing
    • Sydney could help with Advice Page ticket for now
    • Issues on Flows more daunting in terms of complexity for Dev
    • This week Daniel will try to chunk out more of the top stuff
    • Draft GH issues are nearly done. Anita verifying with Content on the autogenerated text pieces to make sure copy is good for design handoff
  • Questions about the FAQ page: moving & breaking up text boxes (Design chat topic)
    • David auto-layout suggestions share. What needs to be a certain distance from each other and how can it be applied to all these?
    • Desktop version - issue is that it is 1 frame. Auto-layout can't understand how to space 1 frame. what frames need to be organized and how do i make those frame units spaced evenly?
    • Need to make sure each is the same text style, sizing. Some dead space needs to be removed.
    • Approach 8px requirement first - in order to make question/answer a frame. Once all ready, then select all these frames and create auto-layout for 24px spacing
    • Phu hoping to finish up by next week
  • [ ]

Action Follow-up

  • @ Jamie to follow up with UXR Leads/Sheron about month timing estimate for IUT2 - when would they be ready and when we might be ready. Do we push back testing? Also, discuss at team planning
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

[2022.11.07] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

  • Jamie is out of town 11/7-11/11

Notes from Meeting

  • [ ]

  • [ ]

  • [ ]

Action Follow-up

  • @
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Nov 14, 2022

[2022.11.14] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • IUT2 feedback for implementation so far
  • [ ]
  • [ ]

FYI / Announcements

Notes from Meeting

  • Lexie PM with Fintech company for 1 year - looking to join project. Background in Data analytics. Loves Product management
    • Davide software fullstack dev with Intuit / primarily frontend joined last week
    • Arpita software dev based out of Toronto
  • All Designs have been officially handed off to Dev. Design saw push recently pushed out. Design created issues to capture bugs and list of minor things Gather functionality issues on website and create a list for Dev #739
    • When category selected like Parenting Flow, next page goes to Unemployment flow before the choice user intended to select. Confusion over the intention of the flow. Unemployment should only appear when selected. Sydney can take a review of this. Something else to capture what's remaining. Can someone check nothing and proceed with the form?
    • Last page of letter generator missing return button. Progress bar not fully populated
  • [ ] Daniel to reserve some time to work on pushes for IUT2. Busy lately

  • How to go about Dev / Design handoff
    • Jamie to check on Figma permissions
    • Davide had questions about scale of pictures. Dimensional differences. # of pixels look bigger than browser itself. Use design system we have with breakpoints and material UI spacing. Daniel to double-check with PR
  • Davide needs permissions for GH write and also Drive doc permissions
    • Tom and Jamie to help

Action Follow-up

  • @ Jamie / Tom to follow up with GH / Figma / Drive / etc permissions for Davide and Lexie
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Nov 22, 2022

[2022.11.21] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

Notes from Meeting

  • Sydney almost done with Something Else flow
  • Davide adapting designs to new LP. Doing on work laptop and his work stuff was getting merged into PRs. So remaking on personal computer.
    • In for December. He will be out for 2 weeks in January
  • Design followup / corrections to last update by Dev.
  • Arpita is working on Employment flow - Rename from "Job"  #700. almost going to submit PR soon
    • want to keep future goals / why page
  • [ ]

  • [ ]

Action Follow-up

  • @
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Nov 29, 2022

[2022.11.28] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

Notes from Meeting

  • Davide got access to onboarding docs / team roster / team drive
  • Davide: how much space between images and text portions on LP? how much space should content take up in LP?
    • spacing btwn illustration and content copy does differ for some. Anita can leave details on the Figma Design Handoff page. how much space should be on the sides? Sydney: Content container component should cover the sides.
    • clicking something in Figma should show dimensions (red numbers) in Inspect mode. some places in Figma are not 1:1 to live app (and require eyeball - e.g. anything that involves progress bar at top of form - way too thin, content width on most designs is diff from width of content container component. Some things would be helpful to address in pause period btwn versions). Syndey: recommend digging around some pages to see how they're put together. Many components built out that could be re-used and make small adjustments to
    • Design looking to update Design System, could we match the Design System/components for Dev? Some things built into components dev side already but no Design System Dev-side. Dev suggests usage of Inspect tool, Sydney can help with questions. Inspect tool shows green interface sizes. Max widths, content containers that Dev uses. Should these be used to see dimensions of components themselves, slider exists to help with break points dimensions. Defaults by Figma 1440, iphone 11 default. Would be good to reflect max width - lowest mobile and adjust grids we're using.
  • suggestion of being more feature / page focused in future ala Sam Content suggestion
    • Open to suggestions from team as far as how to best approach this more so that we can iterate more easily and reduce shotgun/spreading too thin with multiple changes at once. Possibly approach starting in Jan 2023 / once dev changes have been made for IUT2
    • Davide: his company does 2 week sprints across all teams, having things laser-focused to really push things. could we bring in more of this
    • EA project uses a rough light form of 1-month sprints. PM's can do more to communicate more closely.
  • How could Design better assist Dev with the changes?
    • feel free to throw over tickets for what feedback we notice. After IUT2 done, we expect to be slow-going Dev side.
    • are we looking to deploy/release live weekly? monthly? supposed to be weekly. Suggestion to check in with Daniel.
  • We're looking to continue meeting 12/5 next week for those who are available.
    • Jamie, Anita will be in

Action Follow-up

  • @ Design Team - when DS work is more done during transition, check back in with Dev regarding Design Systems/components and how to better align them with Dev-side components.
  • @ Tom to check in with Daniel about pushing latest changes live. Plz merge Sydney's latest

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Nov 29, 2022

[2022.12.05] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
    • Review previous action items outstanding
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Check-in on IUT2 implementation - how's it going? any questions / help needed
  • [ ]
  • [ ]

FYI / Announcements

  • HFLA Holiday Party in LA area - several of us will try to stop by

Notes from Meeting

  • Check-in on IUT2 implementation - how's it going? any questions / help needed
    • Design finishing deck handover for UXR
    • Davide got updated images from Daniel, site was not performing with original images, images may also be too small now. Working on responsiveness to be better - resizing screen how it looks for browser (e.g. looks good on computer screen but mobile phone). Do Design's mobile designs help? Dev sees them but not implemented yet - will use them for reference. Design Leads can clarify if not making sense. Would tablet sizes help? prob no since main content doesn't take up too much space.
    • Daniel been busy with work. To review latest items ready for review (Something Else Flow and Unemployment Flow changes) and then deploy after
  • Should we start Dev meetings back up? not for now. seems our Slack chats working but will watch
    • agree a dev Slack channel would be helpful for conversations
  • [ ]

Action Follow-up

  • @ Tom - to set up Slack channel for Dev
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Dec 13, 2022

[2022.12.12] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Check-in on IUT2 implementation - how's it going? any questions / help needed. How much is left? Any idea on timing?
  • [ ]
  • [ ]

FYI / Announcements

  • last meeting for the year. We're planning on resuming meeting 1/2/23 in the new year

Notes from Meeting

  • Going forward, Sydney will help with PR reviews to help unblock flow more. Code changes are in dev branch (which is the staging branch), then merged to Main/production. Devs pull to their local machine to work on changes then merge back up. Daniel helps merge to Main and is the only one with access at this time.
  • Arpita is good from their end atm
  • Davide is leaving the project per Slack channel message. Unclear if temporary or fully leaving. Jamie/Tom/Daniel to check in with them
    • What happens to LP Update they were working on? Could their work be picked up? May be that next person resumes LP update from scratch. Team will assess and see after a week

Action Follow-up

  • Review previous action items
  • @
  • @

Items for next weeks agenda

  • Restart recruiting new Developers to join the team
  • Carry over to next week anything we didn't get covered this week
    • Make next weeks agenda

@jamiesiu
Copy link
Member Author

jamiesiu commented Dec 13, 2022

[2023.01.09] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Welcome back! 2023
  • New Volunteer Royal joined the team!
  • IUT2 Check-in and Support/Questions
  • Dev Recruiting
  • [ ]

FYI / Announcements

Notes from Meeting

  • Welcome back! 2023
    • [ ]
  • New Volunteer Royal joined the team!
  • IUT2 Check-in and Support/Questions
  • Dev Recruiting
    • ensure requirements are clear for Devs to make it easier for folks joining
    • what we looking for in a tech lead? someone communicative and responsive. having them reachable to help clarify requirements with who wrote a ticket
    • we use react and typescript, lil bit of JS.
    • Tom to post outside the org
    • Lead dev is supposed to review and merge PRs. how can we help ease this and share the responsibility? Sydney doing reviews now too. Seems like Arpita also has
  • Arpita still works with HFLA website team, supporting them. Seems like no difference btwn projects. Seems project requirements and issues are clear to them. Support from Design/Content via Slack pings and ability to reach out
    • having linked issues with Figma is helpful
    • Daniel was helpful for Arpita ramping up
  • live Issue right now is preventing LG from advancing
    • design unable to inspect and grab live dimensions
    • https://expungeassist.org/welcome seems to create an infinite loop. should give 404
    • Did Daniel merge Dev branch to main branch recently? Arpita working on current issue seems to be working fine. Maybe something that was missed in update from dev to main. Arpita to pose qn in Slack
  • Landing page update Update Landing Page #704
    • who would be looking at this? unclear where left off with Davide leaving
    • Anita to help provide some info about image sizes
  • Any tools aside from Inspect Tool that we could use for Design/referencing?
    • [ ]
      [ ] Did Daniel merge Dev branch to main branch recently?
    • Arpita working on current issue seems to be working fine. Maybe something that was missed in update from dev to main
    • [ ]

Action Follow-up

  • Review previous action items
  • Tom/Jamie/James to find time this week with Daniel to discuss their eventual transition
  • Anita to help provide some info about image sizes to Update Landing Page #704
  • Tom to create recruiting posts for Dev roles outside of HFLA org
  • Jamie to join 1/16 HFLA onboarding and help recruit for Dev/Lead roles

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Jan 24, 2023

[2023.01.23] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • IUT2 Progress Check-In
  • Design Requests for Dev (if any)
  • Dev Team Recruiting
  • [ ]

FYI / Announcements

  • Next week is team planning / first week of month. All discipline syncs cancelled (including Mon/Thur dev syncs)
  • Jamie Siu out 1/27 Friday to 2/3 Friday
  • James Shin out 1/30 Monday to 1/31 Tuesday
  • Tracy N out two weeks for personal time / self care
  • Royal in boot camp meetings at this sync time

Notes from Meeting

  • Design team working on Design System, doing discovery/exploration of what it is and entails. Important to have dev involvement in creating and maintaining. Should make future development easier and smoother through use of shared re-usable components. Given focus on IUT2, will not over-burden dev team at this time. Danielle/past HFLA volunteer built Design System. Storybook.js used by devs to store re-usable code. Daniel said we don't use now but open to doing in future. Do our devs have experience using it? May be learning curve. Tom to talk to team about it
  • Dev recruiting - Tom G. potential new lead considering our team and who would like to meet our folks more.
  • Anita confirmed with Sydney on dimension aspects 375px on mobile interface, what's widths of text input boxes, and cards to preview that section? What breakpoints does dev use?
  • Review of the board together - new owner needed for Update Landing Page #704 (moved to backlog), Employment flow - Rename from "Job"  #700 completed/merged by Arpita, Letter Generator does not advance when clicking Next Button #768 fixed on live by Daniel
  • ETA for completion of IUT2 changes? UXR would like to know for their planning. Hard to estimate right now given team bandwidth in flux. Daniel used to help a lot and is not as available given their new job and in transition. So will continue to check in weekly. Loosely say for now about 1-2 months out.
  • We plan to do a walkthrough of the site together after IUT2 changes are done. At all-team meeting or sync time to check for bugs / fixes
  • [ ]

Action Follow-up

  • Review previous action items
  • Tom/Jamie to follow up with Daniel on their availability to help out with coding front
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Feb 14, 2023

[2023.02.13] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

  • [ ]

Notes from Meeting

  • PM has been chatting with Bonnie/Content/Dev about ChatGPT. Bonnie is supportive. To follow up further with UXR on their perspective.
  • CfA org change and impact is still being fleshed out. We should resume our ongoing work as expected for now.
    • We had some concern about legitimacy of our product from IUT1 that may involved CfA verbiage. Do we want to involve UXR to further clarify the impact of these CfA changes?
    • About Us page update had been put on pause due to CfA change and we'll pick it back up Update About Us Page #703. Raman to look into
  • Status on the Landing Page update
    • PM to follow up with Daniel. Sydney was following up with them previously
  • Bug that Kyle / Anita encountered using LG - Flow goes from Job to Recovery pages to then a blank page. blank preview page rendering. Happens on Google Chrome (updated) but not for all users
  • Review of existing tickets in Ready for Review
  • [ ]

Action Follow-up

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Feb 28, 2023

[2023.02.27] Agenda and Notes

Attendees

  • Thomas PM
  • Lexie
  • Sydney
  • Tom G
  • Anita
  • Serena
  • Raman
  • Ailin C
  • Troy
  • Royal
  • Tracy
  • Phu
  • Justin
  • Alexis
  • Jamie

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • Landing Page Update / IUT2 Implementation
  • Design / Content side check-in
  • [ ]
  • [ ]

FYI / Announcements

  • All-Team meeting is next week

Notes from Meeting

  • Lexie / Raman / Troy introductions. Info from Design to Dev is passed via Figma. Design creates GH issues with requirements and points to designs pages with links. Raman to go to onboarding. Troy has setup issues - using npm, should be able to run after cloning. Reach out to Sydney with issues. Are we setting up individual branches other than dev/main? Create branch off dev branch, name with issue # and general description of issue.
  • Sydney is reviewing landing page and will merge soon into dev. UXR wants to do Landing Page-focused usability testing until LG updates are done. Pending corrections for LP. Sydney needs to double-check other things on dev okay to go to main.
  • Updated flow in GH - when issues are done dev-side vs done per issue requestor. Dev is looking into a staging environment. In past and now, we would likely just push to production first in lieu of this. Goal to push things live more often. Corrections would come in new tickets.
  • Improving flow btwn Dev, Content and Design. When/if issues need more context on problem being solved or design decisions, whys etc. More collab if complex or new features. If things are more static, then less a concern
  • CMS / Tom G - demo would be helpful
  • Design Systems - Design is auditing colors. Design is focusing on auditing mobile wireframes, consistency across board/naming. Bugs noted in categories / recovery flow - is blocking Design from review, Sydney is working on it. Material UI design library v4 is used by Dev https://v4.mui.com/. Design to review and can ask questions after for more info.
  • When did the bugs start? Daniel's push had overwrote some things others wrote (e.g. something else flow). Process issue - team was much smaller before and version control process was different. Normally should go local -> dev -> main
  • [ ]
  • [ ]

Action Follow-up

  • Review previous action items
  • @
  • @

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Mar 7, 2023

[2023.03.06] Agenda and Notes

Attendees

  • Thomas PM
  • Lexie
  • Sydney
  • Tom G
  • Anita
  • Serena
  • Raman
  • Ailin C
  • Troy
  • Royal
  • Tracy
  • Phu
  • Justin
  • Alexis
  • Jamie

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

  • All Team Meeting

Notes from Meeting

  • Review of the updated LP https://expungeassist.org/#/
    - [ ] Seems some headers are not as clear/blurry to some of team - not affecting usability. Can document in GH for prioritization based on time/team availability
    - [ ] Some things are not in alignment (e.g. image causes eye to jump) and spacing is not as expected. Image for "What is EA?" affected by break points? 900
    - [ ] Some things in quality are not as clear as in Figma fidelity e.g. the sample letters. Artifact folder in GDrive. Way to export things on Figma that don't impact quality and not large file? SVG best for resizing? @ Thomas to check with Daniel/Sydney on where images came from
    - [ ] Section that has 1, 2, 3 How it Works has text as images (intentional design choice to make easier for dev) but comes off as slightly blurry
    - [ ] Partnership opportunities intended to be just the text with purple block. Better to stretch out purple color? But then might confuse footer with rest of page (as shown in Start Now). Welcome page in LG could be changed away from purple
    - [ ] Start Now button at top "Quick and easy way.." is in lower case
  • Raman will look to pick up first issue. Able to clone repo
  • What else is remaining for IUT2?
    • Bug preventing getting past the Recovery flow is now fixed, able to advance further now so Design should be able to do Design System audit color.
    • Changing recovery to self-improvement, would changing it cause any issues in flow. Other flows changed name as well. Employment flow change away from job. Where else does rename impact things? (preview pages and website URLs) @ Design to review existing GH issues for where categories rename impact flow and will document in issues.
    • Do the latest pushes include the other changes from Sydney?
    • New bug appears where clicking categories, advancing, and then going back causes it to go to Recovery Flow page before going back to the categories selection. @ Raman will create a GH issue to capture this and we'll prioritize since it affects usability flow.
  • [ ]
  • [ ]

Action Follow-up

  • Review previous action items
  • @ Raman will create a GH bug issue for where going back brings user to the Recovery page by mistake
  • @ Thomas (PM) to check with Daniel/Sydney on where images came from for LP update
  • @ Design/Anita to review existing GH issues for where categories renames impact flow and will document in issues for Dev.

Items for next weeks agenda

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

@jamiesiu
Copy link
Member Author

jamiesiu commented Mar 14, 2023

[2023.03.13] Agenda and Notes

Attendees

  • Thomas PM
  • Lexie
  • Sydney
  • Tom G
  • Anita
  • Serena
  • Raman
  • Ailin C
  • Troy
  • Royal
  • Tracy
  • Phu
  • Justin
  • Alexis
  • Jamie

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

  • Anita is out for vacation 3/10-3/19

Notes from Meeting

Action Follow-up

  • Review previous action items
  • @ Thomas to check in with Arpita
  • @

Items for next weeks agenda

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

@jccchurch
Copy link
Member

jccchurch commented May 8, 2023

[2023.05.08] Agenda and Notes

Attendees

  • Thomas PM
  • Sydney
  • Tom G
  • Anita
  • Raman
  • Ailin C
  • Troy
  • Phu
  • Justin
  • Alexis
  • Julia
  • Analicia
  • Lane
  • Liz
  • Michelle

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

  • [ ]
  • [ ]
  • [ ]

FYI / Announcements

  • [ ]

Notes from Meeting

Issue 690 Option to download word doc
For usability testing - the text is just simple text
Ideally this button will be ready for IUT2
Dev has other issues to finish up - Sydney is ensuring issues are solved before closing
After shipping for testing, will close issues
Create a system between dev & design to clarify what is done
Design may make changes to wireframes and will copy them over to master pages
Master pages will contain most up to date designs
This is something we could achieve with a Github action - that would send a slack message
Sydney will do all issues at once & advise when backlog is cleared
Once things are in design handoff, they shouldn’t be updated anymore - this could cause problems
Open up a following issue and create a dependency
Previewing final statement for example - copy changed - realized that design handoff was already made & content was unsure which language got used
Even with small copy changes - still make an issue - otherwise it won’t be noticeable to the developer and could get missed
Anita will share with Sam
Overall - figuring out a better process between 3 teams
Automated slack messages would be helpful
Does issue 690 look ok as is? Or should it be separated into 2 - one for copy and one specific to the addition of the button that says “download word doc”?
Content may want to change the copy
Sydney - leave issue as is for the moment - if copy does change, then add extra issue
Placeholder text could cause an issue

Design & Content want to work on return button (live on website)
Noticed that since website does not collect data, and there is a huge risk for error - the whole letter could get erased
Design is trying to prevent user error with modal pop ups
Design had worked on modals but stopped due to bandwidth - this issue became low priority
Anita would like to return to this issue if dev has bandwidth
Design will finalize & handover to dev - is it feasible? Or is there a better idea?
Sydney - does it actually delete the letter? Things are not saved beyond local - if that button links to the homepage the letter may be retained - that would solve the issue
If you’re navigating site within website - it will save the data - but the second you leave or press browser back/forth button then things are deleted
Might be good to include some warning to avoid data loss
Could lose people that way
Use disclaimer to clarify which steps will delete stored info

Issues that are Ready for Review
Automate this process to move forward faster / don't have to look through issues individually
Efficiency can be improved here, dev will look into

Padding & responsive design - alignment seems to shift especially in header & menu
FAQ gets pushed to the left - is this a screen size issue? What can design do to help with this?
Consider this a bug & open a ticket for it
May have to do with content containers - design will write an issue with screenshot if possible - dev will look into it

Items for next weeks agenda

  • Establish facilitator & notetaker rotation
  • Make next weeks agenda

@lmitch10
Copy link
Member

lmitch10 commented Aug 29, 2023

[2023.09.11] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests

New Meeting Items

FYI / Announcements

  • [ ]

Notes from Meeting

Items for next weeks agenda

  • Establish facilitator & notetaker rotation
  • Improving cross collab on Github using issues: Create issues for each team vs handing one issue from team to team
  • Make next weeks agenda

@lmitch10 lmitch10 added size: 1pt can be done in 6 hours or less and removed size: missing labels Sep 19, 2023
@amejiamesinas
Copy link
Member

amejiamesinas commented Oct 12, 2023

[2023.10.12] Agenda and Notes

Attendees

Recurring items:

  • Accountability and Support Check
  • Blockers Support / Help Needed
  • Progress Share / Feedback Requests
  • [ ]
  • [ ]

New Meeting Items

  • Roadmapping
  • Accessibility
  • Milestones and Role Issue Tags

Design Questions:

  • The list of questions is provided at the beginning or prior to the beginning. This will give the user an idea of what questions they will be answering.
  • All the questions and answer fields are on one page
  • Give the user the chance to download a copy of the questions
  • Design similar to resume builders. The user can see it building as you fill in the questions
  • if they are in the middle of their letter and have a question, and hit FAQ in the top navigation, they will also lose all their work, can dev fix this or does this wording need to be changed too?

FYI / Announcements

  • [ ]

Notes from Meeting

Items for next weeks agenda

  • Establish facilitator & notetaker rotation
  • Improving cross collab on Github using issues: Create issues for each team vs handing one issue from team to team
  • Make next weeks agenda

@sydneywalcoff
Copy link
Member

sydneywalcoff commented Feb 3, 2024

Since this meeting has been cancelled, I'm going to close this issue.

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 priority: low question Further information is requested role: design anything related to design role: development anything related to code role: product management size: 1pt can be done in 6 hours or less
Projects
Development

No branches or pull requests

9 participants