Skip to main content
ITSM in ITSM

ITSM in ITSM

$249.00
How you learn:
Self-paced • Lifetime updates
Toolkit Included:
Includes a practical, ready-to-use toolkit containing implementation templates, worksheets, checklists, and decision-support materials used to accelerate real-world application and reduce setup time.
Who trusts this:
Trusted by professionals in 160+ countries
Your guarantee:
30-day money-back guarantee — no questions asked
When you get access:
Course access is prepared after purchase and delivered via email
Adding to cart… The item has been added

This curriculum spans the operational intricacies of managing ITSM across multi-vendor ecosystems, toolchain integrations, and hybrid development-operations workflows, reflecting the scope and decision complexity found in multi-workshop organizational change programs.

Module 1: Defining ITSM Governance in a Multi-Vendor Environment

  • Selecting a governance model (centralized, federated, decentralized) based on organizational structure and vendor contract boundaries.
  • Establishing service ownership across business units when IT services are delivered by third-party providers with conflicting SLAs.
  • Defining escalation paths for incidents that span internal teams and external vendors without duplicating effort.
  • Implementing a change advisory board (CAB) that includes external vendor representatives while maintaining internal control over risk decisions.
  • Documenting service relationships in a service model that reflects shared responsibilities across internal and external entities.
  • Enforcing compliance with internal policies when external vendors use their own ITSM tools and processes.

Module 2: Toolchain Integration and Data Consistency Across Platforms

  • Mapping incident fields between a legacy ticketing system and a modern ITSM platform during phased migration.
  • Designing bi-directional synchronization of configuration items (CIs) between CMDB and external monitoring tools with differing data models.
  • Resolving conflicting configuration data when discovery tools report discrepancies across network, cloud, and on-premise environments.
  • Implementing API rate limiting and error handling for integrations between ITSM and DevOps pipelines.
  • Establishing data ownership rules for CI updates when multiple teams (network, security, cloud) maintain overlapping components.
  • Creating audit trails for automated changes initiated from external orchestration tools to maintain change history integrity.

Module 3: Incident Management at Scale with Major Incident Protocols

  • Activating major incident procedures when monitoring alerts exceed predefined thresholds but no user-reported outage exists.
  • Assigning incident commanders during cross-functional outages where technical leads dispute ownership.
  • Documenting war room communications in real time without disrupting resolution efforts.
  • Deciding whether to defer non-critical changes during an ongoing major incident based on risk exposure.
  • Integrating post-mortem findings into known error databases without creating redundant or conflicting workarounds.
  • Managing stakeholder communication during prolonged incidents when technical teams resist sharing unverified root cause hypotheses.

Module 4: Change Enablement and Risk-Based Approval Workflows

  • Classifying a change as standard, normal, or emergency when automated deployment tools bypass traditional change windows.
  • Granting pre-approved change status to CI/CD pipeline updates while maintaining audit compliance.
  • Requiring CAB review for cloud infrastructure changes that affect network security posture, even if automated.
  • Handling rollback decisions when a failed change impacts production but the backup system is also out of sync.
  • Logging undocumented emergency changes after resolution and enforcing retrospective review without penalizing responders.
  • Aligning change windows with business-critical batch processing schedules in hybrid on-premise/cloud environments.

Module 5: Configuration Management and CMDB Accuracy Maintenance

  • Reconciling CI ownership when a server hosts multiple applications managed by different teams.
  • Handling discovery tool conflicts when multiple sources report different IP addresses for the same virtual machine.
  • Defining CI granularity for cloud-native services (e.g., containers, serverless functions) that are ephemeral by design.
  • Validating CI relationships when application dependencies shift dynamically in microservices architectures.
  • Managing CMDB updates during data center decommissioning when some systems are offline and unverifiable.
  • Enforcing manual review of CI changes for high-risk systems even when automated discovery is available.

Module 6: Service Level Management with Realistic KPI Design

  • Negotiating SLA terms for cloud services where uptime guarantees are limited by provider contracts.
  • Excluding planned maintenance windows from SLA calculations without enabling abuse of the exclusion policy.
  • Tracking end-to-end service availability when user experience depends on external APIs beyond internal control.
  • Adjusting OLAs between support tiers when incident resolution bottlenecks shift due to staffing changes.
  • Reporting SLA breaches to leadership when root cause is vendor-related but internal teams are contractually accountable.
  • Defining meaningful KPIs for self-service portal usage that reflect actual user adoption, not just ticket deflection.

Module 7: Continual Improvement Through Operational Feedback Loops

  • Prioritizing improvement initiatives when multiple teams report conflicting pain points in change management.
  • Using incident trend data to justify investment in automation, despite resistance from teams fearing role reduction.
  • Conducting process reviews after organizational restructuring that merged previously siloed IT functions.
  • Implementing feedback mechanisms for service request users when fulfillment is handled by offshore teams.
  • Measuring the impact of knowledge base improvements on first-call resolution rates across support tiers.
  • Aligning continual improvement cycles with budget planning periods to secure funding for process tooling upgrades.

Module 8: Integrating ITSM with Agile and DevOps Practices

  • Defining handoff points between DevOps teams and service operations for production incident ownership.
  • Adapting change management processes to support frequent releases without introducing deployment bottlenecks.
  • Embedding service validation steps into CI/CD pipelines without slowing down development velocity.
  • Ensuring post-deployment monitoring alerts are routed to both operations and development teams during initial stabilization.
  • Mapping user stories to service requests when new features require operational support documentation.
  • Coordinating incident retrospectives between DevOps and ITSM teams when outages originate in application code.
!