How We Work#
Team Meetings#
The section below outlines our team’s primary meetings and their purposes, as well as our our team’s shared meeting standards.
Current Meetings#
New analysts, look out for these meetings to be added to your calendar.
Name |
Cadence |
Description |
|---|---|---|
Technical Onboarding |
Week 1 |
To ensure access to tools and go over best practices. |
Analyst Data Roundtable Meeting |
Thursday, Weekly |
Branch meeting to share your screen and discuss what you’ve been working on. |
Analyst Administrative Meeting |
Wednesday, Bi-Weekly |
Branch meeting for administrative updates every other Wednesday. |
Team Social Meeting (Optional) |
Wednesday, Bi-Weekly |
Due to the geographic spread of our branch, every other Wednesday we get together for an optional hour of chatting. |
Teams Communication Channels#
When communicating with Caltrans coworkers, we use Teams. The message retention policy for Teams is not permanent. Open up a GitHub Issue with the appropriate template for any posts you make on the Data Analysis and Data Office Hours channels that are worth keeping for posterity’s sake and/or are lengthy and complex in nature.
Channel |
Purpose |
Description |
|---|---|---|
#General |
Discussion |
For all employees in Caltrans Division of Data and Digital Services (DDS). |
#Data Analysis |
Discussion |
For sharing and collaborating on data analyses. |
#Data Office Hours |
Discussion |
A place to bring questions, issues, and observations for team discussion. |
#Data Science |
Discussion |
For all employees in DDS’s Data Science Branch. |
Slack Communication Channels#
When working with contractors, we use Slack.
Channel |
Purpose |
Description |
|---|---|---|
#data-warehouse-devs |
Discussion |
For people building dbt models - focused on data warehouse performance considerations, etc. |
(analytics-repo)= |
GitHub Analytics Repo#
The data-analyses repo is our main data analysis repository, for sharing quick reports and works in progress. Get set up on GitHub and clone the data-analyses repository using this link.
For collaborative short-term tasks, create a new folder and work off a separate branch.
For large and long-term projects, create a whole new repo.