Sometime software projects are frustrating. The #requirement spec is bad, we propose #agile development, the customer agrees, we built features that don't exist in the spec because in an agile dev process the real need is discovered.

Close to the end of the project the customer claims that agile was our idea and he will not reduce the amount of features or pay for the agile built extra features, but he is waiting for everything in the spec. Result: our team is deeply offended, motivation goes down.

Because of the contract we will have to deliver the spec, but we will remove the agile built extra features. What a drag! Last try to fix this mess will be the steering committee mid of August. Keep your fingers crossed that we will achieve an agreement ....

What's the reasoning removing already build features? Maintenance aspects? From a social point of view, I'd probably would keep them.

I understand, but they have treated us so badly that it is not possible to be nice - leaving the already built features in there would mean that we accept that the whole thing was our problem and the other side did everything right.

Of course we do not remove those features. They are just not visible anymore.....