Description

This curriculum spans the full lifecycle of service portfolio management, reflecting the iterative, cross-functional coordination required in multi-workshop programs that align IT services with business strategy, governance, and financial oversight.

Module 1: Defining Service Portfolio Scope and Strategic Alignment

Selecting which business units or functions will be included in the initial service portfolio based on regulatory exposure and operational criticality.
Mapping existing IT services to business capabilities to determine alignment with current enterprise architecture standards.
Deciding whether to include shadow IT services in the portfolio inventory based on risk tolerance and governance mandates.
Establishing criteria for service inclusion, such as minimum usage thresholds, financial materiality, or integration dependencies.
Resolving conflicts between business unit autonomy and centralized service governance during portfolio scoping sessions.
Documenting strategic drivers—such as cost consolidation or digital transformation—that justify portfolio boundaries and service categorization.

Module 2: Stakeholder Engagement and Requirements Elicitation

Identifying key decision-makers in business units who control service funding and have authority to approve changes.
Conducting structured interviews with service owners to extract implicit service expectations not captured in formal SLAs.
Facilitating workshops to reconcile conflicting service priorities between departments with shared platforms.
Using service blueprinting techniques to uncover hidden dependencies between business processes and supporting services.
Determining the frequency and format of stakeholder feedback loops to avoid requirements drift post-implementation.
Managing resistance from service owners who perceive portfolio management as an audit or cost-cutting initiative.

Module 3: Service Categorization and Taxonomy Design

Choosing between ITIL-based service types (core, enabling, enhancing) versus business outcome-based classifications.
Defining naming conventions that distinguish between internal platform services and customer-facing offerings.
Assigning ownership for composite services that span multiple technical domains or organizational silos.
Handling legacy services with outdated or ambiguous descriptions that lack clear business purpose statements.
Deciding whether to decompose monolithic services into subcomponents for better cost attribution and management.
Standardizing metadata fields (e.g., criticality, lifecycle stage, compliance tags) across all service records.

Module 4: Demand Management and Service Prioritization

Implementing a scoring model to prioritize new service requests based on business impact, cost, and strategic fit.
Allocating limited service delivery capacity during peak demand periods using formal intake and triage workflows.
Negotiating service deferrals with business units when demand exceeds available resources or budget.
Tracking seasonal or cyclical demand patterns to adjust service capacity planning cycles accordingly.
Enforcing demand governance by requiring business cases for all new or expanded service requests.
Integrating demand data from project portfolios and capital planning systems to forecast future service needs.

Module 5: Financial Modeling and Service Cost Transparency

Selecting cost allocation methodologies (e.g., direct, reciprocal, activity-based) for shared infrastructure services.
Deciding which cost elements (labor, licensing, cloud usage, overhead) to include in service unit pricing models.
Reconciling discrepancies between finance department cost centers and service delivery team expense tracking.
Presenting cost breakdowns to business stakeholders without exposing sensitive vendor contract terms.
Updating cost models when underlying technologies change, such as migration from on-premise to SaaS.
Handling disputes over cost allocations when business units perceive charges as inaccurate or unfair.

Module 6: Service Lifecycle Governance and Change Control

Defining entry and exit criteria for services moving between lifecycle stages (e.g., retired, active, deprecated).
Enforcing retirement timelines for legacy services despite business dependency or user resistance.
Coordinating service changes with application lifecycle management and release planning calendars.
Managing exceptions to governance policies when critical business operations depend on non-compliant services.
Documenting business impact assessments before approving service decommissioning or major modifications.
Integrating service portfolio updates into change advisory board (CAB) decision-making processes.

Module 7: Performance Measurement and Value Reporting

Selecting KPIs that reflect both operational efficiency (e.g., uptime) and business outcomes (e.g., process throughput).
Aligning service performance dashboards with executive reporting cycles and board-level review agendas.
Attributing business incidents to specific services when root causes span multiple technical layers.
Determining the threshold for service performance degradation that triggers formal review or remediation.
Validating self-reported service usage data against system logs or monitoring tools for accuracy.
Producing comparative analyses of service value across divisions to inform consolidation or optimization decisions.

Module 8: Integration with Enterprise Management Frameworks

Synchronizing service portfolio data with enterprise architecture repositories to maintain consistency.
Mapping services to risk and compliance frameworks such as SOX, GDPR, or ISO 27001 for audit readiness.
Embedding service portfolio inputs into annual budgeting and forecasting processes at the business unit level.
Ensuring service descriptions support disaster recovery and business continuity planning requirements.
Linking service records to project management offices (PMOs) to track delivery of new or modified services.
Establishing data governance rules for maintaining service portfolio accuracy across integrated systems.