The Agile Service Management Journey and Organizational Readiness
The Agile Service Management Journey and Organizational Readiness
This domain tests whether you can sequence an Agile Service Management adoption realistically and evidence readiness rather than assert it.
The journey is staged, not switched
Adoption moves through recognisable stages: build the case and vision, baseline the current state, run a bounded pilot, expand by value stream or team, then embed and continuously improve. Each stage needs its own exit evidence, and the controls and metrics must change with it - a pilot that succeeds but leaves the old approval model untouched has not proved anything transferable.
Change models the exam expects
- Kotter: urgency, coalition, vision, communication, removing obstacles, short-term wins, consolidation, anchoring.
- ADKAR: awareness, desire, knowledge, ability, reinforcement - a person-level model that explains why training alone fails when desire is absent.
- Lewin and Satir: unfreeze, change, refreeze; the Satir curve predicts a performance dip after a foreign element is introduced, so a plan assuming immediate improvement is unrealistic.
- Shu-Ha-Ri: follow the rules, then adapt, then transcend - useful for sequencing training, coaching and empowerment.
Readiness dimensions
Assess leadership sponsorship, culture (safety to raise problems, tolerance of experiment), skills, governance fit, tooling, measurement capability and stakeholder appetite. Gather evidence, not opinions: interviews, value stream workshops, baseline lead time, change failure rate, staff survey. Choose a pilot for high pain, low blast radius, a willing team and measurable outcomes - not for visibility alone.
Worked example
Two candidates: a payments platform team facing a regulatory freeze with a 30% change failure rate, and a low-risk internal reporting team with an engaged manager and 200 changes a quarter. Reasoning: payments offers high value but almost no tolerance for experimentation during a freeze, so early failures there would discredit the approach. The reporting team gives a safe failure domain, fast feedback and enough volume to baseline lead time and failure rate properly. Start there; run payments as a second wave once the model and its evidence exist.
Traps
Starting with tooling; running a big-bang rollout; treating readiness as a questionnaire score rather than evidence; ignoring middle managers who control capacity and incentives; declaring success at the end of a pilot without changing any control or metric.