IT Project Cost Tracking
Spending $400M a Year. Measuring It in Story Points.
How a Fortune 500 Firm Priced 300+ IT Projects in Dollars
In most large IT organizations, the work and the money live in different systems. Engineering tracks what teams build, in story points and sprints. Finance tracks what it costs, in dollars. Each system does its job, so the gap between them rarely draws attention.
A Fortune 500 financial services firm was running more than 300 active projects on an annual IT budget above $400 million. The work sat in Jira, measured in story points. The spend sat in the finance system, measured in dollars. The two described the same 300 projects and never met.
Story points are the right unit for planning a sprint. They tell a team how much it can take on and whether it delivered what it committed to. What they can’t tell anyone is how much real time, effort, and money an initiative is consuming. A team can burn its points on schedule while the project behind it costs far more than the budget suggests.
What the agile board left out
Jira answered one question well: what did each team commit to, and what did they ship? That covers delivery. It leaves out cost. The board could show a project on track and on target while saying nothing about whether it was cheap or ruinously expensive to get there.
For a portfolio of 300 projects and a $400 million budget, that blind spot is expensive. Leadership could see which teams were hitting their commitments. They couldn’t see which initiatives were eating a disproportionate share of the budget, because the effort and the cost never sat in the same view.
Connecting the agile data to the budget
We pulled the agile data straight from Jira and translated it into spend. Story points became dollars: cost per developer, cost per project, across the full portfolio. Effort and cost landed in one view for the first time.
The translation itself is the whole trick. A story point has no fixed dollar value, so pricing it means tying developer time and cost back to the work each point represents, then rolling that up across every team and initiative. Done once for 300 projects and kept current, it turns an agile board into something a CFO can read.
Where the money went
With effort priced in dollars, leadership could compare initiatives on a single scale. A project that looked modest in story points might turn out to be one of the most expensive in the portfolio, and now that showed. Two initiatives delivering similar output could be set side by side and judged on what each one cost.
That changed how the portfolio got steered. Rather than managing 300 projects on delivery status alone, leadership could direct spend toward the work that earned its cost and question the initiatives whose price had never been visible.
The Lesson
Your project data is financial data. The agile board and the budget usually live in separate worlds, owned by different teams and reported in different units, and the translation between them is the piece almost nobody builds. The work is already tracked. Putting it in the language leadership decides in is what turns it into a portfolio you can steer.
The win here was giving effort a price. Once a project could be weighed in dollars, it could be weighed against every other project on the one scale that decides whether it continues.
Give Your Portfolio a Price Tag
Agile boards track effort in points and budgets track it in dollars, and the two rarely meet in the same view. That gap means leadership steers a portfolio on delivery status while guessing at cost. We pull the agile data and price it: effort in dollars, per developer and per project, so every initiative can be compared on the one scale that decides whether it continues. And if your reporting already ties work to spend cleanly, we’ll tell you that rather than build you something you don’t need. Reach out to us and book a free Data Health Check.
