IVI Framework Viewer

Representative POMs are described for Architecture Funding at each level of maturity.

1Initial

• Practice

  Start to fund an architecture approach within specific projects.

  Outcome

  Start of Architecture investments within projects

  Metric

  No meaningful tracking / metrics for architecture funding

2Basic

• Practice

  Fund some capabilities from sources beyond the immediate project, in line with architecture governance.

  Outcome

  Some cross-project investments made, typically in infrastructure e.g. shared storage, virtualization.

  Metric

  % of architecture investment funding requests approved No of architects and spend Spend of FTE's and total spend

3Intermediate

• Practice

  Put funding in place for the enterprise architecture function and architecture management practices. Get separate funding for architecturally significant projects. Get funding approved for a target architecture landscape (in principle for a 3-year vision, with confirmation for the current funding cycle).

  Outcome

  Significant funding of cross-project architectural capabilities, and utilisation efficiently managed e.g. high levels (>70%) of server virtualisation.

  Metric

  % of portfolio spent on architecturally strategic investments # of enterprise domain and solution architects Ratio of spend on architects to spend on IT staff / total IT ecosystem spend

4Advanced

• Practice

  Have a funding mechanisms to support cross-project investments outside of the normal funding criteria, e.g. Use: - A separate architecture investment fund/portfolio. - Have a mark-up on IT services. - Use transaction-pricing, with a price set to fund new capability building or architectural transitions. - Assess business benefits to justify architecture investments.

  Outcome

  Shared capabilities visible to the business e.g. analytical single customer view (based on common data model shared across business unit / segment / product silos). End of life funding implications are transparent and well managed e.g. through quantification of technological debt.

  Metric

  % of IT services which are funded via business benefits % of architecture investment aligned with strategic business priorities

5Optimized

• Practice

  Implement a lifetime TCO model to fund services beyond the lifetime of individual platforms. Start collaborative investments with customers, partners and/or suppliers to build architectural capabilities in support of the business ecosystem (e.g. common data model, electronic marketplace).

  Outcome

  Avoid technological debt from unfunded end-of-life events. Shared capabilities developed which are visible to customers, partners or suppliers e.g. establishment of open industry standard data models for data exchange.

  Metric

  % of IT spending fully or partially funded by customers, partners or suppliers TCO: cost of a service is described in business terms e.g. service cost per business user or business transaction