How to Calculate Budgets For Agile Teams

This content is syndicated from LeadingAgile by Jesse Fewell. To view the original post in full, click here.

A common concern I get from Agile newbies is “how do I calculate the cost of my agile project, if I don’t do all up front planning?” Actually, it turns out that when I leverage agile methods to simplify my project accounting,  budgeting becomes much easier. I’m going to show you two approaches that leverage two powerful attributes of agile projects.

Powerful Attributes of Agile Projects

Stable Team Roster. Project managers across the world agree that a key risk for any project is getting your people yanked off the team, or having new people thrown onto a team only at the last minute. This is the evil version of “Resource Leveling”, and it prevents any reliable forecast of a project burn rate. So, let’s see what happens when we request, nay demand, a stable team roster.

Time-boxed Iterations. Rather than try to calculate the budget of a team across 12 months, I want to simplify my problem. If we work in 1-month time-boxed iterations, I only need to calculate the budget of a given iteration. Let’s see how that works below.

Approaches for Calculating Agile Team Budget

Using a Blended RateWhen I worked at Marriott International HQ outside of Washington DC, project managers did not have visibility into the people’s compensation. Instead, we used a common “blended rate” of $125/hour. HR estimated the total loaded cost of the organization came down to that one number. Let’s assume I have a team roster of 12 people, but 4 of them are half-time, yielding a total of 10 Full-Time Equivalents (FTEs).

=> $125 X 8 chargeable hours per day = $1,000 fixed burn rate per person per day.

=> $1,000 X 10 FTEs on my team = $10,000 fixed burn rate per day.

=> $10,000 X 10 chargeable days in a 2-week iteration = $100,000 fixed iteration burn rate.

Using Specific Labor CategoriesIn other organizations, the Project Manager has to capitalize labor costs according to specific categories. For that we can’t over-simplify the problem with a blended rate.

=> Annual loaded cost of each team member / number of theoretical iterations in a year = fixed burn rate per iteration for that team member

=> Sum (every team member’s specific fixed burn rate per iteration) = fixed iteration burn rate

In the example below, I run these calculations to derive a $19,350 fixed burn rate per iteration.

Sample team costs

So What?

Having a fixed, reliable iteration burn-rate is killer. Once I have that budgetary metric, I finally have some compelling talking points around common conversations:

  • “Mr. Client, our agile release planning session says the ‘social media’ initiative will take 5 iterations, totaling $250K. Is it projected upside worth the cost?”
  • “Yes, Ms. Vice President, we can add that emergency feature. However, the team says that will take another 2 iterations costing $100K. Can you authorize the additional budget?”
  • “Team, we have to be ruthless about bugs. Any bug that prevents us from going live will cost us $50K in an extra iteration, and I don’t want that coming out of my annual bonus.”
…or use the metric to argue against common project mistakes:
  • “Sure, you can take the senior tester off my project. But that will cause my current iteration to fail at a cost of $50K. Plus the team feels it will add another 30% risk of missing the deadline for the remaining $200K worth of work. That puts the total financial impact at $50K + (30% x $200K) = $110K. Are you prepared to eat those costs as well?
  • “I know we are falling behind, but If we extend the iteration until we feel we are done, I have no way of forecasting the financial impact. However, if we simply extend the project by one extra iteration, I can tell you it will cost exactly $50K.”

What about you? Have you found agile projects to be easier or harder to budget?



The post How to Calculate Budgets For Agile Teams appeared first on LeadingAgile.

Leave a Reply

What is 4 + 1 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”