<?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: Our first Kanban board for IT Operations and Support</title>
	<atom:link href="http://www.systemsoup.org/2009/12/our-first-kanban-board-for-it-operations-and-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.systemsoup.org/2009/12/our-first-kanban-board-for-it-operations-and-support/</link>
	<description>Thoughts on devops, and random sysadmin related rambles.</description>
	<lastBuildDate>Tue, 16 Feb 2010 07:30:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul</title>
		<link>http://www.systemsoup.org/2009/12/our-first-kanban-board-for-it-operations-and-support/comment-page-1/#comment-15</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 10 Feb 2010 21:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.systemsoup.org/?p=15#comment-15</guid>
		<description>From my experience better than dividing the board into three areas, you can use colorful cards and label it: blue - Support Bucket, red - Emergency and green -normal workflow.
Tool which supports it is http://kanbantool.com</description>
		<content:encoded><![CDATA[<p>From my experience better than dividing the board into three areas, you can use colorful cards and label it: blue &#8211; Support Bucket, red &#8211; Emergency and green -normal workflow.<br />
Tool which supports it is <a href="http://kanbantool.com" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/kanbantool.com?referer=');">http://kanbantool.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Fletcher</title>
		<link>http://www.systemsoup.org/2009/12/our-first-kanban-board-for-it-operations-and-support/comment-page-1/#comment-3</link>
		<dc:creator>Adam Fletcher</dc:creator>
		<pubDate>Fri, 04 Dec 2009 04:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.systemsoup.org/?p=15#comment-3</guid>
		<description>Interesting article. We do something similar where I work, evolved over time. I like this approach much better because it captures the dynamic nature of operations. Ops people need to balance time spent on emergencies, ongoing maintenance, and planned project work, and because of this balance traditional project planning fails. 
 
This process of triage of planned/unplanned work can be codified into software such as RT or other work/ticket tracking software, and doing so adds searching &amp; reporting so you can do lots of analysis on the data you create.

-Adam</description>
		<content:encoded><![CDATA[<p>Interesting article. We do something similar where I work, evolved over time. I like this approach much better because it captures the dynamic nature of operations. Ops people need to balance time spent on emergencies, ongoing maintenance, and planned project work, and because of this balance traditional project planning fails. </p>
<p>This process of triage of planned/unplanned work can be codified into software such as RT or other work/ticket tracking software, and doing so adds searching &amp; reporting so you can do lots of analysis on the data you create.</p>
<p>-Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gildas Le Nadan</title>
		<link>http://www.systemsoup.org/2009/12/our-first-kanban-board-for-it-operations-and-support/comment-page-1/#comment-2</link>
		<dc:creator>Gildas Le Nadan</dc:creator>
		<pubDate>Thu, 03 Dec 2009 22:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.systemsoup.org/?p=15#comment-2</guid>
		<description>Hi Mike!

Good to see you&#039;re trying some of the stuff from devopsdays&#039;09 at home :)

I will be particularly interested to follow what comes out of this experiment, since I think it is quite similar to the situation I was in at my previous job.

I think the board description should read:
&quot;The board is divided into three areas: Support Bucket (Blue); Emergency (Red); and normal workflow (Green).&quot;

Best of luck!
Gildas</description>
		<content:encoded><![CDATA[<p>Hi Mike!</p>
<p>Good to see you&#8217;re trying some of the stuff from devopsdays&#8217;09 at home :)</p>
<p>I will be particularly interested to follow what comes out of this experiment, since I think it is quite similar to the situation I was in at my previous job.</p>
<p>I think the board description should read:<br />
&#8220;The board is divided into three areas: Support Bucket (Blue); Emergency (Red); and normal workflow (Green).&#8221;</p>
<p>Best of luck!<br />
Gildas</p>
]]></content:encoded>
	</item>
</channel>
</rss>

