<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How and why to do requirements walk-throughs</title>
	<atom:link href="http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/</link>
	<description>Advance Your Business Analysis Career</description>
	<lastBuildDate>Thu, 09 Feb 2012 00:08:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Laura Brandenburg</title>
		<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/comment-page-1/#comment-10145</link>
		<dc:creator>Laura Brandenburg</dc:creator>
		<pubDate>Fri, 05 Aug 2011 18:01:17 +0000</pubDate>
		<guid isPermaLink="false">http://clearspringanalysis.wordpress.com/?p=59#comment-10145</guid>
		<description>Hi Bruce,
It really depends on your sales process and what&#039;s committed to in the sale. If you are committing to a schedule, budget, and requirements as part of closing the sale, than a requirements sign-off would be appropriate. But then how would your organization be compensated for all the requirements work you&#039;ve done, if it&#039;s considered part of sales?</description>
		<content:encoded><![CDATA[<p>Hi Bruce,<br />
It really depends on your sales process and what&#8217;s committed to in the sale. If you are committing to a schedule, budget, and requirements as part of closing the sale, than a requirements sign-off would be appropriate. But then how would your organization be compensated for all the requirements work you&#8217;ve done, if it&#8217;s considered part of sales?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Brandenburg</title>
		<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/comment-page-1/#comment-10144</link>
		<dc:creator>Laura Brandenburg</dc:creator>
		<pubDate>Fri, 05 Aug 2011 17:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://clearspringanalysis.wordpress.com/?p=59#comment-10144</guid>
		<description>Well, if the technical requirements are in the specs, then they would be included in the walk-through. Sometimes in order to validate the requirements, some technical discussion is required. If your implementation SME is an approver of the requirements, they need to ensure those requirements are implementable as part of sign-off. This may require some technical discussion. As the BA you can decide whether to allow/encourage that discussion in your walk-through meetings or ask that the technical SMEs schedule that discussion before the meeting and come prepared to sign-off. Either way, if they are negotiating requirements vs. implementation constraints, you will probably want to be involved in the conversation to ensure the business needs are represented.</description>
		<content:encoded><![CDATA[<p>Well, if the technical requirements are in the specs, then they would be included in the walk-through. Sometimes in order to validate the requirements, some technical discussion is required. If your implementation SME is an approver of the requirements, they need to ensure those requirements are implementable as part of sign-off. This may require some technical discussion. As the BA you can decide whether to allow/encourage that discussion in your walk-through meetings or ask that the technical SMEs schedule that discussion before the meeting and come prepared to sign-off. Either way, if they are negotiating requirements vs. implementation constraints, you will probably want to be involved in the conversation to ensure the business needs are represented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/comment-page-1/#comment-10125</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Thu, 04 Aug 2011 20:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://clearspringanalysis.wordpress.com/?p=59#comment-10125</guid>
		<description>Laura,
I work for an SaaS company that usually has the Statement of Work signed off before any business requirements are discussed.  Our product is normally stock, but I&#039;ve been a few projects now where its cowboy coding and the client asking for changes long into the process.  Is this type of meeting better prior to the close of the sales process, so as to capture in the SOW, or immediately after?

Thanks, 
Bruce</description>
		<content:encoded><![CDATA[<p>Laura,<br />
I work for an SaaS company that usually has the Statement of Work signed off before any business requirements are discussed.  Our product is normally stock, but I&#8217;ve been a few projects now where its cowboy coding and the client asking for changes long into the process.  Is this type of meeting better prior to the close of the sales process, so as to capture in the SOW, or immediately after?</p>
<p>Thanks,<br />
Bruce</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kai</title>
		<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/comment-page-1/#comment-10124</link>
		<dc:creator>kai</dc:creator>
		<pubDate>Thu, 04 Aug 2011 20:17:43 +0000</pubDate>
		<guid isPermaLink="false">http://clearspringanalysis.wordpress.com/?p=59#comment-10124</guid>
		<description>Oh ok thanks. I guess i was trying o see if you discuss both functional and technical in a walkthrough</description>
		<content:encoded><![CDATA[<p>Oh ok thanks. I guess i was trying o see if you discuss both functional and technical in a walkthrough</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Brandenburg</title>
		<link>http://www.bridging-the-gap.com/requirements-walk-thoughs-just-do-it/comment-page-1/#comment-10121</link>
		<dc:creator>Laura Brandenburg</dc:creator>
		<pubDate>Thu, 04 Aug 2011 19:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://clearspringanalysis.wordpress.com/?p=59#comment-10121</guid>
		<description>Hi Kai,
This question is addressing a completely different topic, as you are asking what requirements you should include in your specs. I&#039;ll add this one to the Ask a BA list and see if we can&#039;t get an author to answer it for you. Some more context would help. If you have a chance please email us with some more context here: http://www.bridging-the-gap.com/enewsletter-sign-up/ask-a-business-analyst/

Thanks,
Laura</description>
		<content:encoded><![CDATA[<p>Hi Kai,<br />
This question is addressing a completely different topic, as you are asking what requirements you should include in your specs. I&#8217;ll add this one to the Ask a BA list and see if we can&#8217;t get an author to answer it for you. Some more context would help. If you have a chance please email us with some more context here: <a href="http://www.bridging-the-gap.com/enewsletter-sign-up/ask-a-business-analyst/" rel="nofollow">http://www.bridging-the-gap.com/enewsletter-sign-up/ask-a-business-analyst/</a></p>
<p>Thanks,<br />
Laura</p>
]]></content:encoded>
	</item>
</channel>
</rss>

