Whitepaper 'FinOps and cost management for Kubernetes'
Please consider giving OptScale a Star on GitHub, it is 100% open source. It would increase its visibility to others and expedite product development. Thank you!
Webinar 'FinOps and cloud cost optimization for ML/AI workloads.' Register here →
Ebook 'From FinOps to proven cloud cost management & optimization strategies'
OptScale — FinOps
FinOps overview
Cost optimization:
AWS
MS Azure
Google Cloud
Alibaba Cloud
Kubernetes
OptScale — MLOps
ML/AI Profiling
ML/AI Optimization
Big Data Profiling
OPTSCALE PRICING
Acura — Cloud migration
Overview
Database replatforming
Migration to:
AWS
MS Azure
Google Cloud
Alibaba Cloud
VMWare
OpenStack
KVM
Public Cloud
Migration from:
On-premise
Acura — DR & cloud backup
Overview
Migration to:
AWS
MS Azure
Google Cloud
Alibaba Cloud
VMWare
OpenStack
KVM

FinOps principles: Collaboration

The fourth and final principle of the FinOps methodology is Collaboration. As a quick recap, here you can find articles about Visibility, Optimization and Control principles.

What do we mean by collaboration in FinOps?

There is practically no room for development without collaboration: we interact with other people to get feedback, grow and complete some complex tasks which cannot be done on our own. Proper cloud usage is exactly an example of such a task. And by collaboration, I mean not only interaction within a team of engineers or within one department but cross-functional collaboration with a company where engineers, operational, finance and executive teams are involved.

Why is it important?

Because actions and decisions made by one functional team influence others, and the impact can be significant or even fatal for a business. Just imagine the case when an R&D team starts a new project and provisions hundreds of new VMs for that without proper budget planning or notifying the finance and executive team about a cloud bill forecast. Or the executive team cutting costs without proper planning with engineers.

The majority of cloud actions cost money: this is the nature of clouds. You pay for computing, storage, traffic, PaaS, marketplace products, etc. Staying in budget and R&D elasticity is an equilibrium that is not possible to be achieved by one person. For small businesses it should be at least about the collaboration between CTO/VP of Engineering and CFO, for medium-sized and enterprise companies the process and collaboration should be more complex. There should be a FinOps team (it doesn’t mean that they need to sit in one room at the same time) of executive team members translating company strategy; finance people responsible for budgeting, financial control and forecasting; and engineers/operations/DevOps team that works directly with a cloud.

The FinOps team should be responsible for the following issues

  1. Defining cloud usage strategy
  2. Defining and adjusting cloud budgets
  3. Setting cloud usage practices
  4. Reviewing results, adjusting if necessary

Crucial FinOps roles

I would like to highlight some crucial roles in the FinOps team:

  1. Financial analyst and controller – a person that translates expectations and goals from the finance team. It can be CFO or somebody from the CFO office.
  2. Cloud practices visioner  –  a person who sets cloud usage best practices, educates engineers how to properly use clouds and explains why cloud expenses should be another KPI in R&D. Usually, it’s either a separate role or somebody from the DevOps team.
  3. Executive staff –  Senior VP or a C-level positions who controls how the collaboration works and reviews results.
  4. Engineers  – use clouds according to the best practices and budgets and report if there are any escalations.

I have no doubts that the main reason why companies do not succeed with clouds or have serious issues using them is the lack of proper collaboration and planning. Cloud is another fragile asset companies have at their disposal but it brings outstanding results only if it is used properly. Don’t underestimate the value of cross-functional collaboration and cloud usage when it comes to getting to another level.

Nick Smirnov, CEO and Co-Founder

Nick Smirnov, CEO at Hystax

Enter your email to be notified about new and relevant content.

Thank you for joining us!

We hope you'll find it usefull

You can unsubscribe from these communications at any time. Privacy Policy

News & Reports

FinOps and MLOps

A full description of OptScale as a FinOps and MLOps open source platform to optimize cloud workload performance and infrastructure cost. Cloud cost optimization, VM rightsizing, PaaS instrumentation, S3 duplicate finder, RI/SP usage, anomaly detection, + AI developer tools for optimal cloud utilization.

FinOps, cloud cost optimization and security

Discover our best practices: 

  • How to release Elastic IPs on Amazon EC2
  • Detect incorrectly stopped MS Azure VMs
  • Reduce your AWS bill by eliminating orphaned and unused disk snapshots
  • And much more deep insights

FinOps and cloud cost optimization for ML/AI workloads

Join our live demo on 21th 
February and discover how OptScale allows running ML/AI or any type of workload with optimal performance and infrastructure cost.