ISO 20000 Lead Implementer study materials
ISO 20000 Lead Implementer study resources

ISO 20000 Lead Implementer: Planning of an SMS Implementation Based on ISO/IEC 20000-1

ISO 20000 Lead Implementer · Work through your exam, one topic at a time.

All guide sections

Planning of an SMS Implementation Based on ISO/IEC 20000-1

This domain tests how you move from intent to a workable implementation programme: scoping, baselining, sequencing and resourcing. Questions typically describe a starting position and ask for the best next step.

Building the plan

  1. Secure sponsorship and a mandate. Leadership commitment (5.1) is a requirement, not a nicety; without a sponsor who allocates resources the programme stalls.
  2. Define the scope early. Which services, which organizational units, which suppliers, which locations. Scope drives effort, cost and the certificate.
  3. Perform a gap analysis against every requirement of ISO/IEC 20000-1, recording current state, evidence and gap. This baseline is what later proves improvement.
  4. Assess risk and build the business case, including benefits, cost, effort and dependencies on other management systems (ISO 9001, ISO/IEC 27001) so documentation can be integrated rather than duplicated.
  5. Plan the phases with milestones, owners, resources, budget, training and communication. ISO/IEC 20000-5 frames this as Plan (establish the SMS), Do (implement and operate), Check (monitor and review), Act (maintain and improve).
  6. Assign process owners and schedule quick wins to build credibility while slower processes mature.
  7. Plan the feedback loop: measurement, internal audit and management review must be scheduled before any certification audit.

Worked example

A gap analysis shows incident and request management are strong, availability is measured but continuity plans have never been tested, and there is no service catalogue. Reasoning: the plan should sequence the service catalogue first (it underpins SLAs and reporting), then continuity testing once scope is fixed, rather than starting with the weakest technical area, because catalogue and scope unblock the most other requirements.

Traps

Starting with tool procurement; letting scope creep to "all IT"; skipping the baseline so improvement cannot be demonstrated; planning to certification date before planning internal audit and management review; ignoring culture and communication.