<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Spikelab</title>
	<atom:link href="http://www.spikelab.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spikelab.org</link>
	<description>Solutions as simple as possible but not simpler</description>
	<lastBuildDate>Sun, 13 Jan 2013 19:17:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Delivering value: engineers and the end user</title>
		<link>http://www.spikelab.org/delivering-value-engineers-and-the-end-user/</link>
		<comments>http://www.spikelab.org/delivering-value-engineers-and-the-end-user/#comments</comments>
		<pubDate>Sun, 13 Jan 2013 19:17:22 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[devops]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=472</guid>
		<description><![CDATA[When I started following along the devops movement often times the phrase &#8220;delivering value&#8221; would appear in conversation. That made me ponder even harder on a question that had haunted me for quite a while already: who, as an ops person, am I delivering value to? There seem to be two obvious recipients: the rest of engineering, primarily application developers, and end users, where in theory the value delivered to the devs is just a proxy [...]]]></description>
		<wfw:commentRss>http://www.spikelab.org/delivering-value-engineers-and-the-end-user/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Adventure Lab, part 4: 5 lessons learned on customer development</title>
		<link>http://www.spikelab.org/adventure-lab-part-4-5-lessons-learned-on-customer-development/</link>
		<comments>http://www.spikelab.org/adventure-lab-part-4-5-lessons-learned-on-customer-development/#comments</comments>
		<pubDate>Wed, 06 Jun 2012 04:06:56 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=460</guid>
		<description><![CDATA[The Four Steps to the Epiphany book has dramatically contributed to shape what today is known as the Lean Startup movement. One of the fundamental concepts illustrated in the book is the idea of customer development. One of the best things you can do to ensure the success of your business is to talk with your customers and validate your product before you building it.

Following that model the Opportunity Analysis Project (OAP) phase revolved around customer interviews and validating the hypothesis expressed in the Business Model Canvas created at the beginning of the session. While the process looks simple in theory, there are a lot of pitfalls and things to know about in order to run successful experiments.]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventure-lab-part-4-5-lessons-learned-on-customer-development/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The problems with devops in a job title</title>
		<link>http://www.spikelab.org/devops-in-job-title-problems/</link>
		<comments>http://www.spikelab.org/devops-in-job-title-problems/#comments</comments>
		<pubDate>Tue, 29 May 2012 09:58:08 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[devops]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=302</guid>
		<description><![CDATA[Have you recently changed your job title to include the word devops in it? What were you reasons? Has it given the results you hoped for? It&#8217;s been a while since I posted about why devops makes sense in a job title and a few weeks and a few discussions later I have a some thoughts that you might find useful if you decide to go down the same path. If you look at the [...]]]></description>
		<wfw:commentRss>http://www.spikelab.org/devops-in-job-title-problems/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Adventure Lab, part 3: 5 lessons learned on brainstorming</title>
		<link>http://www.spikelab.org/adventure-lab-part-3-5-lessons-learned-on-brainstorming/</link>
		<comments>http://www.spikelab.org/adventure-lab-part-3-5-lessons-learned-on-brainstorming/#comments</comments>
		<pubDate>Mon, 07 May 2012 20:16:57 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=443</guid>
		<description><![CDATA[With teams formed and pressing ahead with the first assignment one of the first tasks on the list is idea generation. I'm sure some folks came to the course with a great idea, but what if you could increase your chances to find the right idea and get the opportunity to fully explore your team's potential?

If you're reading this, chances are you've been involved in a brainstorming session before even if you didn't realise it was one. If it was any close to traditional brainstorming you were probably in a room with a few friends or colleagues, most likely in front of a whiteboard and one of you was frantically scribbling down as the rest of the team was blurting stuff out. This sounds all fine and dandy, except that it's not. There are three main problems with a situation like that:]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventure-lab-part-3-5-lessons-learned-on-brainstorming/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>AdVenturersLab no more. Long live The Adventure Lab</title>
		<link>http://www.spikelab.org/adventurerslab-no-more-long-live-adventurelab/</link>
		<comments>http://www.spikelab.org/adventurerslab-no-more-long-live-adventurelab/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 08:40:38 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[adventurerslab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=409</guid>
		<description><![CDATA[New teams are being formed in sight of the real beginning of the course next week and as I bid farewell to my old group I'm excited to join some awesome people in The Adventure Lab. This series has just got better, I promise you, so make sure you don't miss a post. ]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventurerslab-no-more-long-live-adventurelab/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AdventurersLab, part 2: 5 top tools for collaboration</title>
		<link>http://www.spikelab.org/adventurerslab-part-2-5-top-tools-for-collaboration/</link>
		<comments>http://www.spikelab.org/adventurerslab-part-2-5-top-tools-for-collaboration/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 20:18:35 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[adventurerslab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=412</guid>
		<description><![CDATA[Team collaboration has been pivotal to the success of the project and with a lot of remote and distributed teams is worth to take a look at the tooling that made that collaboration possible. Read on to find out about the top 5 collaboration tools used by many teams and some tips and tricks.]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventurerslab-part-2-5-top-tools-for-collaboration/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>AdventurersLab, part 1: 5 lessons on team building</title>
		<link>http://www.spikelab.org/adventurerslab-part-1-5-lessons-team-building/</link>
		<comments>http://www.spikelab.org/adventurerslab-part-1-5-lessons-team-building/#comments</comments>
		<pubDate>Tue, 17 Apr 2012 21:56:38 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[adventurerslab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=380</guid>
		<description><![CDATA[The first two weeks of the Venture Lab course centered around team building. This makes sense as people form groups in preparation for the real start next week. The teams were initially formed by random selection and in a lot of cases yielded poor results. But even with a difficult situation at hand you can still turn things around if you keep a few things in mind.]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventurerslab-part-1-5-lessons-team-building/feed/</wfw:commentRss>
		<slash:comments>33</slash:comments>
		</item>
		<item>
		<title>AdventurersLab: documenting the Stanford Entrepreneurship course</title>
		<link>http://www.spikelab.org/adventurerslab-documenting-stanford-entrepreneurship-course/</link>
		<comments>http://www.spikelab.org/adventurerslab-documenting-stanford-entrepreneurship-course/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 14:22:33 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[adventurelab]]></category>
		<category><![CDATA[adventurerslab]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=350</guid>
		<description><![CDATA[Last year a spur of online courses was announced among which featured the Technology Entrepreneurship course offered by the Stanford University. I jumped on this as soon as I found out about it and started counting the days to launch like a kid counts the days to Christmas. The course got delayed twice, but has finally started almost two weeks ago and the first assignment is in progress. You might know engineers that over the years have [...]]]></description>
		<wfw:commentRss>http://www.spikelab.org/adventurerslab-documenting-stanford-entrepreneurship-course/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>I&#8217;m not a rabid chef user, but I still love devops</title>
		<link>http://www.spikelab.org/devops-notjust-configuration-management/</link>
		<comments>http://www.spikelab.org/devops-notjust-configuration-management/#comments</comments>
		<pubDate>Sat, 31 Mar 2012 09:35:18 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[devops]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=335</guid>
		<description><![CDATA[It&#8217;s been a couple heated weeks on the devops front. In part due, again, to the NoOps debacle (see Cockcroft&#8217;s post and Allspaw&#8217;s reply) and for the other part due to this statement: [The devops list is] mostly folks who are users, developers, and fans of chef, puppet, similar tools. A few folks have a broader sense of operations. (Call me sensitive, but when I queried about management of shell scripts, I got jumped on by [...]]]></description>
		<wfw:commentRss>http://www.spikelab.org/devops-notjust-configuration-management/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Devops will steal your job. Or not.</title>
		<link>http://www.spikelab.org/automation-devops-sysadmin-jobs/</link>
		<comments>http://www.spikelab.org/automation-devops-sysadmin-jobs/#comments</comments>
		<pubDate>Tue, 13 Mar 2012 21:33:24 +0000</pubDate>
		<dc:creator>spike</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[devops]]></category>

		<guid isPermaLink="false">http://www.spikelab.org/?p=234</guid>
		<description><![CDATA[It must have been at least five years ago, when puppet was getting popular, that I first ran into someone terrified of losing his job because of automation. I even wonder if the same happened before when cfengine came out, and history would suggest it probably did.  However, what also history suggests is that resourceful and competent engineers will always have a job. The devops movement, as heavily entrenched in automation as it is, seems to have [...]]]></description>
		<wfw:commentRss>http://www.spikelab.org/automation-devops-sysadmin-jobs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
