Pre-class Checklist

Unified checklist — 2 weeks before through morning-of

TRAINER ONLY

Pre-class checklist 9 steps · 2 weeks → T-60 min

How to use this checklist

Work through every page below in order. Tick each checkbox before delivery day — progress is saved automatically (per delivery date). Reopen any page to see what is done vs still open.

TipProgress tracking

On first visit, sign in with the trainer password, then set or choose a workshop session (delivery date + name). Checkboxes sync to Cloudflare D1 (SQLite) when configured; otherwise they persist in this browser until cloud sync is enabled. Lead and co-trainer on the same session see the same cloud state.

NoteScope — technical platform prep

This checklist covers infrastructure and lab environments only (ADLS2, Databricks, Snowflake, roster/portal, site deploy, morning-of platform smoke tests).

Classroom logistics (projector, printed handouts, QR codes, seating, whiteboard) → Facilitator guide § Before the room opens.

NoteSingle source of truth

Technical checkboxes live here (2 weeks before → T-60 min platform verify). The facilitator guide owns day-of delivery — schedule, module rhythm, room setup, troubleshooting.

Related: facilitator-guide · module-delivery-pattern · reflection-prompts


Checklist pages (read in order)

# Page When Topics
1 ADLS2 storage 2 weeks before Set month in workshop-data.json · TLC upload · ADLS2 storage account access key · ADLS2 SAS token
2 Databricks workspace 2 weeks before Git folder · groups · Unity Catalog · clusters · SQL warehouse
3 Snowflake (trainer) 2 weeks before Trainer trial · external stage verification
4 Aiven Kafka 2 weeks before Cluster · certs (Module 8)
5 Databricks secrets 2 weeks before CLI · workshop-scope (Module 8)
6 Materials & credentials 1 week before Roster · portal · GitHub invites · site deploy
7 Power BI 1 week before Desktop build · Service publish (Module 7)
8 Day before Day before Reminder email · token expiry · dbt smoke test
9 Morning of T-60 min Live platform verification (Module 8 generator)

After page 9, continue the day-of runbook: Facilitator guide § Before the room opens.


Dependency order

Infrastructure pages 1 → 5 follow platform dependencies — not alphabetical order:

  1. ADLS2 — Databricks 00_setup.py and Snowflake external stage need ADLS2 storage account access key and ADLS2 SAS token from here
  2. Databricks workspace — needs ADLS2 storage account access key
  3. Snowflake (trainer) — external stage needs ADLS2 SAS token from ADLS2
  4. Aiven — Kafka cluster and certs (Module 8)
  5. Databricks secrets — needs workspace (page 2) + Aiven credentials (page 4)

Pages 6 → 7 are one week before (materials can be prepared while infra is verified). Pages 8 → 9 are the final countdown.


Trainee pre-work

Send expectations and links from Trainee pre-work (site URL, token, fork/Codespace, Snowflake trial, .env). Credential timing: schedule below.


Credential Distribution Schedule

Item When How
GitHub fork access 1–2 weeks before Trainer adds collaborator (Read) on source repo using roster GitHub user / GitHub emailTrainee pre-work § GitHub fork access
ATTENDEE_ID Module 1 (start of day) Printed card or slide → paste into .env
.env personal credentials Before Module 4 Exercise: dbt § Configure .env — one step when starting dbt lab
Databricks workspace URL Module 2 Email invite (sent 1–2 weeks before) → paste into .env
ADLS2 storage account access key Module 2 Verbal or printed — never in Git
ADLS2 SAS token Module 3 Printed card — has expiry date
Aiven credentials Module 8 Printed card — SSL certs + Service URI
Snowflake account / user / password Self-service (before Module 3) Each attendee creates own trial → paste into .envnot on trainer card
Databricks PAT Module 2 / 4 (dbt) Self-service via Settings → Access Tokens → paste into .env

Card contents: § Materials & credentials — Credentials Sheet


Quick Reference — Who Manages What

Platform Who creates account Who runs setup scripts Notes
GitHub (lab fork) Trainer (collaborator invite) · Attendee (fork + Codespace) Attendee forks after invite — § GitHub fork access Roster GitHub user / GitHub email required for every trainee
Lab source files Trainer (emergency approval only) Rare — § Emergency fallback Do not send to whole cohort; extra time Modules 2–3
Databricks Trainer (workspace + invites + Workshop policy) Attendee creates own cluster · runs 00_setup.py Trainer shares Git folder (Can Run); no bulk cluster creation for roster
Snowflake Attendee (own trial) Attendee runs 02_account_setup.sql Creates DE_MASTERCLASS, DE_WORKSHOP_WH, DE_WORKSHOP_ROLE
ADLS2 Trainer (one shared account) Attendee uses ADLS2 storage account access key in notebook Trainer generates ADLS2 storage account access key + ADLS2 SAS token
dbt Attendee (Codespaces or Docker) Attendee creates .env from .env.template; devcontainer generates profiles.yml Targets Snowflake with DE_WORKSHOP_ROLE — see § Attendee .env file
Aiven Kafka Trainer (one shared cluster) Attendee adds secrets to Databricks Trainer starts activity generator on Module 8 morning
Power BI Trainer (Module 7 demo) · Attendee (optional self-paced) Trainer builds in Desktop; attendee uses free Desktop after Module 4 Pro/Fabric optional for Service demo