<?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 for Budget Musings</title>
	<atom:link href="http://calendarbudget.com/wordpress/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://calendarbudget.com/wordpress</link>
	<description>Understand your money.  Plan for your future.</description>
	<lastBuildDate>Wed, 10 Mar 2010 11:27:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Time Savings of a Live-in Cook by Cheryll Eighmey</title>
		<link>http://calendarbudget.com/wordpress/time-savings-of-a-live-in-cook/comment-page-1/#comment-381</link>
		<dc:creator>Cheryll Eighmey</dc:creator>
		<pubDate>Wed, 10 Mar 2010 11:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://calendarbudget.com/wordpress/time-savings-of-a-live-in-cook/#comment-381</guid>
		<description>VRy interesting to browse through it</description>
		<content:encoded><![CDATA[<p>VRy interesting to browse through it</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CalendarBudget Release Cycle by Budget Musings Admin</title>
		<link>http://calendarbudget.com/wordpress/calendarbudget-release-cycle/comment-page-1/#comment-371</link>
		<dc:creator>Budget Musings Admin</dc:creator>
		<pubDate>Sat, 27 Feb 2010 18:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://calendarbudget.com/wordpress/?p=756#comment-371</guid>
		<description>Charis - I appreciate your comments. Sometimes it does feel like we&#039;re trying to produce too much!

We take bugs very serious and treat testing as an integral part of the process. The way we look at it, without thorough testing where the whole team is working together to make the product great, we&#039;ll result in a mediocre product. Instead with CalendarBudget, every small problem identified is discussed and prioritized. Naturally, there is always a tradeoff of fixing every small detail that 95% of people won&#039;t care about and getting the features out there, with the intent to fix the small outlier cases soon thereafer. High quality is a must if any product developer wants customers that stay.

We&#039;re not too different than any development house, except a little smaller, more flexible and we try to follow extreme programming principles as much as we can - getting requirements from our users. However, to mitigate the enormous effort in testing, we&#039;re looking into some form of automation - investigating http://seleniumhq.org/. This will get us closer to extreme programming principles of incremental builds since we&#039;ll be able to get through testing more regularly rather than waiting until most of dev is complete (waterfall approach).</description>
		<content:encoded><![CDATA[<p>Charis &#8211; I appreciate your comments. Sometimes it does feel like we&#8217;re trying to produce too much!</p>
<p>We take bugs very serious and treat testing as an integral part of the process. The way we look at it, without thorough testing where the whole team is working together to make the product great, we&#8217;ll result in a mediocre product. Instead with CalendarBudget, every small problem identified is discussed and prioritized. Naturally, there is always a tradeoff of fixing every small detail that 95% of people won&#8217;t care about and getting the features out there, with the intent to fix the small outlier cases soon thereafer. High quality is a must if any product developer wants customers that stay.</p>
<p>We&#8217;re not too different than any development house, except a little smaller, more flexible and we try to follow extreme programming principles as much as we can &#8211; getting requirements from our users. However, to mitigate the enormous effort in testing, we&#8217;re looking into some form of automation &#8211; investigating <a href="http://seleniumhq.org/" rel="nofollow">http://seleniumhq.org/</a>. This will get us closer to extreme programming principles of incremental builds since we&#8217;ll be able to get through testing more regularly rather than waiting until most of dev is complete (waterfall approach).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CalendarBudget Release Cycle by Charis Tod</title>
		<link>http://calendarbudget.com/wordpress/calendarbudget-release-cycle/comment-page-1/#comment-367</link>
		<dc:creator>Charis Tod</dc:creator>
		<pubDate>Mon, 22 Feb 2010 20:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://calendarbudget.com/wordpress/?p=756#comment-367</guid>
		<description>The tester is not entirely responsible for quality. That is the task of the entire team. I suppose that part of the grounds its susceptible for teams to get into this groupthink about bugs is because the testers are marginalized into the peripheries and looked at as a encumbrance more than a help to the team -- i.e. a barrier for driving out features that the team really wants to release. If a bug like that existed, the feature should never have been released, period. If you have so many bugs that you are normally making these types of decisions, it indicates that you&#039;re seeking to produce too many features at the same time. Doing this has the appearance of operating quicker, but is actually slowing you down - as exemplified by the effort of release push backs, patches, bug management.</description>
		<content:encoded><![CDATA[<p>The tester is not entirely responsible for quality. That is the task of the entire team. I suppose that part of the grounds its susceptible for teams to get into this groupthink about bugs is because the testers are marginalized into the peripheries and looked at as a encumbrance more than a help to the team &#8212; i.e. a barrier for driving out features that the team really wants to release. If a bug like that existed, the feature should never have been released, period. If you have so many bugs that you are normally making these types of decisions, it indicates that you&#8217;re seeking to produce too many features at the same time. Doing this has the appearance of operating quicker, but is actually slowing you down &#8211; as exemplified by the effort of release push backs, patches, bug management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CalendarBudget Release Cycle by Narda</title>
		<link>http://calendarbudget.com/wordpress/calendarbudget-release-cycle/comment-page-1/#comment-361</link>
		<dc:creator>Narda</dc:creator>
		<pubDate>Sun, 21 Feb 2010 05:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://calendarbudget.com/wordpress/?p=756#comment-361</guid>
		<description>Have you considered cross-breeding Robin with an octopus? :)</description>
		<content:encoded><![CDATA[<p>Have you considered cross-breeding Robin with an octopus? <img src='http://calendarbudget.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Money &#8211; Till Death Do Us Part by Blog items</title>
		<link>http://calendarbudget.com/wordpress/money-till-death-do-us-part/comment-page-1/#comment-357</link>
		<dc:creator>Blog items</dc:creator>
		<pubDate>Sun, 14 Feb 2010 15:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://calendarbudget.com/wordpress/?p=175#comment-357</guid>
		<description>This is a great place for people to learn.  Like myself, many people really need a little bump in direction to get themselves headed the right way.</description>
		<content:encoded><![CDATA[<p>This is a great place for people to learn.  Like myself, many people really need a little bump in direction to get themselves headed the right way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
