FinOps Domains & Capabilities Flashcards
Describes the fundamental business outcomes organizations should achieve from the FinOps practice
The Domains of the FinOps Framework describe
The areas of activity required to meet the challenges of the FinOps practice itself. They can be thought of as building blocks that enable, educate, and bridge actionable tasks across FinOps Personas and align technology decisions with business objectives
FinOps Capabilities
enables an organization to better understand what cloud services it is using, what is driving spend, and who is responsible for that spend
Understand Cloud Usage & Cost Domain
What questions do we answer int he Understanding Cost and Usage Domain?
What are we using in the cloud
What are we spending on it
What is the impact of that usage in carbon and other metrics
Who in the org is responsible for that usage and cost
How can all personas access that cost and usage data
Collect, transfer, store, and normalize data from various sources, with a goal of creating a complete, contextual dataset of cloud usage and cost data available for analysis.
Understand Cloud Usage & Cost Domain: Data Ingestion
Involves gathering, transferring, processing, transforming, and correlating various datasets to create a queryable, contextualized repository, at the appropriate level of granularity, accessibility, and completeness to support activities in all of the FinOps Capabilities across all FinOps Personas.
Understand Cloud Usage & Cost Domain: Data Ingestion
Define strategies to assign and share cloud costs using accounts, tags, labels, and other metadata, creating accountability among teams and projects within an organization.
Understand Cloud Usage & Cost Domain: Allocation
Analyze cloud data and create reporting to gain insights into usage and spend patterns, identify opportunities for improvement, and support informed decision-making about cloud resources.
Understand Cloud Usage & Cost Domain: Reporting and Analytics
Defines how cloud costs should be apportioned to those responsible for each component of that cost, whether directly or as a shared element.
In the context of FinOps, this involves using account structures, tags, labels, and derived metadata to identify categories to which we assign costs in a way that provides product managers, engineers, and other personas with a transparent and complete understanding of the cost of cloud resources for which they are responsible.
Requires three primary strategies:
Allocation Strategy - how costs should be mapped to the organization
Tagging Strategy - how cloud usage and resources will be mapped to the defined parts of the organization
Shared Cost Strategy - how each set of shared resources will be allocated to budgets
Understand Cloud Usage & Cost Domain: Allocation
is the ability to gain insights into cloud data by creating reporting mechanisms to serve the needs of the organization’s various persona groups
Understand Cloud Usage & Cost Domain: Reporting and Analytics
Detect, identify, alert and manage unexpected or unforecasted cloud cost and usage irregularities in a timely manner to lower risk in cost-effective cloud operations.
Understand Cloud Usage & Cost Domain: Anomaly Management
connects usage with business value to ensure the value created and the impact of that usage are transparently within expectations
The Quantify Business Value Domain
Estimation and exploration of potential cost and value of workloads if implemented in an organization’s cloud environment in a particular model or models.
Quantify Business Value: Planning and Estimating
Enables organizations to estimate the future costs of a workload or system, considering the variety of services, updates, managed services, and models available in the cloud.
Estimating can be done for any scope, from a single service change to an entire application migrating to the cloud, and is primarily supported by engineering personas with input from FinOps teams, product, finance, or leadership when estimates are particularly important, impactful, or complex.
Planning & Estimating is closely related to Forecasting but focuses on exploratory ideation, producing inputs to cloud cost forecasts, and supporting Capabilities like Architecting for Cloud, Workload Optimization, or Onboarding Workloads.
Quantify Business Value: Planning and Estimating
Creating a model of the anticipated future cost and value of cloud systems leveraging statistical methods, historical spend patterns, planned changes, and related metrics.
Quantify Business Value: Forecasting