<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for The Agile Voice</title>
	<link>http://theagilevoice.co.uk</link>
	<description>Thoughts and ideas about Agile Methods</description>
	<pubDate>Sun, 20 May 2012 15:04:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>Comment on The Agile Business Conference 2009 by Simon</title>
		<link>http://theagilevoice.co.uk/2009/10/16/the-agile-business-conference-2009/#comment-6092</link>
		<author>Simon</author>
		<pubDate>Fri, 16 Oct 2009 14:04:04 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/10/16/the-agile-business-conference-2009/#comment-6092</guid>
		<description>Sorry about the size of the text for this posting chaps! There seem to be bugs in the system preventing me from altering the font size.</description>
		<content:encoded><![CDATA[<p>Sorry about the size of the text for this posting chaps! There seem to be bugs in the system preventing me from altering the font size.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Groundhog Agile by Oliver Galloway-Lunn</title>
		<link>http://theagilevoice.co.uk/2009/04/21/groundhog-agile/#comment-5309</link>
		<author>Oliver Galloway-Lunn</author>
		<pubDate>Tue, 04 Aug 2009 20:24:08 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/04/21/groundhog-agile/#comment-5309</guid>
		<description>It might be worth letting the team move onto a new project.  If that's not possible try switching/swapping some team members with another agile team (probably not more than a 3rd of the team) to reinvigorate the team dynamic.

Another option might be to introduce some non-agile or junior developers into the team to allow them to gain some agile skills and experience as well as giving the experienced developers an opportunity to learn some agile coaching skills.</description>
		<content:encoded><![CDATA[<p>It might be worth letting the team move onto a new project.  If that&#8217;s not possible try switching/swapping some team members with another agile team (probably not more than a 3rd of the team) to reinvigorate the team dynamic.</p>
<p>Another option might be to introduce some non-agile or junior developers into the team to allow them to gain some agile skills and experience as well as giving the experienced developers an opportunity to learn some agile coaching skills.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint or Marathon? by Neil Martin</title>
		<link>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-3387</link>
		<author>Neil Martin</author>
		<pubDate>Thu, 30 Apr 2009 21:46:36 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-3387</guid>
		<description>A final thought this might be of interest. 

http://neilmartinagile.wordpress.com/2008/09/13/what-does-a-card-look-like/</description>
		<content:encoded><![CDATA[<p>A final thought this might be of interest. </p>
<p><a href="http://neilmartinagile.wordpress.com/2008/09/13/what-does-a-card-look-like/" rel="nofollow">http://neilmartinagile.wordpress.com/2008/09/13/what-does-a-card-look-like/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint or Marathon? by Neil Martin</title>
		<link>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-3386</link>
		<author>Neil Martin</author>
		<pubDate>Thu, 30 Apr 2009 21:44:26 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-3386</guid>
		<description>Simon 
I have to say i also run super fast sprints to do clean down defect runs and in preparation for releases and they can last 2 days. 

We dont even bother with a card wall for these we use a big white board and we list them and then the pairs just walk up and cross them off as the defect is fixed and passed to QA. I think its about doing what is right for your environment. 

We quite often for focused developments use LEAN style card walls pulling the cards through the lanes into different areas of responsibility. 

But we also use more traditional card walls for our Day to day dev streams . 

I agree with you i just think you have adapt and do what is best in your environment. 
neil</description>
		<content:encoded><![CDATA[<p>Simon<br />
I have to say i also run super fast sprints to do clean down defect runs and in preparation for releases and they can last 2 days. </p>
<p>We dont even bother with a card wall for these we use a big white board and we list them and then the pairs just walk up and cross them off as the defect is fixed and passed to QA. I think its about doing what is right for your environment. </p>
<p>We quite often for focused developments use LEAN style card walls pulling the cards through the lanes into different areas of responsibility. </p>
<p>But we also use more traditional card walls for our Day to day dev streams . </p>
<p>I agree with you i just think you have adapt and do what is best in your environment.<br />
neil</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Groundhog Agile by Neil Martin</title>
		<link>http://theagilevoice.co.uk/2009/04/21/groundhog-agile/#comment-3385</link>
		<author>Neil Martin</author>
		<pubDate>Thu, 30 Apr 2009 21:38:55 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/04/21/groundhog-agile/#comment-3385</guid>
		<description>Simon 
I think i have commented on this in your blog elsewhere but i think a lot of it is about keeping it fresh. Teaching the ability to adapt. I don't think any one thing can work forever everything has its season. 

Some times as well in terms of the business there has to be room for compromise you have to be prepared to understand the business presures upon the KDM's and principals and be prepared to adapt your practises to accomodate this ever changing land scape. 
 Neil</description>
		<content:encoded><![CDATA[<p>Simon<br />
I think i have commented on this in your blog elsewhere but i think a lot of it is about keeping it fresh. Teaching the ability to adapt. I don&#8217;t think any one thing can work forever everything has its season. </p>
<p>Some times as well in terms of the business there has to be room for compromise you have to be prepared to understand the business presures upon the KDM&#8217;s and principals and be prepared to adapt your practises to accomodate this ever changing land scape.<br />
 Neil</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Kanban - Simplistic Agile? by Ged Byrne</title>
		<link>http://theagilevoice.co.uk/2009/02/03/kanban-simplistic-agile/#comment-3332</link>
		<author>Ged Byrne</author>
		<pubDate>Tue, 28 Apr 2009 09:33:51 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/02/03/kanban-simplistic-agile/#comment-3332</guid>
		<description>... a simple, visible method be used to demonstrate production flow.  

Is there also a specific software practice that has taken on the name?</description>
		<content:encoded><![CDATA[<p>&#8230; a simple, visible method be used to demonstrate production flow.  </p>
<p>Is there also a specific software practice that has taken on the name?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Kanban - Simplistic Agile? by Ged Byrne</title>
		<link>http://theagilevoice.co.uk/2009/02/03/kanban-simplistic-agile/#comment-3331</link>
		<author>Ged Byrne</author>
		<pubDate>Tue, 28 Apr 2009 09:31:22 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/02/03/kanban-simplistic-agile/#comment-3331</guid>
		<description>Interesting article, but I'm curious about what you mean by 'Kanban'.

I'm familiar with Kanban from the Toyota Production System, the key principle being that</description>
		<content:encoded><![CDATA[<p>Interesting article, but I&#8217;m curious about what you mean by &#8216;Kanban&#8217;.</p>
<p>I&#8217;m familiar with Kanban from the Toyota Production System, the key principle being that</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Conferences - Is there a future for them? by Peter Marshall</title>
		<link>http://theagilevoice.co.uk/2009/03/18/agile-conferences-is-there-a-future-for-them/#comment-1461</link>
		<author>Peter Marshall</author>
		<pubDate>Sun, 29 Mar 2009 12:18:59 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/03/18/agile-conferences-is-there-a-future-for-them/#comment-1461</guid>
		<description>I would certainly like to see those speakers at agile conferences speaking outside of the theories and to push forward agile. Coming from a test background, I am still surprised at the amount of key speakers that play down the importance of test practices within agile. Only being able to describe testing in a very theoretical form, i.e. automated unit testing. This, to me, identifies that many of these speakers are far too detached from the realities of agile practices. Most being consultants selling projects rather than actually experiencing what is actually happening on the front line. 

Agile testing is a blossoming engineering practice, and needs support from speakers at these conferences.</description>
		<content:encoded><![CDATA[<p>I would certainly like to see those speakers at agile conferences speaking outside of the theories and to push forward agile. Coming from a test background, I am still surprised at the amount of key speakers that play down the importance of test practices within agile. Only being able to describe testing in a very theoretical form, i.e. automated unit testing. This, to me, identifies that many of these speakers are far too detached from the realities of agile practices. Most being consultants selling projects rather than actually experiencing what is actually happening on the front line. </p>
<p>Agile testing is a blossoming engineering practice, and needs support from speakers at these conferences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Conferences - Is there a future for them? by Chris Pitts</title>
		<link>http://theagilevoice.co.uk/2009/03/18/agile-conferences-is-there-a-future-for-them/#comment-1218</link>
		<author>Chris Pitts</author>
		<pubDate>Wed, 25 Mar 2009 13:42:20 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/03/18/agile-conferences-is-there-a-future-for-them/#comment-1218</guid>
		<description>I think you're right. The conferences I have been to over the past two years seem to have simply rehashed what went before - not always a bad thing, I certainly learned new tricks - but devaluing the whole conference scene as you say.

IMO Doing is the new Talking. We now have plenty of people out there able to talk the talk fluently, but can they walk the walk? Just how many projects are truly successful and productive? Personally I would like to see more published detailed case studies to identify what works, what does not, and open, honest discussions as to why.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re right. The conferences I have been to over the past two years seem to have simply rehashed what went before - not always a bad thing, I certainly learned new tricks - but devaluing the whole conference scene as you say.</p>
<p>IMO Doing is the new Talking. We now have plenty of people out there able to talk the talk fluently, but can they walk the walk? Just how many projects are truly successful and productive? Personally I would like to see more published detailed case studies to identify what works, what does not, and open, honest discussions as to why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sprint or Marathon? by Simon</title>
		<link>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-25</link>
		<author>Simon</author>
		<pubDate>Fri, 13 Feb 2009 15:49:32 +0000</pubDate>
		<guid>http://theagilevoice.co.uk/2009/02/13/sprint-or-marathon/#comment-25</guid>
		<description>What I was trying to say was that the definition of Agile itself does not need changing (The main aims, ie. the external behaviour, do remain unchanged), but some of the processes and policies have evolved so perhaps they need redefining.</description>
		<content:encoded><![CDATA[<p>What I was trying to say was that the definition of Agile itself does not need changing (The main aims, ie. the external behaviour, do remain unchanged), but some of the processes and policies have evolved so perhaps they need redefining.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

