Changes made to each section of this site undergo review either during team meetings or meetings with the Technical Advisory Council. During these sessions, commits and Pull Requests are examined and voted on for merging.
FinOps Capabilities embody operational aspects that align with their respective FinOps Domains. These include tasks and processes facilitating the fulfillment of FinOps practice requirements across FinOps Phases. Such activities and processes aim to facilitate enabling, education, knowledge sharing, advocacy, actionable tasks, attainment of business objectives, and enhancement of FinOps maturity.
The FinOps Maturity Model designations aim to pinpoint practitioners’ current operational positions across diverse concepts without passing judgment, empowering them to explore potential investment opportunities. Additionally, they serve as benchmarks to gauge practitioners’ performance as they develop their practices.
Collaborating with the FinOps Personas within your organization is essential for implementing the FinOps Framework. All involved personas stand to gain from grasping the Framework’s operational model. Operating within this framework involves forging alliances during periods of change, establishing a shared lexicon, devising strategies to empower, and creating communication initiatives.
The FinOps Phases consist of Inform, Optimize, and Operate. The Inform phase offers visibility to foster shared accountability. In the Optimize phase, efficiency opportunities are identified and their value determined. The Operate phase establishes and enacts processes aligned with the objectives of technology, finance, and business.
The FinOps Principles serve as a guiding beacon steering our FinOps practice. They are crafted by members of the FinOps Foundation and refined through practical experience. Initially proposed alongside the release of the Cloud FinOps book in September 2019, as a collaborative effort with AWS, these principles now extend across various cloud platforms. Given the dynamic nature of cloud services, subject to quarterly updates, these principles may undergo slight modifications over time as collective experience grows.
On a single platform, cut out unnecessary spending, deliver effective code, and develop profitably.
