Description

This curriculum spans the design and coordination of ITSM practices across governance, service delivery, and improvement functions, comparable in scope to a multi-phase internal capability program that aligns service management with enterprise architecture, risk, and DevOps integration.

Module 1: Defining ITSM Governance Frameworks

Selecting between ITIL 4, COBIT, and ISO/IEC 20000 based on organizational compliance requirements and audit frequency.
Establishing a governance board with representation from IT, legal, and business units to approve service lifecycle changes.
Mapping service ownership to business units to ensure accountability for SLAs and service performance.
Integrating risk management practices into service strategy decisions, including third-party vendor dependencies.
Documenting escalation paths for service disruptions that align with organizational hierarchy and incident severity.
Defining thresholds for service retirement based on usage metrics, cost of maintenance, and technology obsolescence.
Aligning service portfolio management with enterprise architecture review cycles to prevent redundancy.
Implementing version control for policies and procedures to support audit trails and change tracking.

Module 2: Service Portfolio and Catalog Design

Classifying services as customer-facing, internal, or shared to determine catalog visibility and access controls.
Standardizing service request templates to reduce fulfillment time and improve consistency.
Deciding whether to include shadow IT services in the catalog for governance or risk mitigation.
Integrating service catalog data with CMDB to ensure accurate configuration dependencies.
Defining service retirement workflows, including notification schedules and data migration plans.
Implementing role-based access to catalog entries based on job function and data sensitivity.
Establishing naming conventions and metadata standards for service discovery and reporting.
Conducting quarterly catalog reviews with business stakeholders to validate relevance and usage.

Module 3: Incident and Problem Management Integration

Configuring incident categorization schemes that support root cause analysis and trend reporting.
Defining criteria for problem record creation, including recurrence thresholds and impact duration.
Integrating monitoring tools with the incident management system using event APIs and correlation rules.
Implementing major incident management playbooks with predefined communication templates and war room procedures.
Setting up automated bridging between incident and change records for emergency fixes.
Establishing feedback loops from problem management to change advisory boards for known error updates.
Measuring mean time to acknowledge (MTTA) and resolve (MTTR) across support tiers to identify bottlenecks.
Enforcing incident closure validation, including user confirmation and knowledge article linkage.

Module 4: Change Enablement and Risk Assessment

Classifying changes as standard, normal, or emergency based on impact, complexity, and rollback feasibility.
Designing automated approval workflows for low-risk standard changes using predefined criteria.
Implementing change windows aligned with business operations to minimize service disruption.
Requiring risk assessment templates for normal changes, including backout plans and stakeholder impact.
Integrating change records with deployment pipelines in CI/CD environments for auditability.
Conducting post-implementation reviews for failed or disruptive changes to update risk models.
Managing CAB membership rotation to include application owners and infrastructure leads on a rotating basis.
Enforcing change freeze periods during critical business cycles, with documented exceptions and approvals.

Module 5: Configuration Management Database (CMDB) Strategy

Selecting authoritative data sources for CIs (e.g., SCCM, AWS Config, ServiceNow) and defining reconciliation rules.
Defining CI ownership and update responsibilities to maintain data accuracy across teams.
Implementing CI lifecycle states (e.g., planned, live, decommissioned) to support change and incident impact analysis.
Establishing data validation rules and automated health checks for CI completeness and relationships.
Integrating discovery tools with the CMDB while managing network scanning permissions and performance impact.
Defining relationship types (e.g., runs on, depends on) to enable accurate impact visualization.
Managing CMDB scope to exclude low-value CIs that increase maintenance overhead without operational benefit.
Using CI data to generate compliance reports for software licensing and security audits.

Module 6: Service Level Management and Reporting

Negotiating SLA terms with business units, including measurable metrics, exclusions, and penalty clauses.
Defining OLAs with internal teams to support end-to-end SLA achievement.
Implementing real-time SLA dashboards with breach prediction alerts based on current performance trends.
Setting up automated SLA reporting cycles for executive review and service improvement planning.
Adjusting SLA targets based on seasonal demand, system upgrades, or contractual changes.
Linking SLA performance to vendor management contracts and service credits.
Using SLA breach data to trigger service improvement initiatives and root cause analysis.
Archiving expired SLAs and maintaining historical data for trend analysis and legal compliance.

Module 7: Knowledge and Self-Service Enablement

Defining knowledge article ownership and review cycles to ensure accuracy and relevance.
Implementing article approval workflows that balance speed of publication with quality control.
Integrating knowledge base with service request forms to suggest solutions during submission.
Using search analytics to identify knowledge gaps and frequently failed queries.
Structuring articles with consistent templates for troubleshooting, how-to guides, and known errors.
Enabling user ratings and feedback on articles to prioritize updates and identify inaccuracies.
Restricting access to sensitive knowledge articles based on user roles and data classification.
Automating article retirement based on age, inaccuracy flags, or service deprecation.

Module 8: Continuous Service Improvement (CSI)

Selecting key performance indicators (KPIs) aligned with business outcomes, not just IT efficiency.
Conducting service reviews using balanced scorecards that include cost, quality, and user satisfaction.
Using customer satisfaction (CSAT) surveys with targeted questions to identify service pain points.
Applying root cause analysis techniques (e.g., 5 Whys, Fishbone) to recurring service issues.
Prioritizing improvement initiatives using cost-benefit analysis and risk impact scoring.
Integrating improvement backlogs with project management tools to track implementation progress.
Establishing baseline metrics before implementing changes to measure improvement effectiveness.
Documenting lessons learned from failed initiatives to refine the CSI methodology.

Module 9: Integrating ITSM with DevOps and Agile Practices

Aligning service request workflows with sprint planning to manage user-driven feature requests.
Integrating incident data into sprint retrospectives to prioritize technical debt and reliability work.
Mapping change management processes to CI/CD pipelines with automated gating for production deployments.
Defining service ownership models for microservices, including on-call responsibilities and escalation paths.
Using service reliability metrics (e.g., error budgets) to inform change advisory board decisions.
Coordinating incident response with development teams during outages involving custom applications.
Implementing feature flag management within the service catalog for controlled rollouts.
Training operations teams on agile ceremonies to improve collaboration with development squads.