Comments for The Agile Tribe

Comment on The Quick and The Dead……………. by David Greenlees

David Greenlees — Wed, 11 Jan 2012 07:32:00 +0000

Thanks MB. I just finished reading your blog series on what ET is not today. A great read indeed.

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.

As always, thanks for sharing your knowledge with everyone.

Comment on The Quick and The Dead……………. by Michael Bolton

Michael Bolton — Tue, 20 Dec 2011 17:56:00 +0000

Thank you for adding a link to my blog. If you liked that, there’s a more recent one that may pique your interest: http://www.developsense.com/blog/2011/12/what-exploratory-testing-is-not-part-4-quick-tests/

In addition to that, I strongly recommend Jerry Weinberg’s Perfect Software and Other Illusions About Testing, and his Secrets of Consulting, too.

Cheers,

—Michael B.

Comment on Agile, What’s in a Name? by Deepak Dhananjaya

Deepak Dhananjaya — Wed, 14 Dec 2011 19:16:00 +0000

Very truly said about people Misunderstanding the concept of agile and managing it the “non agile ” way and reasoning agile to be failure.
If we understand the process, roles and responsibility that agile defines is so easy and helps us manage the project more structured way.
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

Comment on Why so little good Agile? by Grtgrt

Grtgrt — Wed, 14 Dec 2011 17:16:00 +0000

The problem seems to be that the Agile Manifesto is not abstract enough: For defining Agile we should focus on the goal of Agile rather than on the misleading, very problematic way suggested by the authors of the Manifesto: Please read The New (2011) Definitions of Agile, or Agility is fine – though the Manifesto can be Poison

Comment on Three Truths by PM Hut

PM Hut — Fri, 09 Sep 2011 09:31:00 +0000

Your first point is spot on! Not only that, larger teams increase communication channels. I have published on the advantages of small teams 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.

Comment on Three Truths by David Zheng

David Zheng — Tue, 06 Sep 2011 23:21:00 +0000

Agreed, great article.

Comment on Agile, What’s in a Name? by Seema A

Seema A — Tue, 23 Aug 2011 01:30:00 +0000

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’..

Comment on Agile, What’s in a Name? by Susan Akers

Susan Akers — Tue, 16 Aug 2011 05:26:00 +0000

Nice one Peter. Can’t agree more. Don’t abusing and start using Agile correctly!

Comment on What’s your role in an Agile team? by Agile Scout

Agile Scout — Mon, 25 Jul 2011 00:24:00 +0000

sweet. nice!

Comment on Agile Australia through the looking glass by Wayne Allan

Wayne Allan — Wed, 13 Jul 2011 03:38:00 +0000

Thans Agile Scout

It was quite insightful event there are so many more things I could have mentioned.. and I will… briefly.. just one.

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!�
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.