Comments on: Requirement Visualization: Mock-up & Wireframe Goodies http://practicalanalyst.com/2009/04/27/requirement-visualization-mock-up-wireframe-goodies/ Practical Insight for Business Analysts and Project Professionals Thu, 22 Jul 2010 11:35:32 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: JB http://practicalanalyst.com/2009/04/27/requirement-visualization-mock-up-wireframe-goodies/comment-page-1/#comment-6168 JB Wed, 29 Apr 2009 00:44:31 +0000 http://practicalanalyst.com/?p=1047#comment-6168 Good to see you again, Todd, and thanks for sharing the link. You're right. Good requirements are a must, and my idea isn't to replace the spec. doc, just to supplement it. Once enough requirements have been specified to enable the team to make some assumptions as to what the solution *might* or *could* look like, you can sanity check your requirements with the customer by taking a stab at a picture - or having your designer do it, as the case may be. As you draw out more requirements, the picture gets clearer; as the picture gets clearer, you tend to draw out the remaining requirements.. The idea is that when requirements are put in a visual context, your chances of getting the customer to actually review them increases (as opposed to the 70 page doc of "system shalls"), and the chances of them understanding them the way you intended them really skyrocket. 1 hour ago Good to see you again, Todd, and thanks for sharing the link. You're right. Good requirements are a must, and my idea isn't to replace the spec. doc, just to supplement it.

Once enough requirements have been specified to enable the team to make some assumptions as to what the solution *might* or *could* look like, you can sanity check your requirements with the customer by taking a stab at a picture – or having your designer do it, as the case may be. As you draw out more requirements, the picture gets clearer; as the picture gets clearer, you tend to draw out the remaining requirements..

The idea is that when requirements are put in a visual context, your chances of getting the customer to actually review them increases (as opposed to the 70 page doc of "system shalls"), and the chances of them understanding them the way you intended them really skyrocket. 1 hour ago

]]> By: toddpollock http://practicalanalyst.com/2009/04/27/requirement-visualization-mock-up-wireframe-goodies/comment-page-1/#comment-6161 toddpollock Tue, 28 Apr 2009 21:48:44 +0000 http://practicalanalyst.com/?p=1047#comment-6161 Another gem, Jonathan. I am currently deep in the battle of requirements versus wireframes. I feel like I have this debate once a year. I tried Balsamiq a while back thanks to a post by a buddy of mine (<a href="http://blog.websolvers.com/2009/01/web_site_wireframes.php" rel="nofollow"><a href="http://blog.websolvers.com/2009/01/web_site_wireframes.php</a>" target="_blank">http://blog.websolvers.com/2009/01/web_site_wiref... I thought it was a fantastic tool and we put it in front of a client. Ultimately, we stuck with good old requirements and let the mocks fall out. As brainstorming tools, I'm all for mocks. You simply have to have good requirements though, imo. Another gem, Jonathan. I am currently deep in the battle of requirements versus wireframes. I feel like I have this debate once a year. I tried Balsamiq a while back thanks to a post by a buddy of mine (<a href=”http://blog.websolvers.com/2009/01/web_site_wireframes.php” target=”_blank”>http://blog.websolvers.com/2009/01/web_site_wiref… I thought it was a fantastic tool and we put it in front of a client. Ultimately, we stuck with good old requirements and let the mocks fall out. As brainstorming tools, I'm all for mocks. You simply have to have good requirements though, imo.

]]> By: DougGtheBA http://practicalanalyst.com/2009/04/27/requirement-visualization-mock-up-wireframe-goodies/comment-page-1/#comment-6162 DougGtheBA Tue, 28 Apr 2009 18:08:49 +0000 http://practicalanalyst.com/?p=1047#comment-6162 Jonathan: I like the idea of visualizing, but constantly battling the tendency to provide the "How" as opposed to the "What" when gathering requirements really gets in the way many times. I'd like to hear your thoughts on managing this problem, which is exacerbated when putting prototyping of any kind on the table. Jonathan:

I like the idea of visualizing, but constantly battling the tendency to provide the "How" as opposed to the "What" when gathering requirements really gets in the way many times. I'd like to hear your thoughts on managing this problem, which is exacerbated when putting prototyping of any kind on the table.

]]> By: Jonathan Babcock http://practicalanalyst.com/2009/04/27/requirement-visualization-mock-up-wireframe-goodies/comment-page-1/#comment-8057 Jonathan Babcock Tue, 28 Apr 2009 06:34:13 +0000 http://practicalanalyst.com/?p=1047#comment-8057 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">New blog post: Requirement Visualization: Mock-up & Wireframe Goodies http://tinyurl.com/djff58</span></span> New blog post: Requirement Visualization: Mock-up & Wireframe Goodies http://tinyurl.com/djff58

]]>