3 ms·
If you're developing something novel and it's not deployed as it's completed you risk a competitor beating you to market. As well as this, the time between havi
by _AzMoo 8y ago
If you're developing something novel and it's not deployed as it's completed you risk a competitor beating you to market. As well as this, the time between having a product or feature complete and ready for release equates to lost revenue. The ideal is to have all aspects of the project completed and ready for deployment (actual feature, supporting documentation, training materials, marketing campaigns and materials, etc.) at the same time to maximise possible revenue.
- flukus 8y ago> If you're developing something novel and it's not deployed as it's completed you risk a competitor beating you to market. If you're competitor is imminently releasing a competing product then what you're working on isn't really novel. It would also be potentially patentable if it really was novel, which would grant you a monopoly on the space. > As well as this, the time between having a product or feature complete and ready for release equates to lost revenue. What's the lost revenue from releasing a buggy product? What's the lost revenue if your competitors are about to release a working one? What's the lost revenue from your developers jumping ship and all the related turn over costs? Some of those mistakes could sink the product/business entirely. > to maximise possible revenue. You agree that maximizing revenue at the expense of everything else isn't the goal don't you? If that's all that mattered then development would be outsourced to a third world country to save on expenses. But we've mostly learned no to do that because despite promising revenue gains they lead to several bad outcomes in the short and long term, pushing hard deadlines is no different.