The quality dilemma is basically two fold:
- Build bad software (low quality) and no one will want to buy/use it.
- Spend too much time on quality measures and no one gets to buy/use it because it either costs too much, or is still being worked on.
The issue is how to find a proper middle ground where your first users don’t feel like beta testers, but can still afford the software and have it come out in time to beat your competitors.
Therefore you must be able to build something that is “good enough” but how is that to be defined?
Apple is notorious for building systems which lack features, but are good enough because they are not too buggy (generally).
While some people worry about the cost of quality, they often forget to ask what is the price of poor quality.
The Software Quality Dilemma was originally found on Access 2 Learn
