| layout | title | description | permalink | page-identifier | framework-capability-title | framework-capability-desc | label | order |
|---|---|---|---|---|---|---|---|---|
capability |
Capability Title Here |
coming soon... |
/framework/capabilities/ |
Capability Title Here |
coming soon... |
1 |
{% include contribute-capabiility.md %}
{% include domains-loop.md %}
definition for this Capability. the objective here is to capture the "What" (not the "How") for this Capability.
description of the characteristics of each maturity level (crawl, walk, run) for this Capability in the context of the organization's FinOps practice.
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.
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
the information used that contributes to the measure(s) of success listed above; information here may include specific datasources, reports or any relevant input
a collection of real world examples, stories and “how to” for this Capability; based on FinOps community member experiences; information here may:
- apply to one or more cloud providers
- include specific types of cloud services used) (compute, storage, database, etc...)
- describe a combination of tooling, platform or vendor
- describe the industry the organization belongs to
- describe the complexity of the organization (global, enterprise, etc…)
- include the FinOps personas involved and any other organizational roles