How many change orders did you have for the last building that you designed?
Quite a few but in 33 years never had a single claim for Errors and Omissions though I payed dearly for Liability Insurance all those plus a few years.
Also note that all change orders were completed before the delivery of the building to users. In this case we can only compare Fast-track construction to software development were construction starts before the final drawings are completed, but in this case also all but minor punch list items are resolved before delivery to the end user.
Note that building contract documents including specs are nothing like what is given to any software development team. Strict waterfall development was not natural for the industry and went out of fashion a decade ago.
This is Agile software development which is more fluid. Final requirements are admittedly not fully understood when the first release is made, and continue to evolve, thus the requirement for a customer feedback loop and daily team coordination is highly valued, ie: the scrum.
It is like designing a buildings HVAC system when 1/2 the plumbing is installed but the second half is not known. Software development is not easy and is almost always late, and over budget.
Now that said; It is clear we have issues here, large ones, from "Coming Soon" to the latest "patch/fix/ "oops Sorry" That one is more like installing toilets for a thousand end users to use and finding out only after it is backing up because the end of the sewer pipe was caped by the contractor (developer) while trying to complete a change order to replace a faulty ATM machine. I doubt it was stated in the change order/"Hotfix" cap the public toilets in the stadium during a tournament. This is not a design issue but an OPPS not caught during hot fix testing by QA.
But who would test the toilets after a replacement of a bad ATM? A well managed development team with automated testing.
PS: You appear to have an inside track on the processes inside Innogames. How is that?