OopsFinally, after more 50+ hour weeks than I care to think about, the current release of my company's software package is finally closed for development. Of course, it will be very interesting to see how the testing goes. It closed a week late, with the central lending project the largest and last one submitted, with 18 known issues, and still unstable, but it is formally closed. But that is not the real problem. The real problem is that with the financial industry regulations being changed in the 1st week of March for a July 1st implementation, we are now officially up the creek. Because we chose to implement an intermediate solution for last year's release of the software, that release cannot be updated to handle the latest regulatory changes. This has now turned the first release of this years software into a mandatory install for all of our clients, preferably by the end of July. It will be a most interesting testing cycle to watch, and more interesting to watch management deal with this absurd situation. If the testing goes bad, we have no fall back strategy in place. With hindsight, it is now plain to see that instead of patching last years software with an intermediate solution (one that did not involve and database changes) we should have issued an extra regulatory release of last year's software, with the final version of the code changes including the database changes for the regulatory changes as we then knew them. If we had done that early in this year, then these very late changes could have been addressed in that release as a patch.
In any case, it will be fun to watch.