<?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: My four steps to the epiphany: Lessons learned from creating a minimally viable research product</title>
	<atom:link href="http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/</link>
	<description></description>
	<lastBuildDate>Mon, 06 Sep 2010 15:19:57 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: How to prototype iPad applications in 30 minutes or less using Apple keynote &#124; Amir Khella</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-6593</link>
		<dc:creator>How to prototype iPad applications in 30 minutes or less using Apple keynote &#124; Amir Khella</dc:creator>
		<pubDate>Mon, 12 Jul 2010 22:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-6593</guid>
		<description>[...]   My four steps to the epiphany: Lessons learned from creating a minimally viable research product February 17, 2010 [...]</description>
		<content:encoded><![CDATA[<p>[...]   My four steps to the epiphany: Lessons learned from creating a minimally viable research product February 17, 2010 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy High</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5468</link>
		<dc:creator>Timothy High</dc:creator>
		<pubDate>Wed, 03 Mar 2010 01:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5468</guid>
		<description>That&#039;s fantastic work! I created a VERY basic plugin for Eclipse that is another tangential way to tackle the very same problem. I call it &quot;Doclinks&quot; - I just open sourced it recently, but haven&#039;t gotten around to announcing it or improving it. The idea is to hook up documents (actually, URLs) to the living code using rules. With this, you can define &quot;areas&quot; or &quot;types&quot; of code based on rules, link them to architectural concepts, and so on. You could even filter to see only those files that relate to the document (e.g. a specific feature). 

If you&#039;re interested, check it out: http://sourceforge.net/apps/mediawiki/doclinks/index.php?title=Main_Page

I&#039;d love to hear more about people working on this specific problem (how to quickly ramp up new developers on an old project).</description>
		<content:encoded><![CDATA[<p>That&#8217;s fantastic work! I created a VERY basic plugin for Eclipse that is another tangential way to tackle the very same problem. I call it &#8220;Doclinks&#8221; &#8211; I just open sourced it recently, but haven&#8217;t gotten around to announcing it or improving it. The idea is to hook up documents (actually, URLs) to the living code using rules. With this, you can define &#8220;areas&#8221; or &#8220;types&#8221; of code based on rules, link them to architectural concepts, and so on. You could even filter to see only those files that relate to the document (e.g. a specific feature). </p>
<p>If you&#8217;re interested, check it out: <a href="http://sourceforge.net/apps/mediawiki/doclinks/index.php?title=Main_Page" rel="nofollow">http://sourceforge.net/apps/mediawiki/doclinks/index.php?title=Main_Page</a></p>
<p>I&#8217;d love to hear more about people working on this specific problem (how to quickly ramp up new developers on an old project).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-02-25 &#171; Blarney Fellow</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5400</link>
		<dc:creator>links for 2010-02-25 &#171; Blarney Fellow</dc:creator>
		<pubDate>Fri, 26 Feb 2010 01:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5400</guid>
		<description>[...] My four steps to the epiphany: Lessons learned from creating a minimally viable research product &#124; A... (tags: customer-development brezmejnik) [...]</description>
		<content:encoded><![CDATA[<p>[...] My four steps to the epiphany: Lessons learned from creating a minimally viable research product | A&#8230; (tags: customer-development brezmejnik) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MSでのCustomer Developmentの事例紹介 &#171; Ghost Driver</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5350</link>
		<dc:creator>MSでのCustomer Developmentの事例紹介 &#171; Ghost Driver</dc:creator>
		<pubDate>Mon, 22 Feb 2010 14:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5350</guid>
		<description>[...] My four steps to the epiphany:Lessons learned from creating a minimally viable research product [...]</description>
		<content:encoded><![CDATA[<p>[...] My four steps to the epiphany:Lessons learned from creating a minimally viable research product [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flow &#187; Blog Archive &#187; Daily Digest for February 19th - The zeitgeist daily</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5308</link>
		<dc:creator>Flow &#187; Blog Archive &#187; Daily Digest for February 19th - The zeitgeist daily</dc:creator>
		<pubDate>Fri, 19 Feb 2010 10:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5308</guid>
		<description>[...] Shared My four steps to the epiphany &#8211; Lessons learned from a research product. [...]</description>
		<content:encoded><![CDATA[<p>[...] Shared My four steps to the epiphany &#8211; Lessons learned from a research product. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-02-18 at Scott Porad</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5305</link>
		<dc:creator>links for 2010-02-18 at Scott Porad</dc:creator>
		<pubDate>Fri, 19 Feb 2010 07:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5305</guid>
		<description>[...] My four steps to the epiphany: Lessons learned from creating a minimally viable research product Some excellent examples about how to incrementally work into a solution that actually solve customer problems, as opposed to designing a solution that nobody actually wants. [...]</description>
		<content:encoded><![CDATA[<p>[...] My four steps to the epiphany: Lessons learned from creating a minimally viable research product Some excellent examples about how to incrementally work into a solution that actually solve customer problems, as opposed to designing a solution that nobody actually wants. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5290</link>
		<dc:creator>Amir</dc:creator>
		<pubDate>Thu, 18 Feb 2010 05:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5290</guid>
		<description>Thanks for the corrections, Bassem :)</description>
		<content:encoded><![CDATA[<p>Thanks for the corrections, Bassem <img src='http://blog.amirkhella.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B Fadlia</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5289</link>
		<dc:creator>B Fadlia</dc:creator>
		<pubDate>Thu, 18 Feb 2010 04:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5289</guid>
		<description>oops.. my correction needs a correction, &quot;voice recorder&quot;</description>
		<content:encoded><![CDATA[<p>oops.. my correction needs a correction, &#8220;voice recorder&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B Fadlia</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5288</link>
		<dc:creator>B Fadlia</dc:creator>
		<pubDate>Thu, 18 Feb 2010 04:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5288</guid>
		<description>Very good thoughts and very well organized Amir. I spent 3 years supporting and modifying a vendor Employees Time Recording application after the vendor company was no longer available to support it, so I could relate to this.
BTW, step 1, you bought a time &quot;recorder&quot; and there was a pattern among all &quot;interviewees&quot;</description>
		<content:encoded><![CDATA[<p>Very good thoughts and very well organized Amir. I spent 3 years supporting and modifying a vendor Employees Time Recording application after the vendor company was no longer available to support it, so I could relate to this.<br />
BTW, step 1, you bought a time &#8220;recorder&#8221; and there was a pattern among all &#8220;interviewees&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir</title>
		<link>http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/comment-page-1/#comment-5284</link>
		<dc:creator>Amir</dc:creator>
		<pubDate>Thu, 18 Feb 2010 03:39:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amirkhella.com/2010/02/17/my-four-steps-to-the-epiphany-lessons-learned-from-creating-a-minimally-viable-research-product/#comment-5284</guid>
		<description>Aaron - It&#039;s highly likely that we crossed paths. I met with DonnaWa and her team several times during my time at Microsoft.</description>
		<content:encoded><![CDATA[<p>Aaron &#8211; It&#8217;s highly likely that we crossed paths. I met with DonnaWa and her team several times during my time at Microsoft.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
