ISO/IEC 20000 Introduction — Lesson 2: Service Planning, Design, Transition, Change, Release, and Configuration

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping service planning, design, transition, change, release, and configuration.
• Apply a practical workflow and create a reviewable service transition control checklist.
• Evaluate the exception where emergency changes bypass configuration updates and determine proportionate follow-up.

Detailed Topics

• Service Planning applied to the course scenario and expected evidence.
• Design applied to the course scenario and expected evidence.
• Transition applied to the course scenario and expected evidence.
• Change applied to the course scenario and expected evidence.
• Release applied to the course scenario and expected evidence.
• and Configuration applied to the course scenario and expected evidence.

Instructor Demonstration

The instructor traces a case involving an IT service provider aligning support, change, supplier, availability, and customer reporting practices. The demonstration links decisions to objective evidence, records the result in service transition control checklist, and tests the condition where emergency changes bypass configuration updates.

Hands-On Exercise

Complete a controlled exercise covering Service Planning, Design, Transition, Change, Release, and Configuration. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in service transition control checklist.

1. Define the objective, boundaries, stakeholders, criteria, and expected work product.
2. Perform the activity while recording assumptions, observations, evidence, and decisions.
3. Test normal operation, the exception, and an escalation or follow-up condition.
4. Document conclusions, owners, deadlines, verification methods, and review triggers.

Scenario Analysis

• Identify the requirement or control with the strongest influence on the scenario outcome.
• Compare two defensible responses and explain their risk, operational, and evidence trade-offs.
• Decide how the service transition control checklist should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Start where expected practice and observed evidence first diverge. Separate a missing record from an ineffective process, distinguish unclear ownership from a control failure, and treat “emergency changes bypass configuration updates” as a hypothesis until tested against the applicable criteria and intended outcome.

Validation Checklist

• Scope, roles, criteria, stakeholders, dependencies, and intended outcomes are explicit.
• The service transition control checklist connects conclusions to objective, reviewable support.
• Normal operation, the stated exception, escalation, and follow-up were evaluated.
• Owners, due dates, verification methods, review triggers, and improvement actions are clear.

Lesson Outcome

Learners can apply Service Planning, Design, Transition, Change, Release, and Configuration, explain the reasoning used, and defend the result through service transition control checklist.