Guidelines for using this Maturity Model Tool:

Determine the appropriate response for each statement, in the context of your agency's TBM (Technology Business
Each statement has an opt-out response for items that don't pertain to the current TBM implementation. An opt-out r
Click the “Maturity Scorecard” tab to review your results when complete.
Use the difference between the current state and future state scores as an aid in developing a project plan and dete

Reset
Keep this workbook as a 'blank' master and save it under a new name for each time the Maturity Model is taken.

Maturity Tool Tab Criteria

Please use the below criteria to determine the appropriate grading level for each statement on the Maturity Tool tab:
Planned (Scenarios include: the need is identified, the scope is understood, there is a charge statement and sponso
Started (Scenarios include: the effort is funded; the effort is scheduled; A point of contact (POC) or pilot exists; the e
In Progress (Scenarios include: resources are fully engaged in the effort; the effort has transitioned past phase one
Complete (Scenarios include: deliverables in the production environment; processes in place and being used; the e
N/A Opt-out (Scenarios include: does not pertain to or impact the current TBM implementation)

Maturity Scorecard Tab Scale

5. Implemented and Optimized (planned, governed, controlled, integrated, automated)
4. Proactive (managed, metrics available, actionable, focused, mission value)
3. Repeatable and Reproducible (the process is recurring with the same level of accuracy every time it is run)
2. Emerging Discipline (developing processes, improving data)
1. Ad Hoc (unpredictable, poorly controlled, lacking metrics, reactive)

Terms
Maturity Dimensions: TBM maturity is split into six major maturity dimensions (Engagement, Taxonomy, Data, Autom
Current State: Respond based on the current state of your environment, data, and overall TBM program.
Future State: Respond to the same statements based on the goals for your TBM program and expectations of futur
Criteria: The mechanism for evaluating each statement as it relates to your TBM program and its accomplishments
Maturity Scoring Scale: Indicates the maturity level of your TBM program based on Takes the average of all the stat
TBM (Technology Business Management) program.
mplementation. An opt-out response does NOT have any impact on the scoring.

ping a project plan and determining the level of effort.

Maturity Model is taken.

ent on the Maturity Tool tab:

harge statement and sponsor; there is a proposal or SOW; the effort is not yet funded/scheduled)
ct (POC) or pilot exists; the effort has begun but is less than 20% complete; Phase 1 (in a multi-phase effort) is underway)
transitioned past phase one; the effort is >20% & <80% complete; the effort has deliverables in QA or test environments
place and being used; the effort is more than 80% complete; the effort is in its final phase; incremental improvements continue

cy every time it is run)

ent, Taxonomy, Data, Automation, Reporting and Metrics, and Value). Each dimension has a context definition to aid in respond
ll TBM program.
m and expectations of future achievements. The time horizon is not dictated. Set a time horizon in accordance with your TBM p
m and its accomplishments
s the average of all the statement responses for each dimension.
se effort) is underway)
or test environments
tal improvements continue to refine the outcomes; training has occurred and stakeholders are on board)

xt definition to aid in responding to the statements. Each dimension is scored separately.

accordance with your TBM program's resource availability (i.e.., 6, 12, 18 months), planned activities, and initiatives that will imp
s, and initiatives that will impact the TBM program.
 Maturity Dimensions and Criteria Questions
Engagement: We use TBM data to continuously review, assess, and improve IT budgeting, planning, and forecasting.

Engagement: We have a TBM governance process to evaluate IT investment alignment and value to the agency's mission.
Engagement: We effectively leverage TBM metrics (i.e., TCO, performance, risk) to identify IT projects, services, and technolog
support of your mission.

Engagement: Proposed Initiatives go through a strategic review and use TBM methodologies to account for cost and value.

Engagement: The CXO(s)/ACXOs understand the value TBM brings and is a champion/sponsor of your TBM program.

Engagement: There is a TBM partnership between IT, mission, finance, budget, procurement, and HR functions and operations
Engagement: The CIO’s direct reports, as well as service/application owners, understand the value of TBM and support the TB
program.
Engagement: Organizational change management aspects, such as training and opportunities for continued learning, are prov
to service, project, and application owners to develop their understanding of TBM principles.

Also Applies to:

Other stakeholders such as budget, finance, acquisition, HR, etc.

Engagement: TBM principles help service, project, and application owners effectively engage in optimization (cost and proces
efforts that track costs of services, measured by unit cost, volume and quality of service delivered.

Also Applies to:

Other stakeholders such as budget, finance, acquisition, HR, etc.

Engagement: Vendors are partners in implementing TBM and support the agency's value measures and principles.
Engagement: We partner with procurement so SOWs, contracts, and invoices include the language required to ensure contrac
deliverables are in alignment with the TBM framework.
Engagement: A roadmap for the T continuous improvement/evolution of your TBM program exists and is socialized broadly am
stakeholders.

Engagement: Our organization leverages TBM transparency to build trust with the community it serves.

Taxonomy: Our organization has fully aligned IT Portfolio investment budget data to all Cost Pools.

Taxonomy: Our organization has fully aligned IT Portfolio investment budget data to all IT Towers.

Taxonomy: Our organization has fully aligned IT spend/execution to all Cost Pools.

Taxonomy: Our organization has aligned IT spend/execution to all IT Towers.

Taxonomy: Our organization has a comprehensive IT service catalog.

Taxonomy: Our organization has aligned IT costs and consumption to IT services and applications.

Taxonomy: Our organization has identified service owners who track IT cost and can manage their IT service spend.

Taxonomy: Services consumption, (IT resources consumed, i.e., labor, storage, vm, etc.) is modeled to show a fully burdened T

Taxonomy: IT Services consumption (via Business Units) is modeled/allocated to show TCO to clients.
Taxonomy: We know the cost drivers of services and applications and are leading conversations with clients on managing
consumption.

Taxonomy: Our organization provides transparency through showback or chargeback at the service level.

Taxonomy: Our organization can show how IT services relate to business units, drive business capabilities and enable the miss
Taxonomy: TBM metrics and insights, derived from the implementation of the taxonomy, are used to influence behavior and
manage demand.
Data: Cost modeling incorporates the core datasets representing financial (G/L, Budget, HR), operational (Assets, CMDB, Ticke
etc.) and procurement (Vendors, Cloud services etc.).
Data: Data are regularly refreshed on a monthly or quarterly basis using a largely automated workflow for cleansing, enrichm
mapping and allocation rules.

Data: Consumption data is recorded across the IT service portfolio to show how Business Units consume our services.

Data: We either a.) maintain referential integrity and standardized naming conventions across data sets, or b.) have cross-refe
tables in place to provide referential integrity.

NOTE: For example, something called 'Risk Management Initiative' might also be referred to as RMI, Risk Management Project
Mgmt. Initiative. Referential Integrity expects that a consistent naming convention or identifier is used for tagging across all
resources (storage, backup, VM, cloud, labor, etc.)

Data: Cloud resources are tagged to the service, application, or project they support.

Data: Allocation methods for cost pools and towers utilize standardized metadata, such as BOC, PSC, etc.
Data: Cost allocation methods for services and business units have moved from an 'even-spread' to allocations based on othe
attributes in the model (i.e., consumption, utilization, etc.).

Data: Data insights look for IT-related spend outside of the OCIO to identify areas of 'shadow IT' to incorporate into the IT portf

Data: TBM data is used to perform insight hunting (identifying opportunities for improvements thru patterns or trends in the d
Automation: At least 50% of data incorporated into our model is refreshed through an automated process (API, SQL Query, FT
etc.).
Automation: All financial (G/L, budget, HR), operational (assets, CMDB, tickets), and procurement (vendors, cloud services) da
used in the model are automatically updated monthly or quarterly.
Automation: Infrastructure consumption data from VM environments(i.e., storage, cloud, etc.) is updated automatically mont
quarterly.
Automation: Automation and governance keep portfolios of services, applications, and projects updated and integrated with t
TBM model in real-time.
Automation: Cloud service costs are received in an automated fashion and costs are aggregated with other on-prem compute
storage, and labor costs on a per-service/application basis.

Reporting & Metrics: We can provide IT budget execution updates monthly or quarterly.
Reporting & Metrics: We can provide Cost Pool level budget to spend variances monthly (baseline by original budget and quar
reforecast).
Reporting & Metrics: Cost drivers (highest element of cost) are identified across the service and application portfolio and can b
leveraged in value conversations with the business units.

(i.e., More informed value conversations can be had if it is known that the cost of application 'A' is driven by storage and the c
application 'B' is driven by software development/customization.)

Reporting & Metrics: Data, analytics, and insights are used to identify opportunities, define business cases for change, and me
investment execution outcomes.
Reporting & Metrics: Performance measurements are aligned to overall business strategies, goals, and objectives and effective
reflect customer needs.
Reporting & Metrics: A process exists to identify 'shadow IT' so that it can be controlled, reported on, and incorporated into th
portfolio.
Reporting & Metrics: Operational and executive reporting informs decision making and decisions are more strategic due to the
actionable information from TBM metrics.
Reporting & Metrics: Multiple models are used so both O&M spend and DME capital are tracked and amortization (of capital)
used for rates management.

Reporting & Metrics: The insights gained from TBM are used in application rationalization.
Reporting & Metrics: Project funding controls provide the necessary flexibility to deliver IT business products on time and on
budget.
Reporting & Metrics: TBM insights are pushed to the relevant stakeholders automatically for their consideration.

Reporting & Metrics: Advanced analytics (i.e., machine learning, NLP, discovery tools, etc.) are leveraged to find insights and
produce metrics.

Reporting & Metrics: Benchmarking data is used to inform decision-making.

Reporting & Metrics: Data are up to date and readily available so results are defensible and the time it takes to answer ad-hoc
queries on cost, consumption, and other metrics is reduced by 50% or more.

Value: TBM enables the IT organization to understand which services drive the agency business and mission goals and objectiv

Value: Through TBM, the IT organization is recognized as an enabler for the mission of the agency.

Value: The TBM office enables the IT organization to show it has optimized O&M spend year over year.

Value: TBM focuses on the IT organization in executing plans to modernize and further automate the agency.
Value: TBM enhances the ability of the IT organization to participate in strategic discussions with the agency and uses such
involvement as a planning and prioritization tool.
Value: TBM provides the baseline to measure and validate initiatives after launch to determine how well they achieve the orig
stated benefits and ROI.

Examples of Initiatives include: cyber strategy, data center optimization, cloud migration, application rationalization, platform
modernization, IT management automation, business process automation, etc.

Value: TBM has integrated into IT governance (ARB, IRB, etc.).

Value: Aspects of the TBM framework and data are integrated into IT budgeting (PPBE) processes.

Value: Aspects of the TBM framework and data are integrated into IT Acquisition Management processes.
Value: Aspects of the TBM framework and data are integrated into IT demand management and IT portfolio management
processes.

Value: Aspects of the TBM Framework and data are integrated into IT financial management processes.
Value: Through TBM, the IT investment portfolio has been revised to reflect services and to identify DME initiatives that contri
to new or enhanced services.

Value: TBM is acknowledged as helping the C-suite grow and change the business.

Value: Through TBM, our customers/stakeholders (consumers of IT) understand the value IT brings to the agency.
Value: TBM's transparency provides the details our customers/stakeholders need to understand the relationship between the
decisions/needs and the impact they have on IT costs (people, technology, and time).
Value: TBM principles around cost transparency, application rationalization and insights help identify risk and provide actionab
mitigation.
TBM Maturi
Current State Future State Comments
N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

N/A Opt-out N/A Opt-out

Current State Date Future State Date
Enter Today's Date Enter Future State Date
Scores averaged and scaled based on number of questions answered in each dimension
Current State Future State Future State
Maturity Category Current State Score Description Score Description
Engagement 0.0 Ad Hoc 0.0 Ad Hoc
Taxonomy 0.0 Ad Hoc 0.0 Ad Hoc
Data 0.0 Ad Hoc 0.0 Ad Hoc
Automation 0.0 Ad Hoc 0.0 Ad Hoc
Reporting 0.0 Ad Hoc 0.0 Ad Hoc
Value 0.0 Ad Hoc 0.0 Ad Hoc

Overall Score 0.0 Ad Hoc

Current State Date Future State Date

Enter Today's Date Enter Future State Date

 TBM Maturity Model
Engagement
1.0

Value Taxonomy
0.5

average(sum (question response score*weight))/qty question response levels *

0.0

Reporting Data

Automation
Current State Score Future State Score
te Score
Data
Taxonomy
Operational Efficiency/Effectiveness
 1 Planned
2 Started
3 In Progress
4 Complete
N/A Opt-out