Claude Code for engineering teams

Who it is for

Engineering teams of two to thirty developers who already ship software and want to adopt Claude Code without turning their process upside down.

What you leave with

Claude Code installed and authenticated against your own Console organisation
A repository configured with the context files your codebase actually needs
A review workflow: what the agent may change alone, and what needs a human first
Guardrails for secrets, migrations and production access
Measurements to judge whether time per change is falling

Day one

Block	Content
09.00–10.30	Console organisations, API keys, workspace and repository context
10.45–12.00	First working loop: describe, generate, review, correct
13.00–14.30	Repository conventions: how much context is enough
14.45–16.00	Hands-on on your own repository, deliberately small tasks

Day two

Block	Content
09.00–10.30	Review workflow and code review with agent-generated changes
10.45–12.00	Guardrails: secrets, destructive commands, production systems
13.00–14.30	Measuring impact: a small set of honest metrics
14.45–16.00	Rollout plan for your team, written during the session

Usage costs. Seat is included, but Claude API usage during class runs on your own Console account. Expect a few US dollars for two days at class volume.