[thewellis2]

I recall working on a project a few years ago that had it in place. The end client was a hundred year old company, with bricks and mortar stores, that needed a boring, stable solution that had several key features. They would take only the older version that we built for the escrow, so that if things went sour they had a workign solution that they would have the source-code for that could be given to another company.

On the one hand it was a pain to work towards, as the requirements had little immediate value (new features needed lengthy documentation, lots of features had to be stripped out, long (manual) test checklists, etc) but on the other hand, it got you thinking about how to build software that would need to last longer than the company you're in. Made me realise that feature creep/bloat was what was holding the product back, not the Next Big Thing(tm).