Imagine the finance director of a mid-sized manufacturer. The board has approved a new enterprise system to link the warehouse, production and accounts. The budget is twelve million crowns, go-live in a year. At the first project meeting the supplier presents a plan with a ten per cent contingency. People around the table nod, because ten per cent sounds sensible.
Eight months in, the project is halfway. The supplier reports that the production customisation is more complex than expected. The warehouse wants its own screens. Accounts point out that data migrated from the old system does not reconcile. Each change is small and justified on its own. The finance director adds them up and finds the contingency was gone by the summer. At the next meeting he hears it is a normal delay and projects like this tend to slip. The weekly report still shows the project in green.
An average that reassures
Bent Flyvbjerg and Alexander Budzier of the University of Oxford examined 1,471 IT projects and published the results in Harvard Business Review in 2011.1 The average cost overrun was 27%. You can plan around that figure, which is what makes it treacherous.
Continue reading
Read the full article for free
Enter your email and the full article opens straight away. No payment, just a subscription to TORVAKO Insights.
- Full articles with all the sources they draw on
- Once a month, an overview of new articles and one story from practice
- You will be the first to receive TORVAKO study results
Already a subscriber? Enter your email and the article will unlock on this device too.