2 ms·
You presume that your requirements are complete and known. Often the reason that something like the font issue Jeff talks about happens is that there is no spec
by emmett 18y ago
You presume that your requirements are complete and known. Often the reason that something like the font issue Jeff talks about happens is that there is no spec. Is it a bug or a feature if the spec doesn't mention the question? In theory, "bugs are when behavior doesn't match spec" is an easy rule to apply, but in practice it's often not obvious what the spec is.
- swombat 18y agoIf there is no spec about it, it's a requirement. But requirements are no less important than bugs. The concept that "new requirements are extra and therefore should be discounted" is a fallacy of the outsourcing model. New requirements often point out things that were missed from the initial requirements gathering, and in many ways are more critical than most bugs.