4 ms·
Ah, come on, it's not that hard. A bug is something that should be working according to the specification (or, if the specification is missing, according to co
by swombat 18y ago
Ah, come on, it's not that hard.
A bug is something that should be working according to the specification (or, if the specification is missing, according to common sense), but is not working. If you have a button labelled "print" and it doesn't print, that's not a feature request, it's a bug.
Feature requests are made up of enhancements and requirements.
An enhancement is an small, incremental and obvious improvement to an existing function/element that doesn't change the fundamental functioning of that function/element. If the print button is there and is working fine according to the spec but a user requests that it also prints the date at the top of the document, that's an enhancement.
A requirement is a wholly new piece of functionality that didn't exist before. If the print button is there, and it works fine, and the user requests that it should allow the user to select which pages to print before actually printing, that's a new requirement.
It's really not rocket science...
- swombat 18y agoAnd before people down-mod me because I forgot to mention it, the reason why Jeff is perceiving that something is horribly broken there is not because there's a problem with classifying what kind of "request" the user made. If your developers are in the habit of ignoring feature requests because they're not bugs, you need either new developers or a new project manager. "Work items" (whatever kind they are) should be implemented based on the value they add to the product, the company, the customers, etc. Bugs can be minor and requirements can be critical. In the case Jeff discusses, yes, it's a bug, because it should match the requirements, which presumably include providing customers with the tools to build quality Windows applications. Is it a critical bug? Depends on the point of view. From a developer point of view it's not critical, and they are right to ignore it from that narrow perspective. "Critical bug", in developer-speak, means "The sky will fall when someone clicks that button". However, it should be critical to the windows UI guidelines team and they should be the stakeholder pushing to get it implemented, on the basis that it makes them look like dunces. So the problem there is not about what you call the bug, it's about the fact that the windows UI guidelines team don't care enough (a fact more than obvious whenever I stare at a vista screenshot).
- snprbob86 18y ago"Bugs can be minor and requirements can be critical" Exactly, however "Feature requests" are always considered optional and "Bugs" are always pushed through triage. This distinction causes moderately important feature requests to be ignored while moderately important bugs are fixed. Jeff's point is that the distinction between bugs and feature requests has the unintended consequence of weakening the sorted order of the priorities of this middle range of work items. Additionally, I would argue that identifying something as a either a bug or feature request doesn't provide any value. Spend that energy identifying customer impact. If it doesn't provide any value and actually requires some effort, stop doing it.
- emmett 18y agoYou 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.