Comments on: What iteration-less agile really means

By: Amit Rathore

Amit Rathore — Sun, 05 Apr 2009 19:33:47 +0000

What you’re suggesting is that the people you’re working with think they’re experts and that using an “iteration-less” approach is equivalent to having no process.

Two comments here -

1. No methodology can help you if the people you have aren’t good at what they do. And usually, smart software developers grok the idea of iteration-less agile – often they gravitate towards something like it on their own. It just takes a team that keeps delivering results and is still focused on self-improvement.

2. The idea of this being development “without a process” sounds familiar to me -it was exactly what all the critics of agile methods said when the world was first transitioning from waterfall. The truth of the matter is that going iteration-less requires even more discipline than is required by a waterfall team going agile.

By: NavXaidi

NavXaidi — Thu, 26 Mar 2009 18:06:50 +0000

I think this is something that I am already fighting against.
I am sorry if it sounds roude but
- imagine a group of people who think that they are the experts!
- Now imagine that they are working without a process.
What can you imagine they will be doing?
they will certainly be doing it the way I happen to perceive the idea of iteration less methodology.
Then there are some questions.
- Where will we adjust Reviews and planning?
- what will keep focus of the team?
- How can lean satisfy stake-holder’s changing bussniss requirements?

My comments may have made someone upset (due to may be spelling mistakes …)Please ! accept my appologies.

By: Startup logbook - Clojure in production - release v0.1 « s-expressions

Startup logbook - Clojure in production - release v0.1 « s-expressions — Wed, 28 Jan 2009 09:45:30 +0000

[...] same time (and getting paid for doing that!), it has also been a great opportunity to do this as incrementally as possible. I strongly believe in set-based engineering methods, and this is the approach I took [...]

By: Design for throwability « s-expressions

Design for throwability « s-expressions — Fri, 16 Jan 2009 09:02:41 +0000

[...] way we accomplish this is through extremely loose-coupling. In our case, we take a very release-driven approach to our software process. So our architecture evolves according to our current needs… [...]

By: Eric Willeke

Eric Willeke — Mon, 03 Nov 2008 14:42:18 +0000

Good post, but I do have to disagree with you about the “He didn’t recommend it for any but the most experienced team – and I certainly agree with that” There’s a very deep thread going on over at the kanbandev group right now… I’m going to link to one of my posts on the topic that directly addresses this, but the entire thread it worth a read.

http://finance.groups.yahoo.com/group/kanbandev/message/965