Description

This curriculum spans the full lifecycle of IT service delivery, comparable in scope to a multi-workshop organizational transformation program, addressing strategic planning, cross-functional coordination, and operational execution across service management functions.

Module 1: Service Strategy and Portfolio Management

Defining service portfolio boundaries by evaluating which internal capabilities should be formalized as chargeable services versus operational overhead.
Aligning service investment decisions with business unit roadmaps during annual planning cycles, including justifying decommissioning underutilized services.
Establishing service valuation models for internal billing, including cost attribution for shared infrastructure components like identity management and monitoring.
Conducting demand forecasting for new services using historical usage patterns and business growth projections to size required capacity.
Implementing governance for service retirement, including data archival, access revocation, and stakeholder notification protocols.
Resolving conflicts between business units over shared service funding models when usage and benefit distribution are uneven.

Module 2: Service Design and SLA Architecture

Negotiating SLA terms with legal and procurement teams to ensure enforceability while maintaining operational feasibility under peak load.
Designing service-specific KPIs that reflect actual user experience, such as application response time at the client layer, not just server uptime.
Integrating security and compliance requirements into service blueprints, including audit trail retention and access logging standards.
Specifying failover and recovery procedures in service design documents that align with RTO/RPO agreed upon with business owners.
Coordinating cross-functional design reviews involving network, security, and application teams to prevent implementation gaps.
Documenting exception handling processes for SLA breaches, including escalation paths and root cause analysis timelines.

Module 3: Service Transition and Change Control

Classifying changes using risk-based criteria to determine whether CAB review is required or if standard change procedures apply.
Managing emergency change backlogs by scheduling post-implementation reviews to prevent recurrence of unapproved modifications.
Enforcing build integrity through automated configuration validation before promoting changes to production environments.
Coordinating parallel testing windows with business units to validate service functionality without disrupting live operations.
Handling rollback planning for high-risk deployments, including data state restoration and configuration reversion scripts.
Resolving conflicts between development timelines and change advisory board schedules during peak release periods.

Module 4: Incident Management and Major Event Response

Defining incident categorization rules that enable accurate trend analysis without creating excessive classification overhead.
Implementing escalation procedures for major incidents, including notifying executive stakeholders within defined time thresholds.
Integrating monitoring alerts with incident management systems to reduce mean time to acknowledge while minimizing alert fatigue.
Conducting post-incident reviews that focus on process gaps, not individual blame, with documented action items and owners.
Managing incident communication across geographically distributed teams using standardized status update templates.
Balancing automation of incident routing with the need for human judgment in complex, multi-system outages.

Module 5: Problem Management and Root Cause Analysis

Selecting which recurring incidents to escalate to problem records based on business impact and frequency thresholds.
Applying root cause analysis techniques such as fishbone diagrams or 5 Whys in cross-functional workshops with technical teams.
Tracking known error database (KEDB) accuracy by auditing workaround effectiveness and linking to resolved incidents.
Coordinating permanent fix implementation with change management, especially when fixes require third-party vendor involvement.
Measuring problem management ROI by tracking reduction in incident volume after permanent fixes are deployed.
Resolving ownership disputes for problems that span multiple technical domains, such as network, application, and database layers.

Module 6: Service Operation and Request Fulfillment

Designing service request workflows that balance user convenience with compliance, including approval chains for privileged access.
Automating fulfillment of common requests such as password resets and software installations using runbook automation tools.
Managing catalog versioning when updating service offerings to prevent disruption to users with active requests.
Enforcing request prioritization rules that align with business criticality, not just requester seniority.
Integrating service catalog with identity management systems to ensure provisioning reflects current role-based access policies.
Auditing fulfilled requests quarterly to detect policy violations or unauthorized entitlement accumulation.

Module 7: Continual Service Improvement and Performance Measurement

Selecting CSI initiatives based on service performance data, customer feedback, and resource availability trade-offs.
Establishing baseline metrics for services before launching improvement projects to measure actual impact.
Conducting service reviews with business stakeholders using standardized reporting templates focused on SLA adherence and incident trends.
Implementing feedback loops from support teams into design and transition processes to address recurring operational pain points.
Using balanced scorecards to evaluate ITSM performance across dimensions: quality, cost, agility, and user satisfaction.
Managing resistance to process changes by involving frontline staff in improvement workshops and pilot testing.

Module 8: Governance, Compliance, and Audit Readiness

Mapping ITSM processes to regulatory requirements such as SOX, HIPAA, or GDPR for audit evidence collection.
Configuring access controls in the ITSM tool to enforce segregation of duties between incident, change, and problem roles.
Maintaining audit trails for all service management activities, including change approvals and incident updates, for minimum retention periods.
Preparing for internal and external audits by organizing evidence packs for key processes and control points.
Responding to audit findings by implementing corrective actions with verifiable completion dates and validation steps.
Reconciling policy documentation with actual practice during control assessments to avoid compliance gaps due to process drift.