This work is licensed under CC BY 4.0 - Read how use or adaptation requires attribution
FinOps X 2023, San Diego June 27-30 - Early Bird Registration

Intersection of FinOps & TBM

Related Domains

Definition

A definition for this Capability. the objective here is to capture the “What” (**not** the “How”) for this Capability

 

Maturity Assessment

description of the characteristics of each maturity level (Crawl, Walk, Run) for this Capability in the context of the organization’s FinOps practice

 

Functional Activity

written for each persona responsible for the functional activity and processes encapsulated by his Capability. each one should be associated generally to one of the FinOps Phases (Inform, Optimize, Operate). for example:

As a [FinOps Persona], I will [functional activity] so that [desired outcome] is achieved.

As a FinOps Practitioner, I will…

*

As an Engineering Manager, I will…

*

As a Finance/Procurement Manager, I will…

*

As a Business/Product Manager, I will…

*

 

Measure(s) of Success & KPI

Measures of success are represented in the context of cloud costs and may include one or more key performance indicators ( KPI ), describe objectives with key results ( OKR ), and declare thresholds defining outliers or acceptable variance from forecasted trends.

at least one measure of success; should be described in a context of cost; this could be an efficiency KPI or an agreed upon threshold or target.
for example:

  • idle resource costs will not exceed 3% of total monthly cloud spend
  • anomaly costs will not exceed $150/month

 

Inputs

the information used that contributes to the measure(s) of success listed above; information here may include specific datasources, reports or any relevant input

 

Get Involved

Get involved and contribute to the community by sharing your real world experiences related to this Capability in the form of a story or providing a playbook for how you have implemented best practices in your organization. Your real world experiences can be provided in the context of:

  • one or more cloud providers
  • the types of cloud services used (compute, storage, database, etc…)
  • describe a combination of tooling, platform or vendor, and processes including KPIs
  • the industry the organization belongs to
  • the complexity of the organization (global enterprise, start-up, etc…)
  • the [FinOps personas](https://www.finops.org/framework/personas/) involved / organizational roles

Join the conversation about this Capability in Slack . You can submit stories, how-tos and suggest improvements using one of the options for contributing here.

Related Projects


Intersection of FinOps & TBM
FinOps & TBM: Navigating Co-Existing Disciplines