Description

This curriculum spans the full lifecycle of IT portfolio management, equivalent in scope to a multi-workshop advisory engagement with an enterprise architecture team, covering governance, classification, financial attribution, and risk management across decentralized organizations.

Module 1: Defining the Scope and Boundaries of the IT Portfolio

Determine which services, projects, and assets fall under the IT portfolio versus business unit–owned technology by mapping ownership and funding sources across the enterprise.
Establish criteria for including shadow IT systems in the portfolio based on risk exposure, integration dependencies, and compliance requirements.
Negotiate with business units to include cross-functional digital products in the portfolio despite decentralized development teams.
Decide whether to incorporate decommissioned services in historical views of the portfolio for audit and knowledge retention purposes.
Define thresholds for service materiality—such as cost, user count, or business impact—below which services are grouped into aggregates rather than tracked individually.
Resolve conflicts between centralized governance and devolved innovation by documenting decision rights for service inclusion and exclusion.

Module 2: Classifying Services and Establishing Portfolio Taxonomies

Select a classification model (e.g., core/enhanced/supporting, customer-facing/internal) that aligns with enterprise architecture principles and supports capacity planning.
Implement tagging standards for services based on business domain, technology stack, and service model (e.g., SaaS, PaaS, on-prem) to enable portfolio slicing and reporting.
Reconcile inconsistent naming conventions across departments by enforcing a canonical naming policy and managing aliases in the service catalog.
Address duplication in service definitions caused by overlapping capabilities in different business units or legacy systems.
Integrate service classification with existing CMDB schemas without introducing excessive complexity or data maintenance overhead.
Update classification rules in response to mergers, divestitures, or shifts in business strategy that redefine service relevance.

Module 3: Governance Frameworks and Decision Rights

Design a governance board structure with representation from IT, finance, security, and business units to review service lifecycle transitions.
Define escalation paths for disputes over service retirement, funding reallocation, or ownership changes within the portfolio.
Implement stage-gate reviews for new services entering the portfolio, requiring business case, risk assessment, and integration impact analysis.
Balance agility and control by setting thresholds for delegated approval of low-risk services versus mandatory executive review for strategic systems.
Document and audit decision logs to support regulatory compliance and post-implementation reviews.
Align portfolio governance with enterprise risk management by integrating findings from internal audits and external assessments.

Module 4: Financial Management and Cost Attribution

Allocate shared infrastructure costs (e.g., network, identity management) to services using usage-based, headcount-based, or revenue-based models.
Implement chargeback or showback mechanisms that reflect actual consumption while avoiding administrative overhead.
Track and report on total cost of ownership (TCO) per service, including licensing, support, internal labor, and cloud consumption.
Reconcile discrepancies between accounting system data and operational usage metrics when attributing cloud costs to services.
Establish cost review cycles to identify underutilized or over-resourced services for optimization or rationalization.
Negotiate with finance to align IT portfolio cost models with general ledger categories and capitalization policies.

Module 5: Service Lifecycle Management and Portfolio Rationalization

Define clear criteria for moving services between lifecycle stages (e.g., from active to deprecated) based on business value, usage trends, and technical debt.
Develop communication and transition plans for retiring legacy services, including data migration, user retraining, and dependency remediation.
Conduct periodic portfolio health assessments to identify redundant, overlapping, or obsolete services.
Manage technical debt accumulation by linking service lifecycle status to modernization funding decisions.
Coordinate with application owners to delay retirement when business units rely on undocumented integrations or lack viable alternatives.
Track rationalization outcomes to measure reductions in operational complexity and cost savings.

Module 6: Integration with Enterprise Architecture and Strategic Planning

Map current-state services to business capabilities to identify coverage gaps and redundancies in the portfolio.
Use the IT portfolio as a foundation for modeling future-state architecture by identifying target service patterns and deprecation roadmaps.
Align service investment plans with multi-year technology roadmaps and business transformation initiatives.
Integrate portfolio data into enterprise architecture tools to enable impact analysis for proposed changes or decommissioning.
Facilitate scenario modeling for mergers, acquisitions, or divestitures by simulating portfolio changes and cost implications.
Ensure consistency between service portfolio views and strategic planning documents used by CIOs and CFOs in budget cycles.

Module 7: Performance Monitoring, Reporting, and Continuous Improvement

Define KPIs for portfolio health, such as percentage of services under active support, cost per service, and lifecycle distribution.
Develop dashboards that provide role-based views of portfolio performance for executives, service owners, and operations teams.
Automate data collection from CMDB, financial systems, and monitoring tools to reduce manual reporting errors and latency.
Implement feedback loops from incident management and change control to assess the operational stability of services in the portfolio.
Conduct quarterly portfolio reviews to validate data accuracy, update classifications, and adjust governance rules.
Use benchmarking data from industry peers to evaluate portfolio efficiency and prioritize improvement initiatives.

Module 8: Risk, Compliance, and Dependency Management

Identify single points of failure by mapping service dependencies across infrastructure, third parties, and personnel.
Assess compliance exposure by linking services to regulatory requirements (e.g., GDPR, HIPAA) and validating control coverage.
Track end-of-life and end-of-support dates for underlying technologies and enforce remediation plans for affected services.
Integrate vulnerability management data into the portfolio to prioritize patching and modernization based on service criticality.
Document data residency and processing locations for services to support cross-border data transfer compliance.
Perform dependency impact analysis before decommissioning or upgrading services to prevent unintended business disruption.