Writing Good Feature Requests

Feature requests, too, require careful composition. When you enter a feature request into the FogBugz database, you're saying one of two things:

• "This feature is part of the spec, and now it's your job."

• "I know no one thought of this earlier, but I think it's really, really important."

Any project that requires enough work to justify using FogBugz at all should have a formal, written specification. Specs are enormously important, because they represent the shared vision of how the product should work when it's finished. Developers refer to the spec to figure out how all the pieces fit together, testers use it to figure out what to test (and to see whether a particular piece of behavior is a bug or a feature), managers use it to help schedule to project, and so on. The product's spec should be a collective, comprehensive, up-to-date vision of the way that the product will work.

0 0

Post a comment