Skip to content

Financial management of an IT project: budget, tracking, estimate to complete

Project managers, PMOs, management controllers and budget-holding managers · 2 days (14 hours) · in-house, on site or remote · 10 participants maximum

At a glance

Duration
2 jours (14 heures)
Format
On site and remote
Group size
10 participants maximum
Level
Intermediate
Audience
IT project managers who hold a budget without having been trained to track it
Prerequisites
Having already taken part in a project, in any capacity: the session does not go back over the basics of steering.
Methods
Short talks, twenty minutes at most, each followed by an exercise from the workbook
Assessment
Beforehand: a positioning questionnaire (budgets held, tracking tools, difficulties met), which adjusts the weighting between modules
Lead time
Scheduled during framing, to suit your availability
Pricing
On a quote basis, depending on format, duration and number of participants. The first call is free.
Accessibility and disability
See the dedicated section

A project budget is rarely lost all at once. It is lost in an estimate to complete nobody recalculated, in services committed but not yet invoiced that nobody sees, in a run licence forgotten at framing. These two days give the people who hold a budget the full mechanics to keep it: building a budget that covers internal effort, external services, licences and run; separating what is spent, committed and remaining; calculating a simplified earned value that fits in a spreadsheet; forecasting the landing before the committee discovers it; and arbitrating or renegotiating with defensible figures. The session relies on an exercise workbook: each module ends with a calculation done by hand on a case that gets more complicated from module to module, then with a transposition onto a real project of the company. Nothing here is accounting or tax: it is the budget as a project manager steers it, not as an accountant closes it.

Learning objectives

  • Build a complete project budget separating internal effort, external services, licences and run costs, with the assumptions written next to each line
  • Tell CAPEX and OPEX apart from the project manager's point of view, and know which questions to ask management control without going into accounting
  • Keep a spent / committed / remaining tracking table up to date and consistent, from the data available (timesheets, purchase orders, invoices)
  • Calculate a simplified earned value (physical progress, actual cost, cost and schedule variance) in a spreadsheet, with no dedicated software
  • Produce a reasoned forecast at completion and update it at every committee
  • Prepare a budget trade-off as costed options, and conduct a renegotiation with a supplier or a sponsor
  • Present a budget and its variances to a committee, on one page, without diluting bad news
  • Close a project budget and extract the variances that will serve to estimate the next project

Programme

01Why project budgets slip

1 h 30
  • The four classic leaks: estimate to complete never recalculated, invisible commitments, run forgotten at framing, scope growing with no budget line
  • What a project manager owes the sponsor on the budget, and what they do not answer for
  • Budget, cost, price, effort: four words that get mixed up in committee
  • Round table: state of the budgets participants bring, and each one's sticking point
  • Workbook: the running case is introduced, it will be used through to closure

02Building the budget: internal effort, services, licences, run

3 hours
  • Internal effort: converting person-days into euros, with which daily rate and who to ask for it
  • External services: fixed price, time and materials, capped time and materials; what each mode changes for tracking
  • Licences and subscriptions: acquisition cost, recurring cost, volume tiers, renewal date
  • Run from the framing stage: operations, support, hosting, and why a project with no run line is a wrong budget
  • CAPEX and OPEX from the project manager's seat: what the distinction changes in trade-offs, and what is left to management control
  • Exercise: building the full budget of the running case, then transposing onto the budget brought in

03Tracking: spent, committed, remaining

2 h 30
  • Three columns that never mix: spent (done and paid or payable), committed (ordered, not yet delivered), remaining (what is still to be committed)
  • Where the figures come from: timesheets, purchase orders, invoices, and what to do when they arrive late
  • Recalculating the estimate to complete rather than deducing it: the difference between tracking and subtracting
  • The one-page tracking table, by work package and by cost type
  • Exercise: three months of tracking on the running case, with late invoices and a forgotten order

04Simplified earned value and forecast at completion

2 h 30
  • Physical progress versus budget progress: why “60% of the budget spent” says nothing without “40% of the work done”
  • The four numbers that suffice: planned value, earned value, actual cost, and the variance that follows
  • Calculating a cost and schedule performance index in a spreadsheet, and reading it without over-reading it
  • Forecast at completion: three methods depending on whether the variance is temporary or structural
  • Updating the forecast at every committee, and recording why it moved
  • Exercise: earned value and forecast at completion of the running case at mid-point, then on the budget brought in

05Trade-offs and renegotiation

2 h 30
  • When the forecast overshoots: the four levers (scope, schedule, quality, resources) and their hidden cost
  • Preparing a trade-off as costed options, with a recommendation you own
  • Renegotiating with a supplier: what can be negotiated (volume, schedule, contract mode), what cannot be mid-way
  • Asking a sponsor for more: the file that gets an answer, the one that gets postponed
  • Role play: each sub-group presents a trade-off on the running case, the others hold the sponsor and supplier roles

06Presenting to a committee, closing, capitalising

2 hours
  • The committee's budget page: spent, committed, remaining, forecast, variance and decision requested, nothing else
  • Announcing an overrun: say it first, with the cause and the recommended option
  • Closing a budget: settling commitments, switching to run, archiving the assumptions
  • Capitalising: the gaps between estimate and actual that serve to estimate the next project
  • Validation quiz, individual action plan and handover of the take-away materials

Who it is for

  • IT project managers who hold a budget without having been trained to track it
  • PMOs who consolidate the budgets of several projects and need reliable estimates to complete
  • Management controllers who want to understand how a project manager builds and tracks their figures
  • Business managers or department heads who have been handed a project budget
  • IT departments of small and mid-size companies wanting a shared budget tracking method across their project managers

What you take away

  • The completed exercise workbook, with the corrected answers
  • A project budget template by cost type (internal effort, services, licences, run), with its assumptions
  • A spent / committed / remaining tracking table, in a spreadsheet, ready to fill in
  • A simplified earned value and forecast-at-completion calculator, in a spreadsheet
  • A committee budget page template, with the decision requested
  • An outline for a trade-off file as costed options
  • The full session materials

Prerequisites

  • Having already taken part in a project, in any capacity: the session does not go back over the basics of steering.
  • Being able to use a spreadsheet (simple formulas, sorting, sums): every calculation is done in one.
  • No accounting or tax knowledge is required, and the session provides none: anything to do with accounting, tax or capitalisation of expenses is referred to your management control or your chartered accountant.
  • Bringing, if possible, a real current or past project budget of the company, even partial: it is the material for the transposition at the end of each module.

Teaching methods

  • Short talks, twenty minutes at most, each followed by an exercise from the workbook
  • A running case that gets more complicated from module to module: late invoices, forgotten order, growing scope, request for more budget
  • Systematic transposition onto a real budget brought by participants, chosen during the preparatory call
  • All calculations in a spreadsheet, with no project management software or proprietary tool: what is learnt works everywhere
  • A committee trade-off role play, with sponsor and supplier roles held by participants
  • Feedback from real assignments at every module: what was renegotiated, what cost dearly
  • Group capped at 10 participants so that every tracking table is reviewed

Assessment of learning

  • Beforehand: a positioning questionnaire (budgets held, tracking tools, difficulties met), which adjusts the weighting between modules
  • During the session: correction of the workbook exercises at every module, against a criteria grid handed out at the opening (complete budget, three consistent columns, reasoned forecast)
  • Trade-off role play observed and debriefed on four criteria: costed options, explicit recommendation, cause of the variance named, decision obtained
  • At the end: a validation quiz covering the six modules, corrected and discussed in the room
  • Four to six weeks later: a one-hour remote follow-up on the budget tracking actually put in place and on the first forecast presented to a committee

Where what I teach comes from

Adrien Bouthet, freelance IT Project Manager and Product Owner based in Bordeaux, with eight years of experience steering digital projects. The methods in these two days come from budgets I have held myself. At La Banque Postale, since February 2025, I have been steering the digital onboarding journeys on a budget in the order of one million euros. The year before, on the migration of the document management platform run jointly with Caisse des Dépôts, I took over a late project and brought it back on track in under three months, with licence costs cut from 600,000 EUR to 20,000 EUR a year: that is where the modules on licences, renegotiation and forecast at completion come from. Those figures are results from steering assignments, not a promise made to participants. I have already taught this course in a school, and I have been a trainer in programming and management since 2020. I am neither an accountant nor a tax adviser: what I teach is the budget as seen by the project manager, and anything that belongs to accounting or tax is referred to your management control or your chartered accountant.

Real example

The modules on licences and renegotiation come from real ground: on the migration of the La Banque Postale document management platform, run with Caisse des Dépôts, licence costs were brought down from 600,000 EUR to 20,000 EUR a year and a late project came back on track in under three months. A result from a steering assignment, not a promise made to participants.

Read the case study

Frequently asked questions

Is accounting knowledge required?+

No, and the session does not provide any. We talk about the budget as a project manager builds and tracks it: days, euros, commitments, remaining. The CAPEX / OPEX distinction is covered for what it changes in trade-offs, not for its accounting rules. Any question about capitalisation, depreciation or tax is referred to your management control or your chartered accountant.

How is this different from the “Steering an IT project end to end” training?+

The other session covers the whole life cycle, from framing to production rollout, and devotes part of one module to the budget. This one does nothing but budget, in depth: building, tracking, earned value, forecast, trade-offs and presentation. It is made for people who already steer projects and whose weak point is the numbers.

Do we work on our own budgets or on a textbook case?+

Both. The workbook relies on a running case, because learning estimate to complete and earned value takes a case that gets complicated on purpose. Each module then ends with a transposition onto a real budget brought by participants, chosen during the preparatory call, even partial or already closed.

Is specific software needed?+

No. Everything is done in a spreadsheet, the one you already use. The templates provided are deliberately simple so they can be copied into any project management or management control tool afterwards.

On site or remote?+

Both. On site at your premises, in Bordeaux and across Nouvelle-Aquitaine; remotely anywhere in France. The remote format keeps the sub-groups, the workbook and the trade-off role play; it only requires each participant to have a spreadsheet on their workstation.

How many participants at most?+

Ten. Every tracking table and every forecast is reviewed in session, and the trade-off role play requires everyone to hold a role. Beyond that, the review no longer fits in the two days.

Our budget figures are confidential. How does that work?+

Budgets brought in can be masked or scaled (every amount multiplied by the same coefficient): the method works identically. Documents remain company property and are neither kept nor reused after the session.

Framework and terms

Funding

These sessions are invoiced directly to the company, out of its own skills development budget. They are not eligible for pooled funding schemes (OPCO, CPF, France Travail), which require Qualiopi certification.

Certification

This session is not a certifying course. I do not deliver any Scrum.org, Scrum Alliance, Scaled Agile (SAFe) or PeopleCert (ITIL) certification, nor any qualification registered with the RNCP or the Répertoire spécifique. The goal is operational: practices you can apply, not a diploma.

Contractual framework

Each session is covered by a professional training agreement (convention de formation professionnelle) signed before the start, setting out the objectives, the programme, the duration, the delivery arrangements and the agreed fee. The internal rules applicable to the session are handed to participants at the opening.

Certificate of attendance

A certificate of completion is handed to each participant at the end of the session. It states the objectives, the nature and the duration of the training, along with the results of the assessment of learning.

Accessibility and disability

Disability referent: Adrien Bouthet, contact@adrienbouthet.fr. Any situation requiring an adjustment (access to the premises, adaptation of the materials, of the pace or of the assessment arrangements) is examined during the framing phase, within 5 working days. If the adjustment exceeds our means, we refer to specialised resources (Agefiph, Cap emploi).

A project budget to keep

Book a free first call. We look at the budgets your project managers hold, the level of tracking already in place and the budget that will serve for the transposition, then we set the dates.

The matching service

Freelance IT project manager