Scrum Project Budget: Cost, Earned Value & EVM

Most Scrum teams track their velocity, burndown charts, and delivered user stories. Very few track what all of this actually costs. Yet behind every sprint lies a precise project cost : a reality that the Scrum Guide deliberately leaves out of scope, but which every team accountable to a sponsor must be able to measure (salaries, freelancers, contractors). The gap between the estimated Scrum project budget and actual cost accumulates silently across iterations. When it finally becomes visible, it is often too late to correct the trajectory. This article explains how to calculate sprint costs, track estimated vs. actual variance, and anticipate overruns before they compromise your project.

Scrum Project Budget: What Most Teams Fail to Measure

A sprint has a precise financial cost. It is the sum of days worked by each team member multiplied by their daily rate. Without this tracking, a team can deliver 40 story points of velocity for 6 consecutive sprints while overshooting their budget by 30% : without realizing it until the quarterly steering committee.

Managing agile project cost is not about micromanaging individuals. It is about providing decision-makers with financial visibility aligned with delivery velocity : so they can make informed trade-offs.

In traditional project management, the budget is fixed upfront for a fixed scope. In Scrum, the scope evolves : but the budget often remains fixed. This gap creates a specific need: knowing how much each sprint costs to answer the sponsor's core question: "How much budget is left to deliver what?"

How to Calculate a Scrum Sprint Cost using Daily Rates?

The Foundation: Daily Rates by Role

Calculating a sprint cost relies on three elements: the roles present in the team, their daily rate (internal cost or external rate), and their actual availability during the sprint. Daily rates can be calculated from internal cost (gross loaded salary ÷ 220 working days) or the daily billing rate for freelancers and agencies.

This estimated budget is calculated prior to the sprint. At the end of the sprint, the actual cost is computed from actual logged time : including absences, part-time work, and non-sprint emergencies. The variance between the two yields the sprint overrun or savings.

Internal Cost vs. Billed Cost

For an agency or IT service provider billing services to a client, financial tracking has an extra layer: the difference between internal cost (what the team costs internally) and billed price (what the client pays). The gap constitutes the profit margin. A sprint exceeding its internal cost budget directly erodes profit margins : and teams that fail to track this data often discover at project end that they worked at a loss.

Scrum Budgets in Fixed-Price vs. Time & Materials: What's the Difference?

Contract structure deeply influences Scrum budget management.

Under Time & Materials (T&M), the client pays for actual days consumed. Budget management boils down to ensuring consumed days stay within the approved cap. Actual cost tracking per sprint is directly billable : transparency is total, but financial risk sits with the client.

Under Fixed-Price contracts, the vendor commits to a scope for a fixed price. Budget management becomes critical for profitability: every sprint exceeding estimated budget directly reduces profit. In this setup, tracking cost per delivered story point is mandatory : it is the tool that detects when a project turns unprofitable and enables scope renegotiation before damage becomes irreversible.

How to Establish an Initial Scrum Project Budget?

The question every sponsor asks before launching a Scrum project: "How much will it cost?" In agile, the honest answer is "it depends on the scope you choose to deliver" : but we can do much better than a shoulder shrug.

1. Estimate the initial backlog in story points. During an initial story mapping workshop, the team roughly estimates major epics. You don't need 100% precision at this stage : the goal is an order of magnitude.
2. Calculate probable velocity. For a new team, a rule of thumb is taking 60% of theoretical capacity for early sprints (onboarding, learning curve, friction). For an established team, use historical velocity.
3. Calculate required sprints and total cost. Estimated sprints = total backlog points ÷ velocity. Total budget = estimated sprints × cost per sprint. Express the result as a range (optimistic / realistic / pessimistic) and refine after initial real sprints.

Tracking Estimated vs. Actual Cost Variance Sprint by Sprint

This table tells a concerning story: costs increase sprint after sprint (+27% between Sprint 1 and 3) while velocity drops (38 → 33 points). Cost per delivered point rises from €513 to €752 : a 47% efficiency degradation across 3 sprints. Without cost tracking, these signals remain invisible until monthly reporting.

The 4 Key Budget Metrics in Scrum

1. Consumed Budget vs. Planned Budget (S-curve). Cumulative actual costs over time compared to target baseline.
2. Cost per Delivered Point. Computed every sprint and tracked as a trend over 3 to 5 cycles.
3. Cost / Business Value Delivered Ratio. Connecting financial investment with quantifiable business value.
4. Remaining Budget vs. Remaining Backlog. Evaluating if remaining budget suffices to complete Must-Have backlog items.

Manifst: From Sprints to Earned Value Management

In Manifst, daily rates are defined for each team member. Logged time on tickets is automatically valued to compute the actual cost of the project and each sprint. When a baseline budget (BAC) is set, Manifst automatically computes EVM indicators: Planned Value (PV), Earned Value (EV), Actual Cost (AC), CPI, SPI, EAC, ETC, VAC, and TCPI.

Discover EVM Budget Control in Manifst or view Manifst plans.

Try Manifst for free : EVM budget control included from Starter →