requirements gathering

Writing requirements purely top-down or only bottom-up is risky to say the least. The devil's in the details, and those details are likely to be missed when working from a single direction. What if you could tackle your requirements from both directions by incorporating use cases and user centered design? Learn how balancing your approach to writing requirements can result in more detailed, pragmatic documentation.

Turn to The Last Word, where software professionals who care about quality give you their opinions on hot topics. This month, Karl Wiegers shares some common misperceptions about requirements.

Fashioning a new requirements method is an almost impossible task, given budget and time constraints. But that doesn't mean you have to be stuck with an ill-fitting process. Learn about seven alterations that almost any organization can make.

Chances are you won't be able to deliver on everything your customer wants. Asking good questions at the beginning of a project can help you determine where your customer wants to go. Although you may not be able to give them everything they want, if you are able to deliver the top ten things on a list of fifty items you've still delivered value. Keeping the lines of communication open is essential to helping you achieve your project goal.