Yep, typical consultancy behaviour
@AceRimmer - exactly. I had the misfortune of working on one of the UK government IT projects (that has made the news in the past) outsourced to a large US company subsequently bought by another large US company. I lasted 7 months and could not take the "deliberate entrapment" of the UK government users in defining wrong requirements: no advice was given, and if it was seen they were going down the wrong route, it was actively encouraged and dissentors (like me) who tried to do a good job were 'silenced' or 'disposed of' being easy-come / easy-go contractors. After the UK govt. specified the sub-optimal requirement, it was implemented. Ta da ... QED ... instantaneous further change request amidst accusations of not specifying requirements properly. This article sounds like identical behaviour of actually adding no value to the process and instead actively encouraging 'expensive mistakes' to be made actively or passively. The saddest thing is there were a few whistle-blowers, who instead of getting government thanks ... got axed making me think that there were a few insiders benefitting from the contract award. I wonder why it took so long to get to this point in Australia unless the same thing was happening: some people in government were invested in this and also chose to ignore the obvious abuses?