You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a FinOps practitioner, I need to learn, document, measure, adopt, and automate FinOps capabilities in order to maximize cloud ROI for my organization
🚀 Goal
Flesh out the Implementing FinOps guide to cover all aspects of maturity based on the FinOps assessment guide. We want to make sure our Implementing FinOps guide includes everything practitioners need to know in order to gain knowledge, document their processes, measure KPIs, drive organizational adoption, and automate each of these for each FinOps capability.
To accomplish this, we will need to review each capability and identify:
Knowledge: Is there anything missing or outdated in the capability guides that should be added, updated, or removed?
Metrics: How can we measure success of the capability and the nested elements and action items within the capability?
Process: What process would we recommend for customers to leverage in order to implement this capability?
Automation: How can we automate knowledge sharing, metrics (e.g., collection, reporting, alerting), and related processes (e.g., approvals, next actions)?
Adoption: Do we have any recommendations (or ways to automate) broad adoption for the capability across the organization?
As each capability is reviewed with these 5 lenses in mind, add any ideas on changes we could make to fill gaps and address opportunities in the task lists below. This may be documentation updates, features in existing tools, or potentially new tools that could be added to the toolkit. This issue is for documenting all the ideas and we will review them and prioritize them later, starting with documentation and then moving into new and updated tools.
📋 Understand cloud cost and usage
The content you are editing has changed. Please copy your edits and refresh the page.
We'd love to get your feedback! If you see something missing, please suggest it in a comment and we'll add it to the list. If you'd like to pick up one of the suggestions, either start a discussion or create an issue for it and let us know!
The text was updated successfully, but these errors were encountered:
📝 Scenario
As a FinOps practitioner, I need to learn, document, measure, adopt, and automate FinOps capabilities in order to maximize cloud ROI for my organization
🚀 Goal
Flesh out the Implementing FinOps guide to cover all aspects of maturity based on the FinOps assessment guide. We want to make sure our Implementing FinOps guide includes everything practitioners need to know in order to gain knowledge, document their processes, measure KPIs, drive organizational adoption, and automate each of these for each FinOps capability.
To accomplish this, we will need to review each capability and identify:
As each capability is reviewed with these 5 lenses in mind, add any ideas on changes we could make to fill gaps and address opportunities in the task lists below. This may be documentation updates, features in existing tools, or potentially new tools that could be added to the toolkit. This issue is for documenting all the ideas and we will review them and prioritize them later, starting with documentation and then moving into new and updated tools.
📋 Understand cloud cost and usage
Data ingestion
Allocation
Reporting + analytics
Anomaly management
📋 Optimize cloud cost and usage
Architecting for cloud
Workload optimization
Rate optimization
Licensing + SaaS
Cloud sustainability
📋 Quantify business value
Planning + estimating
Forecasting
Budgeting
Benchmarking
Unit economics
📋 Manage the FinOps practice
FinOps practice operations
FinOps education + enablement
Invoicing + chargeback
FinOps assessment
Onboarding workloads
Cloud policy + governance
FinOps tools + services
Intersecting disciplines
🙋♀️ Ask for the community
We'd love to get your feedback! If you see something missing, please suggest it in a comment and we'll add it to the list. If you'd like to pick up one of the suggestions, either start a discussion or create an issue for it and let us know!
The text was updated successfully, but these errors were encountered: