<?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"
	>
<channel>
	<title>Comments for Webster &amp; Associates LLC</title>
	<atom:link href="http://bfwa.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://bfwa.com</link>
	<description>We can help.</description>
	<pubDate>Sun, 12 Oct 2008 16:29:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on &#8220;Inside-Out&#8221;: IEEE presentation in Longmont (09/02/08) by Slides from IEEE Reliability Society presentation : Webster &#38; Associates LLC</title>
		<link>http://bfwa.com/2008/08/26/inside-out-ieee-presentation-in-longmont-090208/#comment-74</link>
		<dc:creator>Slides from IEEE Reliability Society presentation : Webster &#38; Associates LLC</dc:creator>
		<pubDate>Thu, 11 Sep 2008 16:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?p=79#comment-74</guid>
		<description>[...] As mentioned previously, I spoke last week at the Denver IEEE Reliabilty Society chapter meeting on an SQA-centric view of software development. I plan to develop this into a full-blown articles (or posting), but in the meantime, here is the slide presentation (PPT, 340KB) I used. Feel free to ask questions. ..bruce..   Bookmark this story: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] As mentioned previously, I spoke last week at the Denver IEEE Reliabilty Society chapter meeting on an SQA-centric view of software development. I plan to develop this into a full-blown articles (or posting), but in the meantime, here is the slide presentation (PPT, 340KB) I used. Feel free to ask questions. ..bruce..   Bookmark this story: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfalls by Webster &#38; Associates LLC</title>
		<link>http://bfwa.com/pitfalls/#comment-73</link>
		<dc:creator>Webster &#38; Associates LLC</dc:creator>
		<pubDate>Fri, 22 Aug 2008 16:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?page_id=57#comment-73</guid>
		<description>[...] Pitfalls [...]</description>
		<content:encoded><![CDATA[<p>[...] Pitfalls [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfall: Misjudging relative costs by taskguru</title>
		<link>http://bfwa.com/2008/06/09/pitfall-misjudging-relative-costs/#comment-70</link>
		<dc:creator>taskguru</dc:creator>
		<pubDate>Wed, 11 Jun 2008 05:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?p=62#comment-70</guid>
		<description>Instead of full fledged project management software you can also try a task management tool like http://www.statuswiz.com</description>
		<content:encoded><![CDATA[<p>Instead of full fledged project management software you can also try a task management tool like <a href="http://www.statuswiz.com" rel="nofollow">http://www.statuswiz.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfall: Allowing the specification to drift or change without agreement by Pitfall: Allowing new features to creep (or pour) in : Webster &#38; Associates LLC</title>
		<link>http://bfwa.com/2008/06/03/pitfall-allowing-the-specification-to-drift-or-change-without-agreement/#comment-69</link>
		<dc:creator>Pitfall: Allowing new features to creep (or pour) in : Webster &#38; Associates LLC</dc:creator>
		<pubDate>Wed, 04 Jun 2008 00:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?p=59#comment-69</guid>
		<description>[...] with a prior pitfall on features, this pitfall is so an obvious and well-known that I’m almost embarrassed to include it here. [...]</description>
		<content:encoded><![CDATA[<p>[...] with a prior pitfall on features, this pitfall is so an obvious and well-known that I’m almost embarrassed to include it here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfalls by &#8220;Pitfalls of Modern Software Engineering&#8221;: an update &#124; And Still I Persist</title>
		<link>http://bfwa.com/pitfalls/#comment-68</link>
		<dc:creator>&#8220;Pitfalls of Modern Software Engineering&#8221;: an update &#124; And Still I Persist</dc:creator>
		<pubDate>Fri, 30 May 2008 02:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?page_id=57#comment-68</guid>
		<description>[...] website. To make the pitfalls a bit easier to browse, I’ve now added a page to that website that lists all the pitfalls posted to date, with link to their individual entries. Just FYI. ..bruce..   Share this site with your favorite [...]</description>
		<content:encoded><![CDATA[<p>[...] website. To make the pitfalls a bit easier to browse, I’ve now added a page to that website that lists all the pitfalls posted to date, with link to their individual entries. Just FYI. ..bruce..   Share this site with your favorite [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfalls by &#8220;Pitfalls of Modern Software Engineering&#8221;: an update : Bruce F. Webster</title>
		<link>http://bfwa.com/pitfalls/#comment-67</link>
		<dc:creator>&#8220;Pitfalls of Modern Software Engineering&#8221;: an update : Bruce F. Webster</dc:creator>
		<pubDate>Fri, 30 May 2008 02:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?page_id=57#comment-67</guid>
		<description>[...] To make the pitfalls a bit easier to browse, I&#8217;ve now added a page to that website that lists all the pitfalls posted to date, with link to their individual entries. Just FYI. ..bruce..   Bookmark this page: These icons link [...]</description>
		<content:encoded><![CDATA[<p>[...] To make the pitfalls a bit easier to browse, I&#8217;ve now added a page to that website that lists all the pitfalls posted to date, with link to their individual entries. Just FYI. ..bruce..   Bookmark this page: These icons link [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfalls by Pitfalls of Modern Software Engineering: an explanation : Webster &#38; Associates LLC</title>
		<link>http://bfwa.com/pitfalls/#comment-66</link>
		<dc:creator>Pitfalls of Modern Software Engineering: an explanation : Webster &#38; Associates LLC</dc:creator>
		<pubDate>Fri, 30 May 2008 02:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?page_id=57#comment-66</guid>
		<description>[...] Pitfalls [...]</description>
		<content:encoded><![CDATA[<p>[...] Pitfalls [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pattern: The Never-Ending Story by The Wetware Crisis: the Thermocline of Truth : Bruce F. Webster</title>
		<link>http://bfwa.com/2007/12/07/pattern-the-never-ending-story/#comment-58</link>
		<dc:creator>The Wetware Crisis: the Thermocline of Truth : Bruce F. Webster</dc:creator>
		<pubDate>Thu, 01 May 2008 01:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/2007/12/07/pattern-the-never-ending-story/#comment-58</guid>
		<description>[...] I have seen the same pattern repeatedly in IT systems failure lawsuits I have worked on, particularly when I&#8217;ve had large numbers of internal e-mails and memos to review. At times, I can identify right where the thermocline is and how it creeps up the management chain as the deadline draws near. In such cases, it usually doesn&#8217;t reach the top of the management chain (which, in the case of these lawsuits, means the developer notifying the customer) until shortly (&#60;1 month) before the reported deadline.  In fact,  this syndrome goes hand-in-hand with the IT system failure lawsuit pattern I call &#8220;The Never-Ending Story&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have seen the same pattern repeatedly in IT systems failure lawsuits I have worked on, particularly when I&#8217;ve had large numbers of internal e-mails and memos to review. At times, I can identify right where the thermocline is and how it creeps up the management chain as the deadline draws near. In such cases, it usually doesn&#8217;t reach the top of the management chain (which, in the case of these lawsuits, means the developer notifying the customer) until shortly (&lt;1 month) before the reported deadline.  In fact,  this syndrome goes hand-in-hand with the IT system failure lawsuit pattern I call &#8220;The Never-Ending Story&#8220;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Litigation Support by Some thoughts on &#8220;Up or Out&#8221; : Bruce F. Webster</title>
		<link>http://bfwa.com/litigation-support/#comment-57</link>
		<dc:creator>Some thoughts on &#8220;Up or Out&#8221; : Bruce F. Webster</dc:creator>
		<pubDate>Wed, 30 Apr 2008 16:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/?page_id=4#comment-57</guid>
		<description>[...] aspect that Alex mentions was very real and extremely valuable. I learned most of what I know about being an expert witness from PwC &#8212; specifically from Jeff Parmet, the PwC Partner who hired and supervised me, as [...]</description>
		<content:encoded><![CDATA[<p>[...] aspect that Alex mentions was very real and extremely valuable. I learned most of what I know about being an expert witness from PwC &#8212; specifically from Jeff Parmet, the PwC Partner who hired and supervised me, as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pitfalls of Modern Software Engineering: an explanation by The Wetware Crisis: the Dead Sea effect : Bruce F. Webster</title>
		<link>http://bfwa.com/2008/02/25/pitfalls-of-modern-software-engineering-an-explanation/#comment-56</link>
		<dc:creator>The Wetware Crisis: the Dead Sea effect : Bruce F. Webster</dc:creator>
		<pubDate>Wed, 30 Apr 2008 00:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://bfwa.com/2008/02/25/pitfalls-of-modern-software-engineering-an-explanation/#comment-56</guid>
		<description>[...] currently working on revised versions of two of my books (The Art of &#8216;Ware [Version 2.0] and Pitfalls of Modern Software Engineering) while writing a new one (Surviving Complexity), from which this posting on the &#8220;Dead Sea [...]</description>
		<content:encoded><![CDATA[<p>[...] currently working on revised versions of two of my books (The Art of &#8216;Ware [Version 2.0] and Pitfalls of Modern Software Engineering) while writing a new one (Surviving Complexity), from which this posting on the &#8220;Dead Sea [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.289 seconds -->
