Comments on: Writing Design-Free Requirements http://tynerblain.com/blog/2006/06/02/writing-design-free-requirements/ Software product success. Tue, 22 May 2012 20:46:27 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/06/02/writing-design-free-requirements/comment-page-1/#comment-512104 Scott Sehlhorst Thu, 30 Jul 2009 00:39:00 +0000 http://tynerblain.com/blog/2006/06/02/writing-design-free-requirements/#comment-512104 Thank you very much Roland! You're exactly right. This is even a pretty timely comment, since I've just started updating and rewriting the "rules of requirements" series. I really appreciate your point - very well made - and will be sure to avoid the same mistake in the future. Thanks, Scott Thank you very much Roland! You’re exactly right. This is even a pretty timely comment, since I’ve just started updating and rewriting the “rules of requirements” series. I really appreciate your point – very well made – and will be sure to avoid the same mistake in the future.

Thanks,

Scott

]]> By: Roland Renetseder http://tynerblain.com/blog/2006/06/02/writing-design-free-requirements/comment-page-1/#comment-512089 Roland Renetseder Wed, 29 Jul 2009 22:27:24 +0000 http://tynerblain.com/blog/2006/06/02/writing-design-free-requirements/#comment-512089 Dear author, I ended up on your page from hints on other pages and found myself struggling with all of the acronyms (e.g. MRD, PRD) which are used repeatedly without giving a clear definition. Only accidentally I found in another linked article an explanation that MRD stands for "Market Requirements Document" and by analogy infer that PRD then refers to the "Products Requirements Document". But in a set of articles about high quality requirements the assumption that any reader is familiar with the writer's acronyms is an unjustified assumption. Therefore in my personal perception a better practice would be to give at least the corresponding full term for each acronym at first use in the individual articles or otherwise provide a clear pointer to a glossary where all acronyms are listed in alphabetical order and explained once. Kind regards, Roland Dear author,
I ended up on your page from hints on other pages and found myself struggling with all of the acronyms (e.g. MRD, PRD) which are used repeatedly without giving a clear definition. Only accidentally I found in another linked article an explanation that MRD stands for “Market Requirements Document” and by analogy infer that PRD then refers to the “Products Requirements Document”. But in a set of articles about high quality requirements the assumption that any reader is familiar with the writer’s acronyms is an unjustified assumption. Therefore in my personal perception a better practice would be to give at least the corresponding full term for each acronym at first use in the individual articles or otherwise provide a clear pointer to a glossary where all acronyms are listed in alphabetical order and explained once.

Kind regards,
Roland

]]>