Back in 2004, Mike Cohn wrote an interesting article on requirements and agile development. Here is an interesting excerpt from the article:
[C]onsider the following requirements:It's revealing that a product satisfying the first alleged "requirements" specification (the series of "The product shall . . . ." statements) likely would fail miserably at addressing the user's real needs. The real requirements are to mow the user's lawn, and for it to be fast, easy, and comfortable for the user.
3.4) The product shall have a gasoline-powered engine.
3.5) The product shall have four wheels.
3.5.1) The product shall have a rubber tire mounted to each wheel.
3.6) The product shall have a steering wheel.
3.7) The product shall have a steel body.
By this point, I suppose images of an automobile are floating around your head. Of course, an automobile satisfies all of the requirements listed above. The one in your head may be a bright red convertible, while I might envision a blue pickup. Presumably the differences between your convertible and my pickup are covered in additional requirements statements.
But suppose that instead of writing an IEEE 830–style requirements specification, the customer told us her goals for the product:
* The product makes it easy and fast for me to mow my lawn.
* I am comfortable while using the product.
By looking at goals, we get a completely different view of the product: the customer really wants a riding lawnmower, not an automobile. These goals are not user stories, but where IEEE 830 documents are a list of requirements, stories describe a user’s goals. By focusing on the user’s goals for the new product, rather than a list of attributes of the new product, we can design a better solution to the user’s needs.
Via Jonathan Babcock.