How do I prioritize features versus bugs?

As long as it is just demos, prioritize bug fixes solely around the demo path – other bugs may need to wait

If the demo is to be left behind to be used by users not working on the project, then when the features are at MVP level, bugs must be taken care of.

Of course, if you don't fix the bugs, eventually the tech debt will catch up with you - especially if you are hacking your way to a shippable product. At some point you should stop and ask whether the time has come for you to harden the code for productization. At that point - you should prioritize dealing with bugs over new features, to make sure you ship a quality product that delights your customers. 

Was this article helpful?
0 out of 0 found this helpful

      This website and all posts and content are intended for educational purposes only and for no other purposes. This website does not and is not intended to provide legal, financial or tax related advice. Although we take great care to make sure that all of our information is accurate and useful for it intended educational purposes, if you have a specific issue for which you need actionable advice, please come to the Martin Trust Center in person to speak to one of our Entrepreneurs in Residence (EIR) or consult a licensed attorney or other professional. Despite the backgrounds and qualifications of our staff, mentors, lecturers, authors, EIRs and speakers no attorney-client, advisor, or other confidential/privileged relationship exists or will be formed between you and the Martin Trust Center or the Massachusetts Institute of Technology. Under no circumstances should any content be relied upon in making any decisions that could have any financial or legal impact(s).
Have more questions? Submit a request


Powered by Zendesk