<?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: Seattle Startup Weekend Redux</title>
	<atom:link href="http://www.npost.com/blog/2009/02/09/seattle-startup-weekend-redux/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.npost.com/blog/2009/02/09/seattle-startup-weekend-redux/</link>
	<description>Connecting Startups with Talent Since 1999</description>
	<lastBuildDate>Fri, 27 May 2011 04:20:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Josh Maher</title>
		<link>http://www.npost.com/blog/2009/02/09/seattle-startup-weekend-redux/#comment-314</link>
		<dc:creator>Josh Maher</dc:creator>
		<pubDate>Thu, 12 Feb 2009 20:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.npost.com/?p=1931#comment-314</guid>
		<description>Great insights, I definitely think the smaller teams worked better. Even at the weekend there were largish teams that needed the overhead of planning. For this type of project, the goal should be small enough that a simple shared vision/goal should be all that is needed to be successful. Sprint planning, etc is great for larger projects, but those are not weekend projects.

My feedback, continue to distill the projects to the heart of what the startup is and go at it full speed. The Obey The Decider team accomplished an amazing amount of work with no late nights simply because our goal was simple and shared. We still had PR, Evangelism, Legal, developers, etc - but we all worked independantly on a shared vision reaching the end product quickly.

The rest of my thoughts are here:

http://joshmaher.wordpress.com/2009/02/12/thoughts-on-seattle-startup-weekend-2/</description>
		<content:encoded><![CDATA[<p>Great insights, I definitely think the smaller teams worked better. Even at the weekend there were largish teams that needed the overhead of planning. For this type of project, the goal should be small enough that a simple shared vision/goal should be all that is needed to be successful. Sprint planning, etc is great for larger projects, but those are not weekend projects.</p>
<p>My feedback, continue to distill the projects to the heart of what the startup is and go at it full speed. The Obey The Decider team accomplished an amazing amount of work with no late nights simply because our goal was simple and shared. We still had PR, Evangelism, Legal, developers, etc &#8211; but we all worked independantly on a shared vision reaching the end product quickly.</p>
<p>The rest of my thoughts are here:</p>
<p><a href="http://joshmaher.wordpress.com/2009/02/12/thoughts-on-seattle-startup-weekend-2/" rel="nofollow">http://joshmaher.wordpress.com/2009/02/12/thoughts-on-seattle-startup-weekend-2/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marina Martin</title>
		<link>http://www.npost.com/blog/2009/02/09/seattle-startup-weekend-redux/#comment-313</link>
		<dc:creator>Marina Martin</dc:creator>
		<pubDate>Tue, 10 Feb 2009 04:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.npost.com/?p=1931#comment-313</guid>
		<description>Great write-up, Nathan ... I concur with everything you said.

My favorite anecdotes from this weekend (and last) are those of people learning an entire new programming language in a weekend. That&#039;s something they&#039;ll be able to use many times in the future, and it&#039;s a great testament to the talent of so many people in the room.

The one part of the weekend that could have used improvement was the initial idea pitching and vetting. When you have so little time, spending all of Friday just pitching and voting on ideas wasn&#039;t very efficient. Luckily, KnarlyVote was created over the weekend to help make the vetting process faster in the future. Talk about seeing a problem and solving it ... that team gets major props from me.

They say you shouldn&#039;t marry someone until you&#039;ve seen them with the flu and have traveled with them to a foreign country, because that&#039;s when you see their true colors come out. The same idea applies to people you work with on a company (or any project) ... seeing so many teams not just succeed, but *thrive*, amidst some very significant challenges (coding with no power and no Internet is a challenge!), was incredibly inspirational, and once you&#039;ve worked through obstacles like those with someone and come out on the other side, you know you can work with them on just about anything.</description>
		<content:encoded><![CDATA[<p>Great write-up, Nathan &#8230; I concur with everything you said.</p>
<p>My favorite anecdotes from this weekend (and last) are those of people learning an entire new programming language in a weekend. That&#8217;s something they&#8217;ll be able to use many times in the future, and it&#8217;s a great testament to the talent of so many people in the room.</p>
<p>The one part of the weekend that could have used improvement was the initial idea pitching and vetting. When you have so little time, spending all of Friday just pitching and voting on ideas wasn&#8217;t very efficient. Luckily, KnarlyVote was created over the weekend to help make the vetting process faster in the future. Talk about seeing a problem and solving it &#8230; that team gets major props from me.</p>
<p>They say you shouldn&#8217;t marry someone until you&#8217;ve seen them with the flu and have traveled with them to a foreign country, because that&#8217;s when you see their true colors come out. The same idea applies to people you work with on a company (or any project) &#8230; seeing so many teams not just succeed, but *thrive*, amidst some very significant challenges (coding with no power and no Internet is a challenge!), was incredibly inspirational, and once you&#8217;ve worked through obstacles like those with someone and come out on the other side, you know you can work with them on just about anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce P. Henry</title>
		<link>http://www.npost.com/blog/2009/02/09/seattle-startup-weekend-redux/#comment-312</link>
		<dc:creator>Bruce P. Henry</dc:creator>
		<pubDate>Tue, 10 Feb 2009 03:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.npost.com/?p=1931#comment-312</guid>
		<description>I had some of the same reactions about small groups.  They&#039;re much more nimble and the communication (at least in most of the groups) was easy and transparent.

My thoughts on why some teams had trouble getting enough technical folks are on my blog at http://www.brucephenry.com/2009/02/seattle-startup-weekend-2-why-are-good.html</description>
		<content:encoded><![CDATA[<p>I had some of the same reactions about small groups.  They&#8217;re much more nimble and the communication (at least in most of the groups) was easy and transparent.</p>
<p>My thoughts on why some teams had trouble getting enough technical folks are on my blog at <a href="http://www.brucephenry.com/2009/02/seattle-startup-weekend-2-why-are-good.html" rel="nofollow">http://www.brucephenry.com/2009/02/seattle-startup-weekend-2-why-are-good.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

