I used to know someone who designed databases and IT systems for various government departments.
I asked him why all of the systems either failed or were vastly over time and budget?
His answer rang all too true:
"It's working with bloody civil servants! They design the specs for the system they want and give them to you. So, you design that, but then it turns out that the person who gave you the specs has moved, so now the person who took over his position says they are all wrong, and can we re-do it?
"Then he decides that he needs other people's input, so he organises meetings. Not to design the new specs, but to decide who should be on the committee to design the new specs.
"Of course, by this time it is already vastly over time and budget, but eventually they get the committee together and then after another delay they give you the new design for the specs. So you get on with it.
"But then several senior managers -who know nothing about computers or databases- decide they want to have an input and demand changes. Which you implement -after all, they ARE the customer- and very late and vastly over budget you trial the system. Which, because of all the changes and the bits that they asked to be added on, does not work properly.
"So you have to have teams of hardware and software engineers brought in, working out what conflicts have arisen.
And even at this stage the civil servants are still coming up with new pointless ideas for useless extra features!"
He was very, very cross about it, and the same thing happened on I think it was either 3 or 4 government IT projects he was involved in. Needless to say he bailed out and does not do them anymore!
