Comments on: Lean software development: An iteration-less agile process

By: Tim Stokes

Tim Stokes — Wed, 11 Feb 2009 20:00:31 +0000

I like it. Source control tools used in the correct way could empower a development team to do all this while still providing a releasable set of features at any given point of time. Perfect!

By: Bookmarks for November 14th through November 16th | Bieber Labs

Bookmarks for November 14th through November 16th | Bieber Labs — Sun, 16 Nov 2008 16:00:19 +0000

[...] Lean software development: An iteration-less agile process « epistemologic – "I thought I’d present my reasoning as a set of statements that together build up the argument. I’ll try to address the following things – business analysis, estimation and tasking, ensuring communication, iterations, requirements prioritization, planning, showcasing and closure, taking breaks. There’s probably more, but these are the areas where most people ask questions about this approach." [...]

By: What iteration-less agile really means « epistemologic

What iteration-less agile really means « epistemologic — Mon, 03 Nov 2008 08:55:02 +0000

[...] Why work at ThoughtWorks?Rajani on Why work at ThoughtWorks?thekua.com@work … on Lean software development: An …Fahad Nari on Why work at ThoughtWorks?Rajani on Why work [...]

By: thekua.com@work » Why timeboxing is important

thekua.com@work » Why timeboxing is important — Sun, 12 Oct 2008 20:23:46 +0000

[...] approach. Wayne Allen talks of trialling No More Iterations, while Amit Rathore talks about an iteration-less agile process. Heck, I’ve even given it a go with a couple of my projects. On the other hand, there’s [...]

By: Encore plus Agile: l’utilité des itérations : Blog | Focus Intelligence

Encore plus Agile: l’utilité des itérations : Blog | Focus Intelligence — Wed, 25 Jun 2008 13:06:44 +0000

[...] article intéressant, et même très intéressant que j’ai récemment lu ici, sur la réelle utilité d’une itération. L’approche au problème est très intéressante. Je [...]

By: A Project Delivery Sanity Test « epistemologic

A Project Delivery Sanity Test « epistemologic — Sat, 23 Feb 2008 18:35:39 +0000

[...] Posts Agile estimation – story points vs. hoursHow Lean and Agile are different, not that it mattersLean software development: An iteration-less agile processLean Software Development: How to find bottlenecks – Metrics that MatterWhy work at [...]

By: Amit Rathore

Amit Rathore — Thu, 22 Nov 2007 00:59:31 +0000

I guess I do. Basically, what I’m saying is that the typical time-based window called Iterations are an artificial construct, you don’t strictly need them to be successful. You can basically treat each feature – taking it from concept to deployment – as an ‘iteration’. This is the idea of an ‘iteration-less’ agile approach.