Comments on: Are people reading your requirements? A blogversation. http://tynerblain.com/blog/2006/01/11/are-people-reading-your-requirements-a-blogversation/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/01/11/are-people-reading-your-requirements-a-blogversation/comment-page-1/#comment-82 Scott Sehlhorst Wed, 11 Jan 2006 16:29:28 +0000 http://tynerblain.com/blog/2006/01/11/are-people-reading-your-requirements-a-blogversation/#comment-82 Thanks Jerry for the comments. I completely agree about the importance of crafting a targeted message. Otherwise, it's easy for overworked people to turn on their "filters" and perceive any broad distribution email as spam (unless it's from their boss). Thanks Jerry for the comments. I completely agree about the importance of crafting a targeted message. Otherwise, it’s easy for overworked people to turn on their “filters” and perceive any broad distribution email as spam (unless it’s from their boss).

]]> By: Jerry Aubin http://tynerblain.com/blog/2006/01/11/are-people-reading-your-requirements-a-blogversation/comment-page-1/#comment-81 Jerry Aubin Wed, 11 Jan 2006 15:11:43 +0000 http://tynerblain.com/blog/2006/01/11/are-people-reading-your-requirements-a-blogversation/#comment-81 I love the recommendation (from #1 above) of asking about a specific part of the requirements document. I know from experience that this can be a powerful testing mechanism to see if folks are really paying attention. If you are feeling particularly frisky (and have a very solid relationship with the stakeholders of course) you can even throw out something fictitious and totally off the wall to see how people react. You know you're in serious trouble if people just nod and say "that looked fine." I would also suggest using this "make sure you look at specific area XYZ" technique when the requirements are originally sent out for review. As a Product Manager, I always try to think of myself as marketing the importance of the requirements process to the stakeholders I interface with. "Positioning" is Marketing 101 and I think that a well-crafted, customized message to each stakeholder highlighting "what's in it for them" by reading the requirements can go a long way towards stimulating actual review of the documentation. A critical part of this message should be a pointer for each recipient directing them to the key area(s) that he or she should start with. I love the recommendation (from #1 above) of asking about a specific part of the requirements document. I know from experience that this can be a powerful testing mechanism to see if folks are really paying attention. If you are feeling particularly frisky (and have a very solid relationship with the stakeholders of course) you can even throw out something fictitious and totally off the wall to see how people react. You know you’re in serious trouble if people just nod and say “that looked fine.”

I would also suggest using this “make sure you look at specific area XYZ” technique when the requirements are originally sent out for review. As a Product Manager, I always try to think of myself as marketing the importance of the requirements process to the stakeholders I interface with. “Positioning” is Marketing 101 and I think that a well-crafted, customized message to each stakeholder highlighting “what’s in it for them” by reading the requirements can go a long way towards stimulating actual review of the documentation. A critical part of this message should be a pointer for each recipient directing them to the key area(s) that he or she should start with.

]]>