FinOps Scopes

A FinOps Scope is a segment of technology-related spending to which FinOps Practitioners apply FinOps concepts.

FinOps Scopes enable practitioners to construct the context needed to frame conversations and expectations about which people (Personas), activities (Capabilities), and outcomes (Domains) are in-scope for the FinOps practice. We can visualize creating a FinOps Scope by navigating the Framework poster from the top-down.

An organization’s technology strategy and business strategy will inform how a FinOps Capability like Data Ingestion, Allocation, or Forecasting is applied to – for example – a segment of Data Center spending. Some FinOps activities may have very different inputs, KPIs, or measures of success for these other segments of spending than when used by a FinOps team for public cloud.

For any area of IT investment, even including public cloud, a FinOps practice may only need to focus on a specific segment of usage – like a hybrid Kubernetes deployment across public cloud and on-premises in an organization’s data center – resulting in the creation of a FinOps Scope within the FinOps practice just for this segment of spending.

A FinOps practice will ultimately define multiple FinOps Scopes as part of the practice profile.  Each Scope may have different people, processes, and technologies involved. The inclusion or exclusion of FinOps Framework elements when constructing a FinOps Scope should reflect your organization’s technology strategy, business strategy, and FinOps Maturity.

Scopes are driven by the business & technology strategy

• Organizations can determine their own custom FinOps Scope(s) based on the mix of technologies and spend that is important to their business
• Framework Capabilities can be prioritized or excluded by Scope based on business objectives
• FinOps Personas can be engaged or excluded as appropriate for each FinOps Scope

Scopes are more than a single type of infrastructure

• A Scope may operate across multiple types of infrastructure (e.g. AI or Licensing)
• There may be multiple Scopes within a single type of spend (e.g. Public Cloud)
• Unique KPIs and thresholds for metrics may be associated with a Capability in a Scope, even if that Capability is included in other Scopes

Scopes determine which Personas, Domains, and Capabilities are Engaged

Elements of the FinOps Framework – such as Personas, Domains, and Capabilities – act as foundational building blocks for your FinOps Scopes. Selection or exclusion of these elements should reflect your organization’s FinOps Maturity, business priorities, and situational context. Practitioners can then apply these Scopes to structure their FinOps activities, define ownership boundaries, and align teams around measurable outcomes. As your practice evolves, the Framework elements included or excluded will change. Scopes provide a construct to build the context to focus improvement efforts and benchmark maturity across different areas of FinOps.

Only create a new scope when you need to

• Just as you should strive to only mature your FinOps practice when doing so creates value, only consider new scopes when critical
• There is an overhead to establishing and tracking many Scopes of practice, so keep it simple when possible
• Many of the Capabilities, Personas and Domains can be practiced in the same manner, with only a few exceptions