Maintenance fraud

Asking for new functionality always means two things: first is to implement functionality and second is to take care about the new content. Content maintenance is always hardest part to negotiate between departments in organizations. Who will have the monkey on the back to take care about. Sounds easy but maintenance is always hard nut. Especially if it is related with revenue and costs. Here is the catch. If sum is not 100% clean, even in cents it is not OK, because one small difference could mean revenue or costs are wrongly placed. In other words big mistake might be hidden below surface and could be sign of wrongly placed millions.

In this light every new requirements could be carefully checked and mapped with other codes. There is no place for irregular care. It is regular and demanding care always checking is everything OK or not.

So once again, let us jump on begging, if someone asks for new products or services, marketing or other kind of specification should immediately specify and define code maintenance process, data steward. Especially, whose task it is and regular job. Otherwise might always finish in department that mostly looks like to should take care about it and with least negotiation power.

What is the risk?

Practice shows it could and up in hands of one man who could make local databases in access and through them to make uploads into databases. In this case it is one man show and his leave to another job could mean sudden drop in quality of reports, important reports.