Description

This curriculum spans the technical, financial, and governance dimensions of IT investment analysis with a depth comparable to a multi-workshop advisory engagement, addressing the same complexities found in enterprise service portfolio programs that integrate finance, architecture, and business strategy.

Module 1: Defining Service Portfolio Boundaries and Scope

Determine which IT services to include in the portfolio based on business unit dependencies and funding ownership, excluding shadow IT systems without formal SLAs.
Establish criteria for categorizing services as strategic, transitional, or retired, requiring alignment with enterprise architecture review boards.
Resolve conflicts between service owners over shared components, such as middleware platforms supporting multiple applications.
Decide whether to include project-based initiatives in the portfolio during pre-production phases, balancing visibility against premature commitment.
Negotiate inclusion thresholds for cloud-based SaaS tools managed outside central IT, considering data residency and integration requirements.
Implement version control for service definitions when business units rebrand or restructure, ensuring historical continuity in investment tracking.

Module 2: Aligning IT Investment Categories with Business Capabilities

Map each service to a business capability model, requiring collaboration with business process owners to validate functional coverage.
Classify spending into run, grow, and transform categories based on service lifecycle stage, influencing budget allocation debates with CFOs.
Reconcile discrepancies between IT’s service view and finance’s cost center model when attributing investments to business units.
Adjust investment classifications quarterly in response to shifting strategic priorities, such as digital transformation accelerations.
Document justification for treating cybersecurity upgrades as transformational versus operational, affecting capitalization treatment.
Address inconsistencies in how regional subsidiaries define “new capability” versus “enhancement” for global services.

Module 3: Cost Attribution and Chargeback Models

Select between direct allocation, driver-based distribution, and activity-based costing for shared infrastructure services.
Define usage metrics for chargeback (e.g., API calls, compute hours) that reflect actual consumption without excessive monitoring overhead.
Negotiate fixed versus variable cost recovery models with business units resistant to fluctuating IT charges.
Implement cost transparency reports that expose underlying assumptions, reducing disputes during budget reviews.
Handle disputes over allocation of legacy system maintenance costs when original business sponsors have been restructured.
Decide whether to include internal development effort in service cost models using loaded labor rates or market benchmarks.

Module 4: Capitalization and Accounting Compliance

Determine which software development phases qualify for capitalization under IFRS or GAAP, requiring engagement with external auditors.
Track time and effort for capitalizable activities using integrated project management and HR systems, ensuring audit trail integrity.
Establish cutoff dates for moving projects from capitalized development to operational status, impacting depreciation schedules.
Manage the write-down of capitalized projects abandoned mid-development, requiring CFO and controller approvals.
Classify cloud subscription costs as operating or capital expenditures based on contractual terms and usage duration.
Reconcile IT portfolio records with general ledger accounts monthly to prevent misstatements in financial reporting.

Module 5: Portfolio Prioritization and Demand Management

Implement a scoring model for investment requests using criteria such as risk reduction, revenue enablement, and regulatory compliance.
Enforce capacity constraints in service delivery teams when prioritizing initiatives, preventing overcommitment.
Facilitate prioritization workshops with business stakeholders, mediating conflicts between competing unit demands.
Define thresholds for deferring or canceling low-priority services during budget shortfalls, with formal change control.
Track opportunity cost of approved projects by quantifying delayed alternatives in portfolio reviews.
Integrate demand intake with enterprise risk management to deprioritize initiatives introducing unacceptable compliance exposure.

Module 6: Performance Measurement and Value Realization

Select KPIs for each service that reflect business outcomes (e.g., order fulfillment time) rather than technical metrics alone.
Establish baseline performance before investment implementation to enable credible post-deployment comparisons.
Assign accountability for benefit realization to business owners, requiring formal sign-off at milestone reviews.
Adjust performance targets mid-cycle due to external factors like market shifts or regulatory changes.
Handle cases where expected benefits are realized but attributed to other concurrent initiatives, complicating ROI claims.
Decide whether to retire services with declining usage despite political support from legacy stakeholders.

Module 7: Governance and Cross-Functional Integration

Define escalation paths for investment disputes between IT and business units, specifying decision rights in governance charters.
Integrate service portfolio reviews with enterprise architecture governance to prevent redundant or conflicting investments.
Align investment cycles with corporate budgeting timelines, requiring early forecasting before fiscal year starts.
Coordinate with procurement to influence vendor contract terms based on portfolio-wide usage patterns and renewal schedules.
Ensure data consistency between portfolio management tools and ERP, PPM, and CMDB systems through automated interfaces.
Manage executive turnover by institutionalizing decision frameworks rather than relying on individual sponsor advocacy.

Module 8: Scenario Planning and Investment Resilience

Model portfolio impacts of headcount reductions on service delivery capacity, adjusting investment plans accordingly.
Simulate cost implications of transitioning services to cloud models, including exit fees and re-architecting effort.
Assess exposure to single points of failure by identifying services dependent on specific vendors or skill sets.
Develop contingency funding pools for critical services, requiring pre-approved thresholds for rapid deployment.
Evaluate investment sensitivity to currency fluctuations for globally delivered services with offshore components.
Stress-test portfolio resilience under regulatory changes, such as new data localization laws affecting service hosting.