15 working days · full-time
Day-by-Day Schedule
Three weeks plus a closing capstone block, ~6 hours of hands-on work per day plus assigned courses. Week 1 is everyone; Weeks 2–3 run the two tracks in parallel; Days 12–15 are a cross-functional capstone. Checkpoints land on Days 3, 6, 11, and 15.
Daily rhythm for the lead: 15-min morning briefing (today's goal, yesterday's gaps), hands-on blocks below, end-of-day 10-min standup where each person says what they shipped.
All work happens in the sandbox training repo(s) from the README pre-flight — never on client code. “Course:” lines refer to the course catalog. Ticking “Mark day as complete” on a day page is saved in this browser, or to your Google account when you sign in.
Week 1 — Shared Fundamentals (Days 1–3)
EveryoneWeek 2 — Track split (Days 4–8 in parallel)
DeveloperBA/QADays 4–8 in parallel · Developer: Claude Code Desktop core · BA/QA: Claude Desktop for planning
Week 3 — Track split, deeper (Days 9–11)
DeveloperBA/QADays 9–11 · Developer: Extend, automate, review · BA/QA: Automated testing
Days 12–15 — Cross-functional capstone (everyone)
EveryoneEveryone, Days 12–15. One real-ish mini-product: “client” (the lead) wants a feature for the training app.
After the program
- Weekly 30-min “Claude guild”: one person shows one workflow; skim the What's new digest.
- Optional courses for the next step: Building with the Claude API, MCP advanced topics, Building effective human-agent teams (see the catalog).
- Re-run this plan's checkpoints as interview-style onboarding for new hires.