How to Customize Your SAFe for the AI Age
Most of your scaling apparatus is now optional. Your first principles are not. A companion for leaders running SAFe while adopting AI-native, spec-driven development, and trying to tell the difference.
Most of your scaling apparatus is now optional. Your first principles are not. A companion for leaders running SAFe while adopting AI-native, spec-driven development, and trying to tell the difference.
Is Scrum still relevant when agents write the code? Yes, and more than before, provided you are willing to customize it. A companion to the Scrum Guide walking the accountabilities, events, artifacts, and values for a team running an AI-native, spec-driven lifecycle.
A companion to the Kanban Guide for Scrum Teams for AI-native product teams. What changes in your Definition of Workflow, WIP limits, flow metrics, and Scrum events once agents do the building, and what happens to scaling when the old dependencies start dissolving.
Your scaling mechanisms were a choice: coordination overhead that was worth it at the time. AI has not changed the physics of coordination. But it is like going to a planet with different gravity, so you need to adjust how you walk.
Don't ask whether you still need Sprint Planning. Ask whether you still have an alignment problem. Separating the mechanism from the capability is the whole game right now.
Spec-driven development looks like a step backward if you read it as requirements theater. The better frame: the spec is a higher-level language for intent.