Running engineering organisations that ship
Leading engineering rarely means writing the code – and still means deciding, every week, whether what gets built is any good. That is where this track aims. Leading SAFe and the SAFe Agilist foundations cover scaling lean-agile ways of working across more than one team; engineering-manager and technical-leadership essentials take on the closer-in work: growing people, running teams, and keeping delivery healthy under pressure.
The decisions reach across every level: architecture you sign off without writing, product and delivery foundations that connect what gets built to why, and the alignment work – OKRs, scaling frameworks – that keeps a growing organisation on course. Little of it makes headlines, and most of it is what actually determines whether teams ship.
AI is the newest pressure on the job. You are pitched a productivity miracle and a doom narrative in the same week, and underneath the noise you still have to make staffing, tooling and roadmap calls. So the track adds enough hands-on exposure – a deep dive on Claude Code or a peer – to size up the hype yourself, plus the architecture-review lens for keeping velocity from quietly turning into debt.
The lever you actually hold is what you protect: review time, integration slack, and a process people trust enough to follow when no one is watching. No tool supplies any of that. For the route your engineers themselves walk, see the AI-Assisted Software Development path.