Tips for Discovering Requirements
By Bob Cunha
In the world of software development, it is well known that “good” requirements are needed to deliver a quality product and achieve customer satisfaction. The most common reason for software project failure is attributed to requirements issues – badly defined, not stated correctly, changing requirements, etc.
Requirements are not simply out there waiting to be collected. Instead, it is an investigation process whereby requirements need to be discovered, examined, and molded. The discovery process is more of an art than a science, and certainly experience with this process is a big factor in knowing how to best discover requirements. This article offers seven tips on requirements investigation to help discover and define “good” requirements.
Bob Cunha is an independent consultant specializing in business systems analysis and project management
| Attachment | Size |
|---|---|
| Tips for Discovering Requirements.pdf | 138.46 KB |
Great advice
I really enjoyed your article, Bob. You offer great advice for eliciting 'excellent" requirements.
I especially appreciated the recommendation that people first need to define the terms used for requirements. It can be very painful when different team members are not in sync with what is going to be elicited, how it will be presented, and to what level of detail.