Joining the TDM Calculator Team

Introduction

Welcome to the Hack for LA TDM Calculator team! This guide will help get you up to speed on what you need to know to get started as a project team member.

Let's get you started!

General

• Make sure that you can make the meetings times.
• Read the Guide for New Volunteers
• Read the TDM Background

UI/UX Designer, Product Manager, or Business Analyst

• Review the Product One Sheet to get a sense of the business cases and functionality

Developer

• Review the Back End and front end issues in Prioritized Backlog, In-Progress, on Dev- not yet pushed to production and Released 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

If you like what you see:

• Join the #tdm-calculator Slack channel
• Post on Slack introducing yourself and 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
• send us your Gmail address
• We will set up an onboarding session for you which will include:
  • Adding you to our Shared Google Drive
    • Once you have access to the TDM Calculator Google Drive, add yourself to the Team Roster
  • Adding you to our TDM GitHub teams (read and write)
  • Adding you to TDM Figma
  • Adding you to TDM 1Password vault (if needed)
• Review our Standard Issue Format, so that you know how to read issues

Meeting Times

See all Meeting Times for TDM in your timezone here: https://www.hackforla.org/projects/tdm-calculator

Meeting Name	Who Attends	Time	Day of the Week	Frequency
Team	All Team Members	7PM Pacific	Wednesday	Weekly
Stakeholders	LACP/LADOT Stakeholders and PMs (sometimes attended by team leads. Anyone from the team is welcome to observe)	4PM Pacific	Tuesday	Every Two weeks
Stakeholders Prep and PM	Bonnie, PMs and sometimes leads	IPM Pacific	Thursday	Weekly

How we work

• Our GitHub project board uses Kanban automation and methodology

• Read the Guide: Kanban for Successful Open Source Projects (WIP)

• Follow these guidelines

• • Items in the prioritized backlog column are not assigned yet
• • Items that are assigned should be in the in progress column
• • Only one person should be assigned to each issue (exception: multiple people can be assigned to an agenda)
• • Only one issue should be assigned to a person (exception: you can be assigned also to agendas)
• • If there are questions needed (i.e., you have a blocker, then you can put the issue in the questions and review column with a note about what you need as the last comment). Please do not assign the person you need help from to the issue. This is how Bonnie got assigned to 100 issues.

• Provide weekly updates (in comments at the bottom of your issue) using this template

Please provide update
1. Progress: 
2. Blockers: 
3. Availability:
4. ETA: 
5. Pictures (if necessary): 

How to fill out the template Please provide an update Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

Getting fully up to speed

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

1. Product One Sheet to get a quick sense of the overall product.

2. Volunteers Training Deck

3. Roadmap & Release Plan: Learn what functionality will be developed in the current and upcoming versions

4. Interactive Mockup: Familiarize yourself with the functionality and UI/UX of the upcoming release.

5. Strategy & Vision: Learn why TDM CAlculator should exist and what it is built to accomplish.

6. Product Requirements: Review the specific functionality being developed in the current release.

7. Database Schema: Review the types of and relationships among data referenced in the product requirements

Good to go!

---

Role

• Research
• Design
• Product
• Developer

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