Near the completion of a software project, stakeholders are full of new ideas. Recently, I’ve had a few conversations with clients who wanted to add more features in the last stage of software development. Not bugs but new ideas. My counsel is always the same, if it’s not critical to the current functions, don’t stop the launch.
It’s inevitable that new ideas come to mind. It’s a new tool and because the process of building custom software brings a lot to mind. Custom software can open up possibilities never envisioned. That’s good. It’s one of the benefits of building an application that fits your business or process exactly. You instantly see new ways to leverage the data you have. You see ways to fix other nagging problems and realize a report you’ve always wanted is within reach.
The consequences of holding the launch for these new ideas include:
- If you can gain benefit from the current software phase, delaying it becomes a cost. If you can save 10 man hours/week, delaying the launch is a loss.
- Delayed launches have a demoralizing effect on the team. Each missed deadline makes the project seem like it will never end.
- Slipery slope. If you can hold the entire project because you want one more report, you loose control to every new idea.
- Late addons usually don’t go through the same design and review process. Everyone just assumes you can slip it. Doing so can cause more revisions, more testing, and unintended consequences that lead to more changes.
Custom software is never perfect because, by the time you reach the end, you’ve had time to think of new ideas. You don’t have to stop development just because you’re launching. Custom software grows with and around your company so let it. If you have new ideas, start planning so future versions are bound to come up.
Michael
Yes, you are right. Publication fo the product should be asap. New features are for 2-3 clients, but the product is for 1000 clients. Sure need to be carefully with bugs
Sergey