Join the Team - hackforla/VRMS GitHub Wiki

Welcome to the VRMS product development team! This guide will help get you up to speed on what you need to know to get started as a project team member. Edit: we are doing an audit of our resources. If you have any questions reach out to us on Slack

Who are you?

See below to find a sequence of immediate action steps:

Web Developer or Data Scientist

  1. Read the Project Introduction
  2. Review the Development Board Prioritized Backlog, In-Progress, and Done lists to get a sense of current/recent tickets. Don't worry if you don't see anything at the correct difficulty level for you.
  3. If you like what you see, join the project Slack channel
  4. Post on Slack identifying that you read this part of the Wiki, why you like this project, how you'd like to contribute, and what relevant skills you have to offer; request a short onboarding meeting. Don't worry if you're green, we will find the right way for you to contribute while learning.
  5. During onboarding you will complete the following required actions: receive access to project's Google Drive and GitHub repo, enable Github 2FA
  6. Once you have access to the VRMS Google Drive, add yourself to the Team Roster
  7. Complete the steps in the Getting fully up to speed section below.

UI/UX Designer, Product Manager, or Business Analyst

  1. Read the Project Introduction
  2. Review the Product One Sheet to get a sense of the business cases and functionality.
  3. If you like what you see, join the project Slack channel
  4. Post on Slack identifying that you read this part of the Wiki, why you like this project, how you'd like to contribute, and what relevant skills you have to offer; request a short onboarding meeting. Don't worry if you're green, we will find the right way for you to contribute while learning.
  5. During onboarding you will complete the following required actions: receive access to project's Google Drive and GitHub repo, enable Github 2FA. (Yes, even non-devs will use GitHub for project-management/kanban.)
  6. Once you have access to the VRMS Google Drive, add yourself to the Team Roster
  7. Review the materials in the Getting fully up to speed section below.

Getting fully up to speed

Once you've onboarded, review the following documents in order to understand the purpose, objectives, features, and architecture of VRMS. No matter your role they'll all be useful, but you can review them with varying degrees of depth depending on the expected focus of your contributions.

  1. Product One Sheet: Get a quick sense of the overall product.
  2. Interactive Mockup: Familiarize yourself with functionality and UI/UX of the upcoming release.
  3. Strategy & Vision: Learn why VRMS should exist and what it is built to accomplish.
  4. Roadmap & Release Plan: Learn what functionality will be developed in the current and upcoming versions.
  5. Product Requirements: Review the specific functionality being developed in the current release.
  6. Database Schema: Review the types of and relationships among data referenced in the product requirements

Good to go!

Accessibility standards

Title III of the Americans with Disabilities Act (ADA) requires that all websites be accessible to people with disabilities. The World Wide Web (W3C) Consortium's Web Content Accessibility Guidelines (WCAG) 2.0 Level AA function as the current legal standard for website accessibility.

Get acquainted with accessibility: https://www.ada.gov/pcatoolkit/chap5toolkit.htm

Offboarding

  • Leads need to keep their team accountable to make sure documentation is being written after every update

Back to Home