Talk:Lean software development/Archives/2014

Untitled
Hi  —Preceding unsigned comment added by 117.241.83.135 (talk) 12:00, 15 July 2010 (UTC)

Apart from the fact that it contains some great ideas i cannot really see any strong link between these ideas and Lean apart from its choice as part of a catchy title. Waste reduction relates to so many methodologies that this specific choice is perhaps arbitrary. Can the inclusion in the Lean concepts category be defended by anyone ? Facius 11:46, 10 October 2007 (UTC)


 * To reply to some of the comments above...Lean software development is a recognized, but very new area (<4 years). It is not at all obvious how to apply Lean principles to software development, or why we should.  The Poppendiecks wrote the book(s) on the subject, so it is somewhat understandable that much of the content be biased towards them.   DukeyToo (talk) 17:04, 31 December 2007 (UTC)


 * I agree that the article needs a lot of improvement. While it was helpful to me in getting up to speed on Lean principles, it does not read like an encyclopedia entry.  As a first step, I've cleaned up the language in a few sections and added some internal links to other articles.  Qwirty (talk) 18:54, 6 February 2008 (UTC)


 * I can see how this article needs improvement, but as to the "Lean Concepts" category, that's a discussion for a different page (the category page). If the category itself has merit, then this page should (in some modified form) be included. As the above suggests, Tom and Mary's book is probably going to take centre stage, since it's the (currently) definitive translation of the concepts from Toyota into software.  However there are other sources which can be cited, and I'll try to work on it. --Christian Edward Gruber (talk) 17:22, 31 March 2008 (UTC)

Eliminate Waste - low quality must not always be waste
"Defects and lower quality are waste". I wouldn't accept this sentence. If a low quality product is sold it generates value and everything that is value cannot be waste at the same time. Though I agree that lower quality should be avoided, since it either increases costs of maintainance or leads to product failure. But I think Poppendieck also mentioned the pareto rule in some of her books. So it can be quite the opposite: "too high quality is waste"

I have touched this in m german blog: http://kleffels-software-blog.de/?p=1300 — Preceding unsigned comment added by 109.84.151.233 (talk) 17:05, 1 February 2014 (UTC)

Origin
The beginning of the page (origins) is clearly wrong, since the Poppendiecks published a paper in Dr. Dobb's with the "lean" title in 2001, two years before their book, but also because there is a 1995 article by Niklaus Wirth (IEEE Computer, February) entitled "Plea for Lean Software". Of course it is not a full-fledged development method but it has many elements in common with that method, and one cannot say that the term originated with the 2003 book. B-Meyer (talk) 14:13, 6 October 2013 (UTC)

I did a SQA course in 1993 which talked about applying lean principles to software development. 07:53, 31 March 2014 (UTC) — Preceding unsigned comment added by 203.41.222.1 (talk)