Jump to content

Draft:Cloud FinOps: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Edits to who is writing what.
Line 74: Line 74:


Modernization - STEVEO
Modernization - STEVEO

Cost = usage * rate
Usage depends on technical choices, like architecture, scalability and implementation.
Rate is controlled by the vendors and follows a risk and reward approach


=== Align to business ===
=== Align to business ===

Revision as of 10:01, 4 July 2024


Definition

"FinOps is an operational framework and cultural practice which maximizes the business value of cloud, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams."[1]

The Origin of FinOps

Cloud FinOps is a Portmanteau of finance and DevOps. Born out of the significant changes that cloud computing brought to the finance and procurement processes of IT, the term is designed to signify the importance of teams collaborating to drive successful cloud adoption. The concepts were initially referred to as “cloud cost management” and then changed into “cloud cost optimization”. FinOps specifically focuses on bringing value from cloud services to the organization which is one of the main reasons it has become prevalent over other terms such as cloud cost optimization, which doesn’t obviously cover concepts such as cost allocation and “cloud economics”, which doesn’t call out the cultural aspects driven by collaboration. Cloud Financial Management (CFM) is still a term often used and has generally been used by Amazon Web Services (AWS), while the term is considered similar to FinOps, some argue they should not be used interchangeably.

Timeline of the rise of FinOps

  • 2006 - The birth of Cloud and services such as AWS EC2[2] which begins the move from Capex towards Opex Pay as you go compute consumption creating a paradigm shift.[3]: 6–14 
  • 2008 - GCP launches adding multi-cloud complexity but also generally using very different concepts and naming conventions to AWS.
  • 2010 - Microsoft Launch Azure, adding further multi-cloud complexity, they also release paper on Economics of Cloud[4] from which the term Cloud Economics is coined.
  • 20010-2017 - Rise of the second generation of cloud, more organizations start to serious incorporate cloud into their strategies[5].
    • Growth of cloud usage, introductions to the challenges of moving IT spend from Capex to Opex, removing financial control for the finance teams.[6]
    • Lots of shadow IT for cloud usage, reducing control of costs and IT for the IT teams.
    • Bill shock begins to start as cloud grows over the years.[7]: 1 
  • 2012 - Large forward thinking organization who have heavily invested in the cloud start enacting what will later become known as FinOps.[8]: 1 
  • 2012-2019 - FinOps begins to come to being simultane ous across the world in different organisations.[9]: 4–5 
  • 2019 - FinOps Foundation Founded [3]: 14  and Cloud FinOps first edition released
  • 2020 - FinOps Foundation becomes part of Linux Foundation.[10]
  • 2022 - Cloud FinOps becomes most commonly used term[8]: 5 

Financial Operations

It's important to distinguish Cloud FinOps from traditional financial operations (which can also be abbreviated as "finops"). While financial operations deal with the management of a company's finances, Cloud FinOps focuses specifically on the financial aspect of cloud operations, blending elements of IT, finance, and business to maximize cloud investment value.

Aim of FinOps

The FinOps Foundation gives FinOps the following definition: “FinOps is an operational framework and cultural practice which maximizes the business value of cloud, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.” - FinOps Foundation Technical Advisory Council.[1]

While many organisations came forward with various approaches and concepts around the best way to achieve success in the financial aspects of Cloud, the most generally used is the FinOps Framework from the FinOps Foundation, most recently updated in 2024.[11]

Framework

The most important part of the framework in reference to the Aims of FinOps are the principles[12].

  • Teams need to collaborate
  • Decisions are driven by business value of cloud
  • Everyone takes ownership of their cloud usage
  • FinOps data should be accessible and timely
  • A centralized team drives FinOps
  • Take advantage of the variable cost model of the cloud. [8]: 10 

While many are concerned as to why cloud vendors are entering the cloud FinOps space due to the fact it by design should reduce wastage and the costs of cloud, they see it as a way of unlocking value realization and innovation, which then drives to long term consumption of their services.[13][9]: 11 

The Framework also includes: personas, phases, maturity, domains and capabilities.

Benefits, Challenges and Limitations of FinOps

Cloud Value

Understanding value from IT has long been a challenge for organizations, even prior to the adoption of cloud and is something organizations have long being trying to evaluate.

WRITE SMALL SUMMARY ADDITION (until Luca) - STEVEO

“The purpose of evaluating Information Communication Technology (ICT) is to gain an understanding of how ICT is contributing to organization performance in a given organizational context.”[14]: 19–35 

Collaboration

Research suggests that Cloud has a strong potential to support and facilitate business collaboration at a low cost.[15][16] The financial challenges created around cloud have largely stemmed from a lack of collaboration and understanding between key teams impacted by the paradigm shift created by adoption.[3]: 6–7 

Collaboration between FinOps, finance and engineering personas (amongst others - see FinOps Foundation Framework - Personas) is one of the most important keys to success to effective FinOps, which in turn drives successful cloud value realisation and adoption. However, this collaboration is also one of the most common challenges found in FinOps.[17] Without true executive/leadership sponsorship, FinOps is likely to be limited in its impact and alone, without collaboration, FinOps practitioners are unlikely to drive successful outcomes for the organization.

Cost Reduction (and potential carbon benefits) --- TO BE WRITTEN

Intro - FRANK

Waste Reduction - STEVEO (mastering AWS ref)

Rate opt - FRANK

Modernization - STEVEO

Cost = usage * rate Usage depends on technical choices, like architecture, scalability and implementation. Rate is controlled by the vendors and follows a risk and reward approach

Align to business

IT has often found it challenging how it, and the investment in IT, is aligned directly to business goals. One argument is that  “IT investment is not always aligned with organizational goals, strategy, resources or capabilities”.[18] Cloud has not so far, generally, proven to be much different, there are still major challenges in aligning cloud costs to business outcomes.

Research undertaken in 2017 which viewed academic research from 2010 onwards found that there were relatively varied motivations for an organization to move to the cloud. In terms of FinOps, it is interesting that specifically Cost effectiveness is cited as a key motivator for cloud adoption[19][20]. To help drive the value of cloud, it has been generally agreed that the cloud strategy must align to that of the business.  Studies show show “a very strong statistically significant correlation between Cloud Computing Adoption and Information Technology Effectiveness”[21][22]: 13–29  however “the correlation between Cloud Computing Adoption and Strategic

Alignment was not recognized as statistically significant” ---Ref as above. It can be argued that the lack of cloud value realisation, and the 2023/2024 drive to cloud repatriation is due to the lack of successful FinOps implementation in those organizations.

<Chargeback is aligning cloud costs to the business in its cleanest form for business financial reporting> ---TO BE WRITTEN - FRANK

Unit Economics specifically has been regarded as one of the answers to this long term challenge, the IT Paradox, of bringing an understanding specifically on how ICT costs deliver value to the business. Unit Economics, in short, are where cost (in this case cloud costs) are compared directly to a business metric. A simple example of this may be cost per conversions for a website. The cloud costs attributed to the website can be divided by the amount of unique visitors and the number of conversions that can be found in other data available to the organisation. This would allow an organization to understand how changes to their cloud infrastructure behind the website may have changed the amount of visitors.

Visibility

Showback - TO BE WRITTEN - FRANK

Importance of visibility - Prius effect[23] --- TO BE WRITTEN - FRANK

Challenge - Cloud Service Providers (CSP) such as Azure, AWS, and GCP have an unprecedented level of complexity in cloud computing. Each of these providers offers services, spanning across approximately 19 product categories and encompassing over 150 distinct cloud products. Each product comes with multiple workload types, unique billing formats, spot pricing options, and Reserved Instances (RIs). This intricate landscape presents a significant challenge for businesses seeking to gain central visibility, clarity, and data insights for cost-effective decision-making.[24]

Empowering Engineers to take action

Empowering Engineers to take action has long been seen to be one of the biggest challenges in FinOps, having been one of the top challenges in the State of FinOps data since 2021.(https://data.finops.org) The reasons for this are generally considered to be around the FinOps maturity level of the organization across areas such as adoption, education, skills, tools, leadership support, organizational alignment, awareness, and prioritization. ---Ref Gamification FinOps Hackathon book, the reference is page 10

Engineering Ways of working--- TO BE WRITTEN - STEVEO

Cost as a non-functional requirement.[25] - TO BE WRITTEN - STEVEO

A solution that has been proven to work very well is the gamification of FinOps through conducting a FinOps Hackathon. The organic nature of a Hackathon is familiar with engineers and when given a FinOps problem statement to solve, it enabled cross functional teams to work together and present real cost saving business value adding solutions to leadership. A FinOps Hackathon educates and aligns teams to build FinOps solutions for the enterprise. ---Ref to Brian

References

  1. ^ a b "FinOps Foundation - What is FinOps?". Retrieved 2023-11-10.
  2. ^ Mansoor, Eli (April 2019). Mastering AWS Cost Optimization (2nd ed.). United Kingdom. p. 13. ISBN 9798634715841.{{cite book}}: CS1 maint: date and year (link) CS1 maint: location missing publisher (link)
  3. ^ a b c San Miguel Sanchez, Alfonso; Obando Garcia, Danny (February 2023). Efficient Cloud FinOps (1st ed.). United Kingdom: Packt. ISBN 9781805122579.{{cite book}}: CS1 maint: date and year (link)
  4. ^ "The economics of the cloud" (PDF). The economics of the cloud. November 2010.
  5. ^ "History of the cloud | BCS". www.bcs.org. Retrieved 2024-06-27.
  6. ^ "Business need for FinOps for cloud computing - FinOps Essentials for Cloud Deployments Video Tutorial | LinkedIn Learning, formerly Lynda.com". LinkedIn. Retrieved 2024-06-27.
  7. ^ Monroe, Dwayne (13 November 2019). Azure Cost Management for Busy People (1st ed.). p. 1. ISBN 9781707823345.{{cite book}}: CS1 maint: date and year (link)
  8. ^ a b c Storment, J. R.; Fuller, Mike (2023). Cloud FinOps: collaborative, real-time cloud value decision making (Second ed.). O'Reilly. p. 10. ISBN 978-1-4920-9835-5. OCLC 1371814404.
  9. ^ a b Cite error: The named reference :1 was invoked but never defined (see the help page).
  10. ^ "Why was FinOps born? - FinOps.World". finops.world. 2020-09-24. Retrieved 2024-06-27.
  11. ^ "FinOps Framework Overview". Retrieved 2024-06-27.
  12. ^ "FinOps Principles". Retrieved 2024-06-27.
  13. ^ "What is Cloud FinOps?". Google Cloud. Retrieved 2024-06-27.
  14. ^ Ceric, Dr Arnela (2015-07-01). "Bringing Together Evaluation and Management of ICT Value: A Systems Theory Approach". Electronic Journal of Information Systems Evaluation. 18 (1): 19‑35. ISSN 1566-6379.
  15. ^ Loukis, Euripidis; Kyriakou, Niki; Pazalos, Konstantinos (June 1–2, 2015). Operational and Innovation Collaboration and Cloud Computing. European, Mediterranean & Middle Eastern Conference on Information Systems 2015. Athens, Greece.
  16. ^ Willcocks, Leslie; Venters, Will; Whitley, Edgar (2014-01-01). Moving to the Cloud Corporation: How to face the challenges and harness the potential of cloud computing. ISBN 978-1349467334.{{cite book}}: CS1 maint: date and year (link)
  17. ^ "The State of FinOps". data.finops.org. Retrieved 2024-06-27.
  18. ^ How Does Cloud Computing Change the Strategic Alignment Between Business and IT?
  19. ^ Bogataj Habjan, Kristina; Pucihar, Andreja (2017-08-01). "The Importance of Business Model Factors for Cloud Computing Adoption: Role of Previous Experiences". Organizacija. 50 (3): 255–272. doi:10.1515/orga-2017-0013. ISSN 1581-1832.
  20. ^ Ross, Virginia Watson (2010). Factors Influencing the Adoption of Cloud Computing by Decision Making Managers (Thesis). ProQuest LLC.
  21. ^ Bogataj Habjan, Kristina; Pucihar, Andreja (2017-08-01). "The Importance of Business Model Factors for Cloud Computing Adoption: Role of Previous Experiences". Organizacija. 50 (3): 255–272. doi:10.1515/orga-2017-0013. ISSN 1581-1832.
  22. ^ Chebrolu, Shankar Babu (2010). Assessing the Relationships among Cloud Adoption, Strategic Alignment and Information Technology Effectiveness (Thesis). ProQuest LLC.
  23. ^ "The Prius Effect: Immediate Feedback and Commercial Energy Use". Powerhouse Dynamics. Retrieved 2024-06-27.
  24. ^ McCumber, Brian (July 2023). Power BI for FinOps: Data Driven Multi Cloud Financial Management. FinOps Fabric Publishing; 1st edition. p. 20.
  25. ^ "The Frugal Architect | Make Cost a Non-functional Requirement". thefrugalarchitect.com. Retrieved 2024-06-27.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Draft:Cloud_FinOps&oldid=1232555293"