<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>The Agile Tribe - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-8fd37269" type="application/json"/><link>http://theagiletribe.disqus.com/</link><description></description><atom:link href="http://theagiletribe.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 11 Jan 2012 02:32:30 -0000</lastBuildDate><item><title>Re: The Quick and The Dead&amp;#8230;&amp;#8230;&amp;#8230;&amp;#8230;&amp;#8230;.</title><link>http://www.theagiletribe.net/index.php/2011/12/20/the-quick-and-the-dead/#comment-407679124</link><description>&lt;p&gt;Thanks MB.  I just finished reading your blog series on what ET is not today.  A great read indeed.  &lt;/p&gt;

&lt;p&gt;I also have a copy of Jerry's book (Perfect Software).  That's next on the to do list.  Will add the other to the to buy list.&lt;/p&gt;

&lt;p&gt;As always, thanks for sharing your knowledge with everyone.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Greenlees</dc:creator><pubDate>Wed, 11 Jan 2012 02:32:30 -0000</pubDate></item><item><title>Re: The Quick and The Dead&amp;#8230;&amp;#8230;&amp;#8230;&amp;#8230;&amp;#8230;.</title><link>http://www.theagiletribe.net/index.php/2011/12/20/the-quick-and-the-dead/#comment-390793885</link><description>&lt;p&gt;Thank you for adding a link to my blog.  If you liked that, there's a more recent one that may pique your interest:  &lt;a href="http://www.developsense.com/blog/2011/12/what-exploratory-testing-is-not-part-4-quick-tests/" rel="nofollow"&gt;http://www.developsense.com/bl...&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In addition to that, I strongly recommend Jerry Weinberg's &lt;i&gt;Perfect Software and Other Illusions About Testing&lt;/i&gt;, and his &lt;i&gt;Secrets of Consulting&lt;/i&gt;, too.&lt;/p&gt;

&lt;p&gt;Cheers,&lt;/p&gt;

&lt;p&gt;---Michael B.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Bolton</dc:creator><pubDate>Tue, 20 Dec 2011 12:56:29 -0000</pubDate></item><item><title>Re: Agile, What&amp;#8217;s in a Name?</title><link>http://www.theagiletribe.net/index.php/2011/08/16/agile-whats-in-a-name/#comment-386640033</link><description>&lt;p&gt;Very truly said about people Misunderstanding the concept of agile and managing it the "non agile " way and reasoning agile to be failure.&lt;br&gt;If we understand the process, roles and responsibility that agile defines is so easy and helps us manage the project more structured way. &lt;br&gt;the only point i would like to clarify is thaet "agile does not mean no documentation" mean it never says about not having documentation for the project, but only appropriate documentation can be followed&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Deepak Dhananjaya</dc:creator><pubDate>Wed, 14 Dec 2011 14:16:36 -0000</pubDate></item><item><title>Re: Why so little good Agile?</title><link>http://www.theagiletribe.net/index.php/2011/05/09/why-so-little-good-agile/#comment-386555370</link><description>&lt;p&gt;&lt;/p&gt;

&lt;p&gt;The problem seems to be that the Agile Manifesto is not abstract&lt;br&gt;enough:&lt;br&gt;&lt;br&gt;&lt;/p&gt;

&lt;p&gt; &lt;/p&gt;

&lt;p&gt;For defining Agile we should focus on &lt;strong&gt;the goal of&lt;br&gt;Agile&lt;/strong&gt; rather than on the misleading, very problematic way&lt;br&gt;suggested by the authors of the Manifesto: Please read &lt;/p&gt;

&lt;p&gt;&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="http://greiterweb.de/spw/dox/The_New_(2011)_Definition_of_Agile.pdf" rel="nofollow"&gt;The&lt;br&gt;New (2011) Definitions of Agile&lt;/a&gt;, or&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.greiterweb.de/spw/Agile_is_not_Manifesto.htm" rel="nofollow"&gt;Agility&lt;br&gt;is fine – though the Manifesto can be Poison&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;&amp;lt;/li&amp;gt;&lt;/p&gt;

&lt;p&gt;&amp;lt;/ul&amp;gt;&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Grtgrt</dc:creator><pubDate>Wed, 14 Dec 2011 12:16:40 -0000</pubDate></item><item><title>Re: Three Truths</title><link>http://www.theagiletribe.net/index.php/2011/09/06/three-truths/#comment-305777140</link><description>&lt;p&gt;Your first point is spot on! Not only that, larger teams increase communication channels. I have published on the &lt;a href="http://www.pmhut.com/advantages-of-small-project-teams" rel="nofollow"&gt;advantages of small teams&lt;/a&gt; before. I think the ideal number of team members is 5, less than that you really don't have a team, and more than that you will spend more time resolving conflicts and motivating team members than actually doing something productive.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PM Hut</dc:creator><pubDate>Fri, 09 Sep 2011 05:31:58 -0000</pubDate></item><item><title>Re: Three Truths</title><link>http://www.theagiletribe.net/index.php/2011/09/06/three-truths/#comment-303855520</link><description>&lt;p&gt;Agreed, great article.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Zheng</dc:creator><pubDate>Tue, 06 Sep 2011 19:21:49 -0000</pubDate></item><item><title>Re: Agile, What&amp;#8217;s in a Name?</title><link>http://www.theagiletribe.net/index.php/2011/08/16/agile-whats-in-a-name/#comment-293389168</link><description>&lt;p&gt;That's true...have seen it happening when a lack of planning, accountability, tracking, dcoumentation, structured approach, is conveneintly covered under the term 'AGILE METHODOLOGY'..&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Seema A</dc:creator><pubDate>Mon, 22 Aug 2011 21:30:02 -0000</pubDate></item><item><title>Re: Agile, What&amp;#8217;s in a Name?</title><link>http://www.theagiletribe.net/index.php/2011/08/16/agile-whats-in-a-name/#comment-287895073</link><description>&lt;p&gt;Nice one Peter. Can't agree more. Don't abusing and start using Agile correctly!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Susan Akers</dc:creator><pubDate>Tue, 16 Aug 2011 01:26:13 -0000</pubDate></item><item><title>Re: What&amp;#8217;s your role in an Agile team?</title><link>http://www.theagiletribe.net/index.php/2011/07/25/whats-your-role-in-an-agile-team/#comment-263110855</link><description>&lt;p&gt;sweet. nice!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Saddington</dc:creator><pubDate>Sun, 24 Jul 2011 20:24:40 -0000</pubDate></item><item><title>Re: Agile Australia through the looking glass</title><link>http://www.theagiletribe.net/index.php/2011/07/07/agile-australia-through-the-looking-glass/#comment-250084090</link><description>&lt;p&gt;Thanks Agile Scout&lt;/p&gt;

&lt;p&gt;It was quite an insightful event there are so many more things I could have mentioned.. and I will... briefly.. just one.&lt;/p&gt;

&lt;p&gt;In the open space I discovered that agile change needs to be delivered gently and sometimes without the mention of the word agile at all. If you are in a position to, you can point out that something is not working well and that you would like to try something else for a while to see if it works better. It's as simple as that! &lt;/p&gt;

&lt;p&gt;This correlated with my own experience with people's knee jerk reactions to the word agile, it can conjure up fear, anxiety and a whole heap of other emotional responses. Those who are unfamiliar with agile can have a tendency to view it incorrectly as either the silver bullet for everything or just another werewolf process that devours more of their precious time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wayne Allan</dc:creator><pubDate>Tue, 12 Jul 2011 23:38:37 -0000</pubDate></item><item><title>Re: Agile Australia through the looking glass</title><link>http://www.theagiletribe.net/index.php/2011/07/07/agile-australia-through-the-looking-glass/#comment-245562714</link><description>&lt;p&gt;Thanks Peter.  Put in a paper for next year's conference so we can get to catch up.  :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AgileTribe</dc:creator><pubDate>Thu, 07 Jul 2011 21:11:00 -0000</pubDate></item><item><title>Re: Agile Australia through the looking glass</title><link>http://www.theagiletribe.net/index.php/2011/07/07/agile-australia-through-the-looking-glass/#comment-244979413</link><description>&lt;p&gt;This is awesome. Wish I could have been there!!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Saddington</dc:creator><pubDate>Thu, 07 Jul 2011 08:37:24 -0000</pubDate></item><item><title>Re: Welcome</title><link>http://www.theagiletribe.net/index.php/2009/07/15/hello-world/#comment-244978787</link><description>&lt;p&gt;Keep up the good work!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Saddington</dc:creator><pubDate>Thu, 07 Jul 2011 08:36:56 -0000</pubDate></item><item><title>Re: The Definition of Done</title><link>http://www.theagiletribe.net/index.php/2011/06/27/the-definition-of-done/#comment-242419204</link><description>&lt;p&gt;Hey - I've just walked the team through a definition of done workshop.  Was lucky enough to have a great team.  As we walked through what a story card would go through to be 'done' we captured what this means for our swimlanes on the wall.   What was "Done" for inprogress.  what was "done" for testing, &amp;amp; signoff.  What was "Done" for "Done".    I've shared this link with the team - thanks for this!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jonathan_coleman</dc:creator><pubDate>Tue, 05 Jul 2011 01:58:07 -0000</pubDate></item><item><title>Re: People Issues and performance reviews &amp;#8211; Team Leader or Iteration Manager?</title><link>http://www.theagiletribe.net/index.php/2011/06/20/people-issues-and-performance-reviews-team-leader-or-iteration-manager/#comment-231527590</link><description>&lt;p&gt;Thanks Renee,  Since giving the talk a number of people have raised examples that will change the relationship between the TL and IM.  Examples like distributed project teams where the IM has multiple TLs to consider and split teams where the TL has multiple IMs for interaction. Both of these project types and your operational example will change the IM vs TL relationship but the principles of "keeping close" for each of the above eight recommendations should still apply.  We still value collaboration, interactions and transparency.  How can we bring these values to play in the IM and TL relationship?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Jenkins</dc:creator><pubDate>Tue, 21 Jun 2011 22:23:00 -0000</pubDate></item><item><title>Re: Why so little good Agile?</title><link>http://www.theagiletribe.net/index.php/2011/05/09/why-so-little-good-agile/#comment-230929674</link><description>&lt;p&gt;Thanks for the comments Renee - you're right about the fine line.  I'm not in favor of fanatical adherence to a set of rules as a replacement for considered thinking; find the set of practices that work together to enable the most effective delivery of value to customers, but make sure it is about effectively delivering value not about using the label agile to justify doing sloppy work.&lt;/p&gt;

&lt;p&gt;My tirade is aimed at teams and organizations that pick up a few practices that look easy without understanding how the various practices interact together to create a system to deliver customer value effectively.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shane Hastie</dc:creator><pubDate>Tue, 21 Jun 2011 08:14:40 -0000</pubDate></item><item><title>Re: People Issues and performance reviews &amp;#8211; Team Leader or Iteration Manager?</title><link>http://www.theagiletribe.net/index.php/2011/06/20/people-issues-and-performance-reviews-team-leader-or-iteration-manager/#comment-230904927</link><description>&lt;p&gt;Nice write up Steven. Do you see the TL vs IM relationship behaving differently in a more operational rather than project area?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Renee Troughton</dc:creator><pubDate>Tue, 21 Jun 2011 07:04:45 -0000</pubDate></item><item><title>Re: Just give me a &amp;#8216;G &amp;#038; T&amp;#8217;!</title><link>http://www.theagiletribe.net/index.php/2011/05/23/just-give-me-a-g-t/#comment-214522968</link><description>&lt;p&gt;Thanks for your comments Adam and Matthias. There are probably at least another 100 acronyms out there in the Scrum/Agile world and I agree Adam that if your audience is knowlegdable you can get away with some acronyms.  The big mistake that people make is that they ASSUME they know their audience and so that they will understand but experience has certainly proven to me and also surprised me that some things you take as basic acronyms are not understood. That's the risk!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AgileTribe</dc:creator><pubDate>Mon, 30 May 2011 20:18:55 -0000</pubDate></item><item><title>Re: Just give me a &amp;#8216;G &amp;#038; T&amp;#8217;!</title><link>http://www.theagiletribe.net/index.php/2011/05/23/just-give-me-a-g-t/#comment-214171133</link><description>&lt;p&gt;IMHO Susan - I do think acronyms have their place.  They are after all about efficiency, that is – getting your message across as quickly as possible.  Sometimes the brain is working faster than the mouth and getting all those long words out just slows you down.  A handy set of acronyms with a knowledgeable audience gets you there quicker.  It’s like software usability – for the novice users you need nice elaborate GUIs that explain it all, however for the power user a green screen (or 3270 for the ultimate acronym) will get the job done faster!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam Spencer</dc:creator><pubDate>Mon, 30 May 2011 05:18:59 -0000</pubDate></item><item><title>Re: &amp;#8216;A Rose by any other name?&amp;#8217;</title><link>http://www.theagiletribe.net/index.php/2011/04/28/a-rose-by-any-other-name/#comment-214041675</link><description>&lt;p&gt;Thanks for your comments Todd , much appreciated .&lt;/p&gt;

&lt;p&gt;I personally have concerns with evangelism and the use of the term . &lt;/p&gt;

&lt;p&gt;Agile was once the doyen of the software community , now however more than ever, non software teams are practicing Agile. &lt;/p&gt;

&lt;p&gt;Once particular stakeholder recently saw this word used in a coaching&lt;br&gt;mission statement and immediately stated that he associated it with&lt;br&gt;preaching.&lt;/p&gt;

&lt;p&gt;So the point I was attempting to  convey is to be sure we step outside&lt;br&gt;the dogma of evangelising the perfect dot point adoption of Agile and&lt;br&gt;be pragmatic about how we coach ,espouse and aid it's adoption. &lt;/p&gt;

&lt;p&gt;I wrote this post after a number of these interactions with non software teams and being introduced to the &lt;br&gt;&lt;/p&gt;

&lt;p&gt;"Oath of Non Allegiance" by Alistair Cockburn , which reads : &lt;/p&gt;

&lt;p&gt;I promise not to exclude from consideration any idea based on its&lt;br&gt;source, but to consider ideas across schools and heritages in order to&lt;br&gt;find the ones that best suit the current situation.Hope thhis clarifies my intent and thoughts - Cheers &lt;br&gt; &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tony Ponton</dc:creator><pubDate>Sun, 29 May 2011 21:39:55 -0000</pubDate></item><item><title>Re: &amp;#8216;A Rose by any other name?&amp;#8217;</title><link>http://www.theagiletribe.net/index.php/2011/04/28/a-rose-by-any-other-name/#comment-213089374</link><description>&lt;p&gt;I whole-heartedly agree, but I am curious that you warn us to remain "pragmatists" not "evangelists". I mean, sure, there's no need to be self-righteous and dogmatic, but I thought the software community had already adopted the word "evangelist" to mean something a bit different to its original religious connotations. You see the job title "technology evangelist" popping up quite a bit these days, and I think it reflects the realization that new technologies need more than just technical excellence to succeed -- they also need passionate supporters and advocates.&lt;/p&gt;

&lt;p&gt;By that definition, this blog itself would be an example of evangelism!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Todd Owen</dc:creator><pubDate>Fri, 27 May 2011 20:52:28 -0000</pubDate></item><item><title>Re: &amp;#8216;A Rose by any other name?&amp;#8217;</title><link>http://www.theagiletribe.net/index.php/2011/04/28/a-rose-by-any-other-name/#comment-211412088</link><description>&lt;p&gt;My detailed thoughts as conveyed to Tony on this - &lt;br&gt;&lt;a href="http://agileforest.com/2011/05/25/a-converse-view/" rel="nofollow"&gt;http://agileforest.com/2011/05...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Renee Troughton</dc:creator><pubDate>Wed, 25 May 2011 06:14:33 -0000</pubDate></item><item><title>Re: Why so little good Agile?</title><link>http://www.theagiletribe.net/index.php/2011/05/09/why-so-little-good-agile/#comment-211411596</link><description>&lt;p&gt;" Please stop calling these half-hearted implementations Agile – it’s not, it’s just a continuation of the bad practices that many organisations have followed over the years, just with a different brand." I couldn't agree more.&lt;/p&gt;

&lt;p&gt; I did find it interesting that your post was slightly at odds with Tony's right below. &lt;br&gt; &lt;br&gt;There is a fine line between being adaptive and pragmatic tailoring vs going too far. &lt;/p&gt;

&lt;p&gt;For context of a more ellaborative thoughts - &lt;a href="http://agileforest.com/2011/05/25/a-converse-view/" rel="nofollow"&gt;http://agileforest.com/2011/05...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Renee Troughton</dc:creator><pubDate>Wed, 25 May 2011 06:13:55 -0000</pubDate></item><item><title>Re: Just give me a &amp;#8216;G &amp;#038; T&amp;#8217;!</title><link>http://www.theagiletribe.net/index.php/2011/05/23/just-give-me-a-g-t/#comment-209740887</link><description>&lt;p&gt; If you dive deeper into Scrum, there are some more:&lt;br&gt;SM (ScrumMaster), PO (ProductOwner), and the good, old "chickens" and "pigs" ;-) &lt;br&gt;Are those acronyms helpful for getting more buy in through the company? No way...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthias Marschall</dc:creator><pubDate>Mon, 23 May 2011 04:35:52 -0000</pubDate></item><item><title>Re: The Family Agile</title><link>http://www.theagiletribe.net/index.php/2011/04/27/the-family-agile/#comment-206633424</link><description>&lt;p&gt;Unfortunately I did not take any pics or the wall. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shawn Wallace</dc:creator><pubDate>Thu, 19 May 2011 00:09:48 -0000</pubDate></item></channel></rss>
