I've been struggling in a peculiar situation since a while ago and would like your inputs on it. In our project (which is a maintenance project), there are some tasks that are done from time to time (on a weekly basis) and, although simple, needs to be done carefully to avoid the usage of wrong information.
However, there are some cases where a couple of lower level fellows repeatedly commit the same mistakes, over and over.
- This task itself is fairly simple (check the data in an Excel Spreadsheet, compare what is currently in place in the database, generate the inserts based on Excel data)
- It's extensively documented and
- I've done so many meetings to openly discuss about these very same issues that I lost my count.
- this specific task is a kind of 'special copy and paste' where some SQL insertions are generated (for the sake of avoiding some heart attacks, this process is being automated)
- This task is in place for over one year, and we had at least one every month (usually a lot more)
I know such routine processes are boring, but still one needs to understand (and I've reinforced it n times) that any information being changed in production, needs to be done carefully.
As of now, we have some higher level peers reviewing the data (and in most of the cases, raising flags), which is a waste of efforts... but that's the only solution we found so far to avoid bogus data going live.
How would you deal with such cases?