Pre-work Checklist: Researcher: Vaisali Krishna Kumar

[vaisali89]

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events

Overview

As a new researcher on the HfLA website UX team, fill in the following fields as you complete each onboarding item.

Action Items

• Add yourself to the #hfla-site-ux and #hfla-site Slack channels
• Share your Gmail address with the research team lead
• (once added to the drive) Add yourself to the team roster.
• Confirm with the research team lead that they have added you to the meeting invites
  • UX weekly team meeting, Thursdays 5 pm PST
  • All team meetings (UX, Development, Product), Sunday 10 am PST
  • Research team meetings, Wednesdays, 2:00 pm PST
• Confirm with the research team lead that they have added you to Github repo
• Self Assign this issue (gear in right side panel)
• Add this issue to Projects: Project Board (gear in right side panel)
• Confirm that the research team lead has given you login credentials for the team Miro and Figma accounts
• Attend weekly team meetings:
  • UX weekly team meeting, Thursdays 5 pm PST
  • All team meetings (UX, Development, Product), Sunday 10 am PST
  • Research team meetings, Wednesdays, 2:00 pm PST
• Review the prioritized backlog to see what Research Issues are available (this will not be the complete list, but will give you some talking points for your conversation with your lead).
• Meet with team lead to receive first assignment
• Once you accept an assignment (issue), please add the following in a comment

Availability for this week:
My estimated ETA for completing this issue:

• Weekly, please also provide an update on the issue

provide update
1. Progress
2. Blockers
3. Availability
4. ETA

Resources/Instructions

• Project Board filtered to show role: user research
• Miro
• Figma
• Googledrive-UI/UX
• Googledrive-HackforLA website
• UX Research Presentations
• Weekly Meeting Agendas
• Example of an issue with really good updates, this issue also is a good example of when you have finished an issue, but there is still more work to be done, so it leads to a new issue being made instead of changing the scope of the original issue.

[github-actions]

Hi @vaisali89.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels