Agile Transformation Model
The Agile Transformation Model takes an organisation through the stages of moving from traditional project management to agile ways of working: assessing where you are, planning the shift, running it team by team, and holding the change once the initial push has faded.
Five stages run left to right, carrying the organisation from first assessment to agile habits that hold.
Reach for this when…
- Leadership has mandated 'agile' but nobody has a plan beyond renaming meetings.
- One team is agile and the rest of the organisation still works in the old rhythm around it.
- The transformation stalled after the initial excitement and slid back to old habits.
How to run it
- Assess current ways of working and where the real friction sits.
- Build a transformation plan: sequence, pilot teams, and what success looks like.
- Run the change with pilot teams first, not the whole organisation at once.
- Support leaders and teams through the shift with coaching, not just training.
- Lock in the change: adjust structures, incentives and metrics so it doesn't snap back.
A worked example
Situation. Thandiwe Nkosi led operations transformation at a grocery retail chain in Cape Town, South Africa, where head office had announced an agile rollout across forty stores' supply-chain teams in one go.
Applied. She stopped the big-bang rollout and restarted with the assessment stage done properly: two pilot regions first, with a coach embedded for twelve weeks, before touching the rest.
Result. The two pilot regions cut replenishment lead time by a third and became the reference case the other regions actually wanted to copy, instead of a mandate they resented.
The catch
The model reads as a clean sequence but transformations rarely move in a straight line - teams regress under pressure and the 'lock in' stage is where most efforts quietly die once attention moves elsewhere. It also assumes leadership will change how it measures and rewards people, which is the part most often skipped.
If the incentive structure and the org chart haven't changed by the final stage, the transformation was a training programme wearing agile's name.