<?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: Kanban systems for software development</title>
	<atom:link href="http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Wed, 01 Feb 2012 18:32:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Less haste, more speed</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-29174</link>
		<dc:creator>Less haste, more speed</dc:creator>
		<pubDate>Fri, 14 Oct 2011 16:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-29174</guid>
		<description>[...] these naturally occurring issues (after all every company, every team, is different), I will use Kanban. Kanban was devised by people from a company to deal with a problem of fully carrying through [...]</description>
		<content:encoded><![CDATA[<p>[...] these naturally occurring issues (after all every company, every team, is different), I will use Kanban. Kanban was devised by people from a company to deal with a problem of fully carrying through [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuraisha Chavan</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-28569</link>
		<dc:creator>Yuraisha Chavan</dc:creator>
		<pubDate>Thu, 04 Aug 2011 08:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-28569</guid>
		<description>I would like to see which companies  have you implemented this in and what was the outcome? Would like to try this only if it has worked. I dont want to have trial and error.</description>
		<content:encoded><![CDATA[<p>I would like to see which companies  have you implemented this in and what was the outcome? Would like to try this only if it has worked. I dont want to have trial and error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: When great communication is required &#124; Rural Source IT</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-28289</link>
		<dc:creator>When great communication is required &#124; Rural Source IT</dc:creator>
		<pubDate>Mon, 01 Aug 2011 15:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-28289</guid>
		<description>[...] the team and with the client organization. Many processes in the Agile space fit the bill: Scrum, Kanban, XP, [...]</description>
		<content:encoded><![CDATA[<p>[...] the team and with the client organization. Many processes in the Agile space fit the bill: Scrum, Kanban, XP, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kanban Nightmares - Zsolt Fabók&#039;s Page</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-11219</link>
		<dc:creator>Kanban Nightmares - Zsolt Fabók&#039;s Page</dc:creator>
		<pubDate>Wed, 05 Jan 2011 08:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-11219</guid>
		<description>[...] content of the Queue, the prioritization, and keeping the basic rules of Kanban, required attention almost on a hourly [...]</description>
		<content:encoded><![CDATA[<p>[...] content of the Queue, the prioritization, and keeping the basic rules of Kanban, required attention almost on a hourly [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Four Principles of Effective Software Teams &#171; kingsbery.net</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-10260</link>
		<dc:creator>Four Principles of Effective Software Teams &#171; kingsbery.net</dc:creator>
		<pubDate>Tue, 21 Dec 2010 14:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-10260</guid>
		<description>[...] they use to build it, and the process they use in building it. He noted that there are several processes out there, but all effective software processes include the following four [...]</description>
		<content:encoded><![CDATA[<p>[...] they use to build it, and the process they use in building it. He noted that there are several processes out there, but all effective software processes include the following four [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hasan Jaffal</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-7034</link>
		<dc:creator>Hasan Jaffal</dc:creator>
		<pubDate>Wed, 31 Mar 2010 11:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-7034</guid>
		<description>In Agile projects, it&#039;s a common practice to visualize and share project status using charts or diagrams on boards. While no single document delivers all of the ammunition agile teams need to get the rhythm, this set of visual materials offers an easy framework to help guide software development teams through the various agile cycles. 

A variation of the Kanban, an easy way to represent these cards, with some enhancements to this representation and a synchronized use of the concept, ArabiaGIS introduced the Sync Kanban concept. 

The Sync Kanban is composed of a board for each project where the team leader or the responsible developer will try to represent the project status and the features progress with pies. 

for complete description: http://www.jaftalks.com/Home/Show/Sync-Kanban-Agile-Project-Management

Regrads,
Hasan Jaffal</description>
		<content:encoded><![CDATA[<p>In Agile projects, it&#8217;s a common practice to visualize and share project status using charts or diagrams on boards. While no single document delivers all of the ammunition agile teams need to get the rhythm, this set of visual materials offers an easy framework to help guide software development teams through the various agile cycles. </p>
<p>A variation of the Kanban, an easy way to represent these cards, with some enhancements to this representation and a synchronized use of the concept, ArabiaGIS introduced the Sync Kanban concept. </p>
<p>The Sync Kanban is composed of a board for each project where the team leader or the responsible developer will try to represent the project status and the features progress with pies. </p>
<p>for complete description: <a href="http://www.jaftalks.com/Home/Show/Sync-Kanban-Agile-Project-Management" rel="nofollow">http://www.jaftalks.com/Home/S.....Management</a></p>
<p>Regrads,<br />
Hasan Jaffal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I2E &#187; Blog Archive &#187; Sesiones Agile Open Space 2009 parte 1</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-6152</link>
		<dc:creator>I2E &#187; Blog Archive &#187; Sesiones Agile Open Space 2009 parte 1</dc:creator>
		<pubDate>Mon, 02 Nov 2009 08:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-6152</guid>
		<description>[...] A la conclusión que llegue es que kanban sobre todo encaja bien en procesos de mantenimiento o helpdesk, aunque también hay ejemplos en los que utilizan kanban para el desarrollo de software. [...]</description>
		<content:encoded><![CDATA[<p>[...] A la conclusión que llegue es que kanban sobre todo encaja bien en procesos de mantenimiento o helpdesk, aunque también hay ejemplos en los que utilizan kanban para el desarrollo de software. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-106</link>
		<dc:creator>Corey</dc:creator>
		<pubDate>Thu, 30 Aug 2007 04:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-106</guid>
		<description>Outstanding!  I would love to hear more about your results.</description>
		<content:encoded><![CDATA[<p>Outstanding!  I would love to hear more about your results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Yip</title>
		<link>http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/comment-page-1/#comment-105</link>
		<dc:creator>Jason Yip</dc:creator>
		<pubDate>Thu, 30 Aug 2007 04:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/29/kanban-systems-for-software-development/#comment-105</guid>
		<description>I still prefer and aim for single piece flow by developing poly-skilled team members but this pretty much matches what we&#039;ve seen for a well-tuned pull system as well.</description>
		<content:encoded><![CDATA[<p>I still prefer and aim for single piece flow by developing poly-skilled team members but this pretty much matches what we&#8217;ve seen for a well-tuned pull system as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.470 seconds -->

