Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement FinOps guide build-out #777

Open
22 tasks
flanakin opened this issue Jun 26, 2024 · 0 comments
Open
22 tasks

Implement FinOps guide build-out #777

flanakin opened this issue Jun 26, 2024 · 0 comments
Assignees
Labels
Tool: FinOps guide Implementing FinOps guide Type: Feature 💎 Idea to improve the product

Comments

@flanakin
Copy link
Contributor

flanakin commented Jun 26, 2024

📝 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:

  1. Knowledge: Is there anything missing or outdated in the capability guides that should be added, updated, or removed?
  2. Metrics: How can we measure success of the capability and the nested elements and action items within the capability?
  3. Process: What process would we recommend for customers to leverage in order to implement this capability?
  4. Automation: How can we automate knowledge sharing, metrics (e.g., collection, reporting, alerting), and related processes (e.g., approvals, next actions)?
  5. 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

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!

@flanakin flanakin added the Type: Release 🚀 Tracks the progress of a release label Jun 26, 2024
@flanakin flanakin self-assigned this Jun 26, 2024
@flanakin flanakin changed the title Flesh out the Implement FinOps guide Implement FinOps guide build-out Jun 26, 2024
@flanakin flanakin assigned KevDLR and unassigned flanakin Jun 26, 2024
@flanakin flanakin added Type: Feature 💎 Idea to improve the product Tool: FinOps guide Implementing FinOps guide and removed Type: Release 🚀 Tracks the progress of a release labels Jun 26, 2024
@flanakin flanakin added this to the Guide - Build-out milestone Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tool: FinOps guide Implementing FinOps guide Type: Feature 💎 Idea to improve the product
Projects
None yet
Development

No branches or pull requests

3 participants