Comments on: Writing Valuable Requirements http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/ Software product success. Thu, 18 Mar 2010 20:39:50 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: David Locke http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/comment-page-1/#comment-491335 David Locke Fri, 24 Apr 2009 02:11:05 +0000 http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/#comment-491335 Marketure does end up being translated into requirements. These are best associated with a persona, so they get implemented. The value of these requirements accrue to the company, rather than a customer. I do get your points. Thanks. Marketure does end up being translated into requirements. These are best associated with a persona, so they get implemented. The value of these requirements accrue to the company, rather than a customer.

I do get your points. Thanks.

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/comment-page-1/#comment-491331 Scott Sehlhorst Fri, 24 Apr 2009 01:53:32 +0000 http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/#comment-491331 @David - thanks for the question. There are really three elements to this one. First - don't write a requirement without having identified its value. If you don't know how valuable something is, you can neither prioritize it correctly or justify the expense of implementing it. "Don't know" can be replaced with "Can't estimate" if you must. Second - don't write a requirement that is not valuable to your target users. You're targeting specific markets / market segments / user personas with your product. If a capability provides no value to the users (or buyers) you are targeting, it has "no (meaningful) value." Third - value is not just absolute, it can also be relative (to other requirements that could be implemented). When you can quantify your estimates comparatively, you can use a cardinal scale for value (and ROI) measurement. When you can not, you have to use an ordinal scale. Ridiculous examples of requirement with "no value:" <ul> <li>The printer must color the dots in a braille book.</li> <li>The tricycle must allow the rider to measure their altitude.</li> <li>The accounting software must play mp3 files</li> </ul> @David – thanks for the question. There are really three elements to this one.

First – don’t write a requirement without having identified its value. If you don’t know how valuable something is, you can neither prioritize it correctly or justify the expense of implementing it. “Don’t know” can be replaced with “Can’t estimate” if you must.

Second – don’t write a requirement that is not valuable to your target users. You’re targeting specific markets / market segments / user personas with your product. If a capability provides no value to the users (or buyers) you are targeting, it has “no (meaningful) value.”

Third – value is not just absolute, it can also be relative (to other requirements that could be implemented). When you can quantify your estimates comparatively, you can use a cardinal scale for value (and ROI) measurement. When you can not, you have to use an ordinal scale.

Ridiculous examples of requirement with “no value:”

  • The printer must color the dots in a braille book.
  • The tricycle must allow the rider to measure their altitude.
  • The accounting software must play mp3 files
]]> By: David Locke http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/comment-page-1/#comment-490737 David Locke Mon, 20 Apr 2009 19:10:45 +0000 http://tynerblain.com/blog/2006/05/30/writing-valuable-requirements/#comment-490737 So give me an example of a requirement that provides no value. I realize that marketure requirements do not have any user/customer value, but they do have internal value. I just can't imagine an ordinary requirement that provides no value. If I had a requirement that didn't have any value, it would never get implemented. So give me an example of a requirement that provides no value. I realize that marketure requirements do not have any user/customer value, but they do have internal value. I just can’t imagine an ordinary requirement that provides no value.

If I had a requirement that didn’t have any value, it would never get implemented.

]]>