ISO/IEC 20000 Introduction — Lesson 3: Service Delivery, Relationships, Suppliers, Incidents, Problems, and Continuity

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping service delivery, relationships, suppliers, incidents, problems, and continuity.
• Apply a practical workflow and create a reviewable service operations responsibility matrix.
• Evaluate the exception where incident and problem records are closed with conflicting causes and determine proportionate follow-up.

Detailed Topics

• Service Delivery applied to the course scenario and expected evidence.
• Relationships applied to the course scenario and expected evidence.
• Suppliers applied to the course scenario and expected evidence.
• Incidents applied to the course scenario and expected evidence.
• Problems applied to the course scenario and expected evidence.
• and Continuity 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 operations responsibility matrix, and tests the condition where incident and problem records are closed with conflicting causes.

Hands-On Exercise

Complete a controlled exercise covering Service Delivery, Relationships, Suppliers, Incidents, Problems, and Continuity. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in service operations responsibility matrix.

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 operations responsibility matrix 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 “incident and problem records are closed with conflicting causes” 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 operations responsibility matrix 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 Delivery, Relationships, Suppliers, Incidents, Problems, and Continuity, explain the reasoning used, and defend the result through service operations responsibility matrix.