Contributed by JohnAllen Crites of Pearson.
|Internship Title||FinOps Analysts Intern|
|Education Status||Full-time – Finance Major|
|Department Joined||Infrastructure & Operations|
|FinOps Capabilities||Forecasting & Budget Management|
|Period of Internship||12-weeks|
|Background||The company has 5 separate business units that request AWS accounts from a centralized Cloud Management team.
Product owners are required to submit an estimate & secure budget before an AWS account can be provisioned.
Product owners can consult with engineering leads, FinOps Analyst, or self produce and estimate.
Estimates can be for new Cloud first workloads or migrations from data centers
|Problem Statement||The centralized FinOps team believes inconsistency in estimates is a result of lack of training across business units and wants to establish centralized governance and tooling. FinOps recommends a standard template and at a minimum all production estimates are peer reviewed by the FinOps team.
|Scope||Pull and organize actuals for the previous 12 months and compare to estimates submitted during account provisioning. Over 100 AWS accounts.|
|Out of Scope||Existing Cloud workloads re-architectured, requires re-forecast but are out of scope for this project using first time estimation required to acquire an AWS account.
Types of insights :
|Tools Used||AWS Cost Explorer
AWS Aurora Mysql
|Skills Used||Excel formulas
|Personas Interactions||Technical Project Managers
|Key Discoveries||One business unit “X” had a significantly higher variance of estimate to actuals
Teams that estimated the closest to actuals
LEARNING & DEVELOPMENT PLAN
|Mentor||Part of a cohort of interns
Manager met twice a week
Peer mentor assigned
|Certification||No Certification achieved during internship
12 leadership learning hours
Third party CFM training tool
|Tools||All AWS services were new tools learned by the intern.|