Where SAFe transformations stall
Most organizations adopt the Scaled Agile Framework (SAFe) on paper and keep working like it's still waterfall underneath. The ceremonies happen; the cadence doesn't. PI Planning becomes a status meeting instead of a commitment. The release train has a name but no engine. The framework isn't the problem — the operating discipline behind it is.
I've embedded SAFe inside enterprise organizations as a SAFe Advanced Certified Scrum Master (ACSM) and PMP, leading Agile delivery across government modernization and financial-services programs. The difference between a transformation that sticks and one that's quietly abandoned is whether someone holds the cadence when it gets uncomfortable.
What I'm brought in to do
- PI Planning facilitation — preparation, the event itself, and the follow-through cadence that keeps commitments real.
- Agile Release Train (ART) standup — standing up the train, sequencing dependencies, and choreographing delivery across teams.
- RTE coaching — developing the Release Train Engineer and Scrum Masters who carry it after I leave.
- Waterfall-to-Agile transition — the team-of-teams operating model and the culture change that makes the framework stick.
A framework is a map. Delivery is the terrain. I coach the cadence and accountability that turn SAFe from a diagram on the wall into a train that actually moves.
Common questions
Can you run our first PI Planning?
Yes — end to end. Preparation, facilitation of the event, and the cadence that follows so momentum survives after the room clears.
Do you help teams move from waterfall to Agile?
Yes. Most transitions fail on culture and cadence, not framework knowledge. I coach the team-of-teams model that makes the change durable.