Comments on: Writing Good Requirements – The Big Ten Rules http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/ Software product success. Sat, 19 May 2012 12:04:06 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-910686 Scott Sehlhorst Mon, 30 Apr 2012 20:12:43 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-910686 Thanks - makes sense! Hopefully this was helpful for you! From a tester-working-with-customers point of view, I've had success getting people to keep a few ideas as separate (but both important): (1) testing to make sure the code is doing what the developer intended, (2) testing to make sure the code is doing what the requirements-writer intended, (3) testing to make sure the code is doing what the customer intended (even if the requirements-writer missed it), (4) testing to make sure that the product is delivering value to the customers (think of Ford's "faster horse" - customers don't always ask for what they need, or need what they ask for), (5) testing to make sure that the product is succeeding in the market. Each requires a different approach. Verifiable requirements really only tackle (2). Developers writing tests gets you (1). (3-5) come from getting the right requirements, not just getting the requirements (written) right (sic: correctly). Thanks again, Scott Thanks – makes sense! Hopefully this was helpful for you! From a tester-working-with-customers point of view, I’ve had success getting people to keep a few ideas as separate (but both important): (1) testing to make sure the code is doing what the developer intended, (2) testing to make sure the code is doing what the requirements-writer intended, (3) testing to make sure the code is doing what the customer intended (even if the requirements-writer missed it), (4) testing to make sure that the product is delivering value to the customers (think of Ford’s “faster horse” – customers don’t always ask for what they need, or need what they ask for), (5) testing to make sure that the product is succeeding in the market.

Each requires a different approach. Verifiable requirements really only tackle (2). Developers writing tests gets you (1). (3-5) come from getting the right requirements, not just getting the requirements (written) right (sic: correctly).

Thanks again,

Scott

]]> By: mj http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-910101 mj Mon, 30 Apr 2012 13:30:24 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-910101 Yes, yes.... I guess I was to quick. Verifiable is the right word to use... I am a tester and like to use the word "testable" to customers that is not very advance. I am trying to define for a customer how he should write the requirements and searching the Internet for stuff like this to send him, so I did not read everything word by word... In my world you verify code but the requirements should be verifiable... You cannot verify requirements because you have nothing to compare it to? but do not listen to me, because this is just me philosophizes and I am very new in this world... Yes, yes…. I guess I was to quick. Verifiable is the right word to use… I am a tester and like to use the word “testable” to customers that is not very advance. I am trying to define for a customer how he should write the requirements and searching the Internet for stuff like this to send him, so I did not read everything word by word…

In my world you verify code but the requirements should be verifiable… You cannot verify requirements because you have nothing to compare it to? but do not listen to me, because this is just me philosophizes and I am very new in this world…

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-910065 Scott Sehlhorst Mon, 30 Apr 2012 13:09:45 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-910065 Hey mj, thanks for the comment and welcome to Tyner Blain! That's where I was going with "verifiable" - I used <i>verify</i> instead of <i>test</i>, since requirements "verification" is a pretty consistently used term with companies I've worked with. When I was a developer, I always thought of it as "testable", but once I moved into requirements-authoring, I saw that people thought of it as "verifiable." "Testing", I think, also carries a bit of a connotation of metrics versus measurement. As an example, you can absolutely "test" or "verify" that the system must respond in 20 ms. Either word works. But it feels more comfortable to "verify" that net-promoter score has risen, or that market share has increased. Yes, you can "test" that stuff - they are synonyms after all, but people outside of "write the code" land seem to gravitate towards verify. Does that resonate? Or should I consider changing the <i>title</i>? If you read the article, it should be clear - but maybe a better title would be more effective? Hey mj, thanks for the comment and welcome to Tyner Blain!

That’s where I was going with “verifiable” – I used verify instead of test, since requirements “verification” is a pretty consistently used term with companies I’ve worked with. When I was a developer, I always thought of it as “testable”, but once I moved into requirements-authoring, I saw that people thought of it as “verifiable.”

“Testing”, I think, also carries a bit of a connotation of metrics versus measurement. As an example, you can absolutely “test” or “verify” that the system must respond in 20 ms. Either word works. But it feels more comfortable to “verify” that net-promoter score has risen, or that market share has increased. Yes, you can “test” that stuff – they are synonyms after all, but people outside of “write the code” land seem to gravitate towards verify.

Does that resonate? Or should I consider changing the title? If you read the article, it should be clear – but maybe a better title would be more effective?

]]> By: mj http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-909665 mj Mon, 30 Apr 2012 10:39:25 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-909665 Testable? Testable?

]]> By: Driving down – product requirements « Life As A System http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-852877 Driving down – product requirements « Life As A System Sat, 07 Jan 2012 21:45:19 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-852877 [...] lot can be said about writing good design requirements (in fact, much has been written about it), and there are some several guidelines.  I’ll get more into those in [...] [...] lot can be said about writing good design requirements (in fact, much has been written about it), and there are some several guidelines.  I’ll get more into those in [...]

]]> By: DIEGO KAMINKER http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-819237 DIEGO KAMINKER Thu, 06 Oct 2011 04:14:34 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-819237 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @johnmoehrke: Here is my contribution to #HITstd - Write Good Requirements http://t.co/0sPhBllq #MU writers should read! LOL! #HITstd</span></span> RT @johnmoehrke: Here is my contribution to #HITstd – Write Good Requirements http://t.co/0sPhBllq #MU writers should read! LOL! #HITstd

]]> By: Keith W. Boone http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-819229 Keith W. Boone Thu, 06 Oct 2011 03:03:34 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-819229 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @johnmoehrke: Here is my contribution to #HITstd - Write Good Requirements http://t.co/0sPhBllq #MU writers should read! LOL! #HITstd</span></span> RT @johnmoehrke: Here is my contribution to #HITstd – Write Good Requirements http://t.co/0sPhBllq #MU writers should read! LOL! #HITstd

]]> By: johnmoehrke http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-819227 johnmoehrke Thu, 06 Oct 2011 02:58:14 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-819227 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Here is my contribution to #HITstd chat - Write Good Requirements http://t.co/QB4x1gST</span></span> Here is my contribution to #HITstd chat – Write Good Requirements http://t.co/QB4x1gST

]]> By: Passionate Requirements | devblogging.com http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-805083 Passionate Requirements | devblogging.com Thu, 21 Jul 2011 06:18:49 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-805083 [...] is the latest in the Big Ten Rules of Writing Good Requirements series, and rather than extending, it replaces the previous article on writing passionate [...] [...] is the latest in the Big Ten Rules of Writing Good Requirements series, and rather than extending, it replaces the previous article on writing passionate [...]

]]> By: Alberto Manuel http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-628025 Alberto Manuel Wed, 13 Oct 2010 00:17:12 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-628025 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Writting better requirements . Atomic. #EA #BPR #BPM http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/</span></span> Writting better requirements . Atomic. #EA #BPR #BPM http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/

]]> By: brainmates – product management people » Blog Archive » Requirements Check List http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-623624 brainmates – product management people » Blog Archive » Requirements Check List Thu, 16 Sep 2010 04:23:26 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-623624 [...] was also influenced by Scott Sehlhorst who wrote Writing Good Requirements, The Big Ten Rules . VN:F [1.9.3_1094]please wait...Rating: 0.0/5 (0 votes [...] [...] was also influenced by Scott Sehlhorst who wrote Writing Good Requirements, The Big Ten Rules . VN:F [1.9.3_1094]please wait…Rating: 0.0/5 (0 votes [...]

]]> By: Jennifer Banzon http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-623458 Jennifer Banzon Wed, 15 Sep 2010 06:26:47 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-623458 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @brainslink: 2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b #baot</span></span> RT @brainslink: 2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b #baot

]]> By: Cloudspace http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-623350 Cloudspace Tue, 14 Sep 2010 22:35:44 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-623350 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @brainslink: 2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b</span></span> RT @brainslink: 2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b

]]> By: Vin D'Amico http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-623351 Vin D'Amico Tue, 14 Sep 2010 22:31:06 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-623351 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b</span></span> 2 good posts on writing good software requirements: http://dld.bz/vC5a and http://dld.bz/vC5b

]]> By: David Hawks http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-617406 David Hawks Wed, 25 Aug 2010 22:18:08 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-617406 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Stumbled across a nice set of articles on writing good requirements by @sehlhorst http://bit.ly/1sxvrV</span></span> Stumbled across a nice set of articles on writing good requirements by @sehlhorst http://bit.ly/1sxvrV

]]> By: vishal sodani http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-617136 vishal sodani Tue, 24 Aug 2010 18:57:45 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-617136 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/</span></span> http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/

]]> By: brainmates http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-616894 brainmates Mon, 23 Aug 2010 06:53:52 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-616894 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">[ACT] Reading @sehlhorst http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/ - will be applying his rules</span></span> [ACT] Reading @sehlhorst http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/ – will be applying his rules

]]> By: Vlad Nemes http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-616237 Vlad Nemes Thu, 19 Aug 2010 18:54:10 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-616237 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Writing Good Requirements - The Big Ten Rules: Shared by vlad differentiating ourselves from the competition is... http://bit.ly/aY7F2j</span></span> Writing Good Requirements – The Big Ten Rules: Shared by vlad

differentiating ourselves from the competition is… http://bit.ly/aY7F2j

]]> By: Sandeep Bhat http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-615007 Sandeep Bhat Wed, 11 Aug 2010 10:32:48 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-615007 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @coombes: http://bit.ly/aVYJNx - Writing good (marketing) requirements. Essential reading for me at the moment.</span></span> RT @coombes: http://bit.ly/aVYJNx – Writing good (marketing) requirements. Essential reading for me at the moment.

]]> By: coombes http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/comment-page-1/#comment-614915 coombes Tue, 10 Aug 2010 21:27:44 +0000 http://tynerblain.com/blog/2006/05/25/writing-good-requirements-the-big-ten-rules/#comment-614915 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">http://bit.ly/aVYJNx - Writing good (marketing) requirements. Essential reading for me at the moment.</span></span> http://bit.ly/aVYJNx – Writing good (marketing) requirements. Essential reading for me at the moment.

]]>