A lot happens before ideas become solutions.
At ElixWare we want to bring you more than just great, affordable software. We want to let you know how and why we do what we do.
Our Ruminations blog will bring you insights into how we got here and some of the things we consider when trying to help you run your business. We hope it gives you a better understanding of how we strive to better serve your needs.
I can't say we've never had days like this, but today seemed to have something extra. And the truth is we expect a few more of these in the not too distant future.
Sometimes part of a project's requirements is a commitment to ensure compatibility with an existing system or design. In those instances, it's important that the client does not update or change this target - especially without telling us.
Fortunately for us we accidentally stumbled on the changes before we were done with the compatibility portion of the project. Unfortunately, we were told that the situation could "remain fluid". This means we wait until we're told about (or stumble upon) any future modifications.
So, what do we do? We try to have it both ways. On one hand we try to pay close attention to any of the changes we can find. And we do the basic analysis on what it will take to accommodate the most recent modifications. On the other hand, we try not to focus too much on what has changed because any work we do could be simply a waste of time (once things change again).
There are more parts to the project than the compatibility portion. And we need to pay close attention to all of the project's requirements as we work through our deliverables. Generally speaking, if a client will change things without telling us once, they will do it again (and again).
In the end, we're familiar enough with the client to try to avert foreseeable problems. And they are familiar enough with us to know that we'll adapt as necessary, make sure the project gets completed and keep them from having to listen to the same soundtrack we had today.