Question 5: How will I make changes or introduce enhancements/new features & how much will it cost?

Hi, Richard Schreiber, the Software Whisperer. And today we're going to talk about a frequently asked question that I get often, which is, once I go live with my software, what do I do if I have new features or enhancements that I want to put into the mix? And what's the best way to go about that? Well, you're going to have inevitably new enhancements and features and maybe even some bug fixes once you go live. But for enhancements, the best tool that you can use to track and approve those changes is called a change order. And within that change order, though, you need to identify whether that change is a nice to have or a must have. And a must have will usually come with a higher level of priority, because the one thing you want to be careful of is once you go live, all of those nice to haves that you put in some parking lot somewhere, you don't want to start introducing those at additional cost. Once you go live, you must always be thinking about your return on investment for the software. So. But one final thing that comes into play when you're considering a change is, or even a defect, is there a workaround that could be implemented without resulting in software programming costs? That's something you want to consider, too, especially in the case of edge cases, which we spoke about earlier. Those are those rare, unusual instances that happen, unusual circumstances that bring them up, but sometimes they can be really problematic. Does it make sense to spend all this money on programming to fix those rare edge cases? Or is it something that you can resolve with a workaround or even tolerate the bug and just fix it after the fact? So again, Richard Shriver, the Software Whisperer, keep asking questions.