Apply the FinOps inform, optimise and operate cycle to an engineering organisation's cloud spend.
Information & Communications Technology
Cloud Cost Optimisation and FinOps Practice for Engineering Teams
Apply FinOps practice to make engineering teams accountable for cloud spend, covering cost allocation, rightsizing, committed-use discounts, storage tiering and the dashboards that turn spend into a shared metric.
🗓️Duration5 training days
📚Content4 modules · 8 sessions
🎓On completionAccredited attendance certificate
About the programme
Course Overview
Cloud bills grow in ways that finance teams cannot explain and engineering teams do not feel responsible for, because the two groups usually work from different data and meet only when a budget is already exceeded. FinOps closes that gap by making cost a shared engineering metric rather than a finance-only concern, following a cycle of making spend visible, acting on what it shows, and then operating with cost as a routine input to architecture decisions. This course builds each part of that cycle: tagging and cost allocation so spend can be attributed to a team, product or feature, rightsizing compute and storage against actual utilisation rather than initial estimates, and choosing between on-demand, committed-use and spot or preemptible capacity for different workload patterns. Participants design storage lifecycle tiering, autoscaling policies that track real demand, and anomaly detection that catches an unexpected spend spike within hours rather than at the end of a billing cycle. The course closes with unit economics, connecting infrastructure cost to a business metric such as cost per transaction, and dashboards that give engineering teams a live view of the cost impact of their own decisions.
Expected Learning Outcomes
Design a tagging and cost allocation standard that attributes spend to teams and products.
Rightsize compute and storage based on measured utilisation rather than initial provisioning estimates.
Choose between on-demand, committed-use and spot capacity for different workload patterns.
Build storage lifecycle tiering policies that move ageing data to lower-cost storage automatically.
Configure cost anomaly detection and alerts that catch unexpected spend within hours.
Connect infrastructure cost to unit economics such as cost per transaction or per customer.
Who Should Attend
Engineering teams being asked to take ownership of their cloud spend.
FinOps practitioners bridging finance, procurement and engineering teams.
Cloud platform teams building cost visibility tooling for other teams.
Finance and procurement staff working with engineering on cloud budgets.
Engineering managers accountable for a product or platform's cloud budget.
Architects making cost-aware trade-offs during system design decisions.
Course Modules
Select any module to see its sessions and points.
01FinOps Foundations and Cost Visibility
2 sessions · 8 points
Session 1The FinOps Operating Model
- Explain the inform, optimise and operate cycle and how it applies across an organisation.
- Define FinOps roles and responsibilities shared between finance, engineering and leadership.
- Assess current cost visibility maturity before introducing new tooling or process.
- Set goals for a FinOps initiative that engineering teams can see themselves achieving.
Session 2Tagging and Cost Allocation
- Design a mandatory tagging taxonomy covering team, product, environment and cost centre.
- Build showback or chargeback reporting that attributes spend to the responsible owner.
- Handle shared and untagged resources so allocation reporting remains largely complete.
- Enforce tagging compliance through automated checks rather than periodic manual review.
02Rightsizing and Purchasing Strategy
2 sessions · 8 points
Session 1Rightsizing Compute and Storage
- Analyse utilisation data to identify over-provisioned compute and storage resources.
- Resize or consolidate workloads based on measured CPU, memory and storage usage patterns.
- Set autoscaling policies that track real demand instead of a fixed static capacity.
- Identify and remove idle or orphaned resources that continue to accrue cost.
Session 2Committed-Use, Spot and On-Demand Strategy
- Compare on-demand, committed-use and spot or preemptible pricing for different workloads.
- Build a commitment portfolio that balances discount coverage against workload flexibility.
- Design workloads to tolerate interruption so they can safely use lower-cost spot capacity.
- Track commitment utilisation so purchased capacity is not left unused.
03Storage, Containers and Anomaly Detection
2 sessions · 8 points
Session 1Storage Tiering and Lifecycle Management
- Classify data by access frequency to choose an appropriate storage tier.
- Configure lifecycle policies that automatically move or delete ageing data.
- Balance retrieval cost and latency against storage savings for archived data.
- Audit storage growth trends to catch runaway accumulation before it becomes costly.
Session 2Container and Anomaly Cost Management
- Allocate shared cluster cost to individual teams and workloads running on it.
- Identify over-provisioned container requests that inflate cluster infrastructure cost.
- Configure anomaly detection that flags an unexpected spend spike soon after it starts.
- Define an escalation path for investigating and resolving a confirmed cost anomaly.
04Unit Economics and Embedding Cost Ownership
2 sessions · 8 points
Session 1Unit Economics and Forecasting
- Connect infrastructure spend to a business unit metric such as cost per transaction.
- Build a cost forecast that reflects planned growth and known seasonal demand.
- Track unit cost trends over time to show whether optimisation efforts are working.
- Present unit economics in terms that both engineering and finance stakeholders accept.
Session 2Dashboards and Sustained Cost Ownership
- Design dashboards that give engineering teams a live view of their own cost impact.
- Set cost key performance indicators that sit alongside reliability and performance metrics.
- Run regular cost review sessions that keep optimisation an ongoing practice, not a one-off.
- Embed cost awareness into architecture review so trade-offs are visible before launch.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.