• Vera (unregistered)

    Stories like this always make me wonder which hurricane-in-human-disguise swept through and made them that scared of anything 'unpredictable.'

  • 516052 (unregistered) in reply to Vera

    Nothing so spectacular. They just probably had to do with regulators of some sort.

  • Tse (unregistered)

    The correct way to handle such a situation is to mention that an immediate update of the report is a feature required by key users and scoping it, so the business has to decide. The biggest issue is going over the decision makers' heads.

  • Roby McAndrew (unregistered)

    "If we don't do this we will fail" "Yes. We fail every time. It is 100% predictable"

  • (nodebb)

    A bureaucracy moves at the speed of its dullest most slothful member.

  • (nodebb) in reply to 516052

    This was absolutely the end product of financial regulations. Not that you don't want banks to be regulated! But the inevitable result is that financial companies have to tick whatever boxes the regulators insist they tick, and that leads to box-ticking becoming the goal. Tim C. thought his deliverable was a software feature for the customer, but the deliverable the customer needed MORE was all the artifacts they can use to prove to the regulator that this new piece of software was from a known source and properly vetted. As a new module it probably needed a new entry in a database of software, and that means paperwork showing how it was paid for, how it will be supported, how you'll replace it if the vendor is no longer viable, what risk it introduces to the company (inherently, if it breaks, and if it has flaws), who is responsible for managing it... "I whipped this up over the weekend in my hotel room" sounds to a bank IT manager like "I created a guaranteed audit failure for you!"

    So the real WTF is not understanding your customer's needs :D

Leave a comment on “It's all Part 1 of the Process”

Log In or post as a guest

Replying to comment #704617:

Log Out

« Return to Article