• David.Poole - Tuesday, February 27, 2018 12:29 AM

    They have their uses but in my experience are rarely driven by requirements.  The ones I've seen tend to be massively over engineered and have been put in place by people desperately trying to 2nd guess what the customer needs vs the inadequate statement of what they want.  Failure to 2nd guess correctly results in the project being deemed ITs failure for not satisfying the NSRs (Non-Stated Requirements) that were assumed to be so obvious that they weren't specified

    Staying with the sad topic of blame apportionment (!) we have implemented a few audits where experience showed that users denied having changed whatever it was and the existence of a table, that could demonstrate when and who and what was done, has rebalanced the conversation beautifully 🙂 
    More neutrally, we find that when users know changes are tracked, more care is often taken, which is generally a good thing.