"A requirement specifies the least stringent condition that must hold to solve or avoid a prospect problem (problem that a prospective customer faces)."
Note that a requirement, under this definition:
- Is possible, in principle, to test.
- Does not specify a design or solution.
- Correlates unambiguously to a problem that a prospective customer faces.
5 comments :
Roger,
I've finally got round to commenting on your definition on my blog. Enjoy!
Agreed. A good requirement is a statement of the problem, that can be solved, and absent a design of how to solve it.
See my article "On Reqs and Specs" for more. http://www.pragmaticmarketing.com/publications/topics/09/on-reqs-and-specs/
We make this so complicated and yet it's simple. Thanks for the post.
I love the simplicity of this. Sometimes simplicity is the most difficult to achieve!
Thanks, Lisa and Cait. As Steve implied, product managers need to define the problem. The requirements simply specify the conditions that indicate the absence of the problem. Doing so - and not encroaching further into design - empowers designers to unleash their talents and creativity on crafting solutions.
Post a Comment