<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Silly Features -  a blog from Uri Gilad</title>
	<atom:link href="http://sillyfeatures.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://sillyfeatures.com</link>
	<description>About identifying silly decisions  - and product management</description>
	<lastBuildDate>Fri, 04 May 2012 10:18:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on SLA is not just for customers &#8211; count everything by Show Them The Way &#8211; It&#8217;s Not Just The SLA</title>
		<link>http://sillyfeatures.com/2012/03/04/sla-is-not-just-for-customers-count-everything/#comment-173</link>
		<dc:creator><![CDATA[Show Them The Way &#8211; It&#8217;s Not Just The SLA]]></dc:creator>
		<pubDate>Fri, 04 May 2012 10:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=564#comment-173</guid>
		<description><![CDATA[[...] SLA is not just for customers &#8211; count everything(sillyfeatures.com)       Share this:FacebookEmailPrintDigg       Tags: communication with customers, customer experience, Customer Management, Customer service, customer touch points, keep customers informed, Service-level agreement [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SLA is not just for customers &#8211; count everything(sillyfeatures.com)       Share this:FacebookEmailPrintDigg       Tags: communication with customers, customer experience, Customer Management, Customer service, customer touch points, keep customers informed, Service-level agreement [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The dark and dangerous side of big data by Ethan Ram</title>
		<link>http://sillyfeatures.com/2012/03/07/the-dark-and-dangerous-side-of-big-data/#comment-154</link>
		<dc:creator><![CDATA[Ethan Ram]]></dc:creator>
		<pubDate>Sat, 24 Mar 2012 17:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=573#comment-154</guid>
		<description><![CDATA[When you build an algorithm to do some analysis on big data you have to identify and eliminate the outliers before you can actually look at the results. The outliers, like the case you describe above, may shift your results significantly, to the point that they obstruct the real results. I&#039;ve had some strange cases where the weekly trends were looking almost too good to be true... I then found that they were actually too good indeed: had a couple of days with huge number of users comping from a couple of North Ireland towns, and a couple of other days with large numbers from a remote village in Malaysia. Bogus/worms/attacks or whatever you want to call them... 
One problem i found is that it&#039;s very hard to eliminate the outliers when you use standard tools like google analytics and the like.]]></description>
		<content:encoded><![CDATA[<p>When you build an algorithm to do some analysis on big data you have to identify and eliminate the outliers before you can actually look at the results. The outliers, like the case you describe above, may shift your results significantly, to the point that they obstruct the real results. I&#8217;ve had some strange cases where the weekly trends were looking almost too good to be true&#8230; I then found that they were actually too good indeed: had a couple of days with huge number of users comping from a couple of North Ireland towns, and a couple of other days with large numbers from a remote village in Malaysia. Bogus/worms/attacks or whatever you want to call them&#8230;<br />
One problem i found is that it&#8217;s very hard to eliminate the outliers when you use standard tools like google analytics and the like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just do it &#8211; on agile vs. waterfall by eram</title>
		<link>http://sillyfeatures.com/2012/03/09/just-do-it-on-agile-vs-waterfall/#comment-153</link>
		<dc:creator><![CDATA[eram]]></dc:creator>
		<pubDate>Sat, 24 Mar 2012 16:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=582#comment-153</guid>
		<description><![CDATA[Agility is anything from a philosophical view of how to run a large company to the details of who you manage your daily team meetings. I think that for a product mgr in a B2B company the main advantages you have are: 
(1) having short release cycles &gt;&gt; you don&#039;t have to plan months in advance only to find out that the business priorities have changed and your development teams are 2 months late so only 30% of the original plan is going happen.
(2) you write less of those documents that devs &quot;forget&quot; to read before they implemented and, instead, become more involved in the development process itself. 
(3) Things are much better accounted for. So you end up actually having the feature that you wanted. In the classic waterfall there are like 7 handovers of ownership on a feature. So many times the original reason to have the feature in the first place gets lost in translation. 

Glad to see you on the Agile wagon. It IS so much more fun!

p.s. some of my pondering on the subject are here- http://thenullterminator.wordpress.com/category/agile/

Ethan]]></description>
		<content:encoded><![CDATA[<p>Agility is anything from a philosophical view of how to run a large company to the details of who you manage your daily team meetings. I think that for a product mgr in a B2B company the main advantages you have are:<br />
(1) having short release cycles &gt;&gt; you don&#8217;t have to plan months in advance only to find out that the business priorities have changed and your development teams are 2 months late so only 30% of the original plan is going happen.<br />
(2) you write less of those documents that devs &#8220;forget&#8221; to read before they implemented and, instead, become more involved in the development process itself.<br />
(3) Things are much better accounted for. So you end up actually having the feature that you wanted. In the classic waterfall there are like 7 handovers of ownership on a feature. So many times the original reason to have the feature in the first place gets lost in translation. </p>
<p>Glad to see you on the Agile wagon. It IS so much more fun!</p>
<p>p.s. some of my pondering on the subject are here- <a href="http://thenullterminator.wordpress.com/category/agile/" rel="nofollow">http://thenullterminator.wordpress.com/category/agile/</a></p>
<p>Ethan</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just do it &#8211; on agile vs. waterfall by Vin D'Amico</title>
		<link>http://sillyfeatures.com/2012/03/09/just-do-it-on-agile-vs-waterfall/#comment-148</link>
		<dc:creator><![CDATA[Vin D'Amico]]></dc:creator>
		<pubDate>Fri, 09 Mar 2012 17:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=582#comment-148</guid>
		<description><![CDATA[Good point. The &quot;best&quot; process for software development is situational. We should begin every new project by asking questions about the environment, the culture and the situation. Only then can we determine how to approach the project. Thanks for sharing!]]></description>
		<content:encoded><![CDATA[<p>Good point. The &#8220;best&#8221; process for software development is situational. We should begin every new project by asking questions about the environment, the culture and the situation. Only then can we determine how to approach the project. Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Facebook and real estate &#8211; a marketing adventure by NabeWise &#8211; online neighborhood assessment &#171; Startups &#8211; Classified &#38; Ads &#171; Startups &#171; Startupeando</title>
		<link>http://sillyfeatures.com/2012/01/29/facebook-and-real-estate-a-marketing-adventure/#comment-137</link>
		<dc:creator><![CDATA[NabeWise &#8211; online neighborhood assessment &#171; Startups &#8211; Classified &#38; Ads &#171; Startups &#171; Startupeando]]></dc:creator>
		<pubDate>Wed, 01 Feb 2012 03:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=522#comment-137</guid>
		<description><![CDATA[[...] Facebook and real estate &#8211; a marketing adventure (sillyfeatures.com) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Facebook and real estate &#8211; a marketing adventure (sillyfeatures.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Facebook and real estate &#8211; a marketing adventure by NabeWise &#8211; clickable neighborhood assessment &#171; Startups &#8211; Classified &#38; Ads &#171; Startups &#171; Startupeando</title>
		<link>http://sillyfeatures.com/2012/01/29/facebook-and-real-estate-a-marketing-adventure/#comment-136</link>
		<dc:creator><![CDATA[NabeWise &#8211; clickable neighborhood assessment &#171; Startups &#8211; Classified &#38; Ads &#171; Startups &#171; Startupeando]]></dc:creator>
		<pubDate>Wed, 01 Feb 2012 03:16:35 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=522#comment-136</guid>
		<description><![CDATA[[...] Facebook and real estate &#8211; a marketing adventure (sillyfeatures.com) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Facebook and real estate &#8211; a marketing adventure (sillyfeatures.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The product owner by John Quincy</title>
		<link>http://sillyfeatures.com/2011/09/25/the-product-owner/#comment-125</link>
		<dc:creator><![CDATA[John Quincy]]></dc:creator>
		<pubDate>Sat, 15 Oct 2011 18:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=463#comment-125</guid>
		<description><![CDATA[Pretty good article.  I get worried when organizations go full force with &#039;agile&#039; without even knowing what it is or even if they should go that route -- and the PO is one of the most misunderstood roles.

You might find this video amusing on how some companies choose agile:

http://www.youtube.com/watch?v=nvks70PD0Rs

John]]></description>
		<content:encoded><![CDATA[<p>Pretty good article.  I get worried when organizations go full force with &#8216;agile&#8217; without even knowing what it is or even if they should go that route &#8212; and the PO is one of the most misunderstood roles.</p>
<p>You might find this video amusing on how some companies choose agile:</p>
<p><span style="text-align:center; display: block;"><a href="http://sillyfeatures.com/2011/09/25/the-product-owner/"><img src="http://img.youtube.com/vi/nvks70PD0Rs/2.jpg" alt="" /></a></span></p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The product owner by A Product Manager? Who exactly this guy is&#8230;? &#171; Seeingfuture</title>
		<link>http://sillyfeatures.com/2011/09/25/the-product-owner/#comment-124</link>
		<dc:creator><![CDATA[A Product Manager? Who exactly this guy is&#8230;? &#171; Seeingfuture]]></dc:creator>
		<pubDate>Sat, 15 Oct 2011 07:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=463#comment-124</guid>
		<description><![CDATA[[...] The product owner (sillyfeatures.com)  Share this:TwitterFacebookLike this:LikeBe the first to like this post. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The product owner (sillyfeatures.com)  Share this:TwitterFacebookLike this:LikeBe the first to like this post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The hidden costs of the installer package by eram</title>
		<link>http://sillyfeatures.com/2011/10/08/the-hidden-costs-of-the-installer-package/#comment-121</link>
		<dc:creator><![CDATA[eram]]></dc:creator>
		<pubDate>Wed, 12 Oct 2011 09:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=475#comment-121</guid>
		<description><![CDATA[interesting post.
a couple of additional points: 
on the SAAS provide side the decision is actually to part from having a one-version-product to having a per-customer-version. On the development side this also has a large overhead as critical bugs, and even features, will have to be delivered to specific versions and customers - a lot of branching and merging overhead will result.
having 1-2 such customers is usually relatively easy on the operational side. but once you grow to about 5 such customers you&#039;ll have to create a full back-office system to support the operations - so there&#039;s going to be a big jump in expenses before your see the return: a 24/7 support team, support case management system, a build system with proper versioning and smooth upgrades, a technical integration person, post-sales engineers... and managers to run the operation. You may need the operation to be run from another country so add the office space, travelling etc. 
This has a potential of becoming a major cause for premature scaling for a startup.]]></description>
		<content:encoded><![CDATA[<p>interesting post.<br />
a couple of additional points:<br />
on the SAAS provide side the decision is actually to part from having a one-version-product to having a per-customer-version. On the development side this also has a large overhead as critical bugs, and even features, will have to be delivered to specific versions and customers &#8211; a lot of branching and merging overhead will result.<br />
having 1-2 such customers is usually relatively easy on the operational side. but once you grow to about 5 such customers you&#8217;ll have to create a full back-office system to support the operations &#8211; so there&#8217;s going to be a big jump in expenses before your see the return: a 24/7 support team, support case management system, a build system with proper versioning and smooth upgrades, a technical integration person, post-sales engineers&#8230; and managers to run the operation. You may need the operation to be run from another country so add the office space, travelling etc.<br />
This has a potential of becoming a major cause for premature scaling for a startup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tools of the trade (and other software) by Haggai</title>
		<link>http://sillyfeatures.com/2011/05/08/tools-of-the-trade-and-other-software/#comment-104</link>
		<dc:creator><![CDATA[Haggai]]></dc:creator>
		<pubDate>Wed, 11 May 2011 17:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://sillyfeatures.com/?p=411#comment-104</guid>
		<description><![CDATA[I know it&#039;s a bit off-topic to your post, but check out www.ninite.com. It makes the relocation process easier.]]></description>
		<content:encoded><![CDATA[<p>I know it&#8217;s a bit off-topic to your post, but check out <a href="http://www.ninite.com" rel="nofollow">http://www.ninite.com</a>. It makes the relocation process easier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

