How could a popular company like Netscape release such crappy software a month before going IPO?
Of course this issue did get fixed and Netscape went on to fame and fortune – at least for a few years. But ten years later, I still remember thinking, “Netscape – you should be ashamed!” What’s the lesson? You only have one chance to make a good first impression. Believe me, I know! I have seen too many demos that ended in disaster. Software often has a conspicuous way of letting you know it is broken. But sometimes the problems can be more subtle, like when the software does not work in the way the user was expecting. Criticism from users can be hard to hear. Of course, there is no point in taking this criticism personally. Learn from your mistakes and always keep the benefits and end goals of your software in mind. If you have no specifications then it seems like a serious and robust QA process is impossible. And it probably is. But… What if you outsource your QA to a vendor that can work with you on-site to identify the major features and functions to be tested? Through a series
Related Questions
- Shemaroo is going to have its third animated release this year, so what is the strategy that the company is following when it comes to animation?
- We have a portable toilet company and are billing every 28 days, once a month. Can the Portable Toilet software bill this way?
- How could a popular company like Netscape release such crappy software a month before going IPO?
