Comments on: Introduction to Lean Software Development

By: Herb Richter

Herb Richter — Fri, 12 Feb 2010 21:58:13 +0000

I am pursuing my Lean Six Sigma Black Belt and have many years in application development. How about taking this thinking one step further and apply Lean Six Sigma to applications development? Lean alone is not enough and adding Six Sigma is not enough. Lean Six Sigma takes the best of both to add more value combined than it would separately.

By: Agile and Lean Software Development - an Oxymoron? | Agile Blog: Scaling Software Agility

Tue, 22 Sep 2009 03:56:31 +0000

[...] Though the principles of the Agile Manifesto do not sound like the principles of Lean, the patterns are the same. (For a great overview of Lean software do not miss Corey Ladas’ guest post on Shaping Software.) [...]

By: Guest articles at Shaping Software | Lean Software Engineering

Guest articles at Shaping Software | Lean Software Engineering — Mon, 22 Jun 2009 18:24:24 +0000

[...] Introduction to Lean Software Development [...]

By: Powerful Consulting - #2 — Practice This

Powerful Consulting - #2 — Practice This — Sun, 21 Jun 2009 20:16:27 +0000

[...] is interesting that the original law resonates with one of the principals of Lean Software Development – defer commitments. Consultant should offer options and tools for decisions. It’s up to the [...]

By: Brian

Brian — Thu, 18 Jun 2009 13:44:35 +0000

Nice article! I’m completing my business/IT degree now after many years working in IT companies both large and small. I have now covered these Lean systems approaches from both operations management and software engineering perspectives.
I think the core concept that can be applied to software engineering is that quality is determined by the customer, and if what we’re doing doesn’t benefit them, in a way thats visible and tangible to them, then we probably shouldn’t be doing it at all. This can as often be a matter of managing expectations as it of design or delivery.
Most of us are in IT because we love learning the latest tools and playing with the new technology. But I’ve seen many projects go to hell in a handbasket when a clever engineer pushed for something the customer didn’t want or really need. In the end the customer ends up disappointed by either the quality, timing or cost of the project, and thats not good for us as developers or vendors.

By: Corey

Corey — Wed, 17 Jun 2009 20:56:07 +0000

I appreciate the comments. Interesting that they all focus on continuous improvement. That is a big part of what we’ve been after: creating conditions where improvement is understandable and possible in the real world, and not just an empty slogan. Focus on limiting work in process and delivering work in small batches all the way through deployment makes problems and opportunities to improve more obvious to everybody.

By: Ted

Ted — Wed, 17 Jun 2009 15:51:19 +0000

Six Sigma and continuous improvement are core Japanese business practices. Improving efficiency, creating value and reducing cost are its main points.

Mass production (e.g., cars) was focused on value/quality/efficiency (Toyota) or decorative add ons (GM/Ford). GM/Ford built a few core car platforms and then added items only for looks (tailfins, pin stripes, etc.) instead of improving efficiency, adding real value and building in better quality. This is why Toyota does better than GM. Toyota/Honda limited their franchise numbers (number of dealerships) while GM/Ford sold too many franchises.

By: Praveen

Praveen — Tue, 16 Jun 2009 16:10:11 +0000

Thanks Corey (and JD) for bringing this piece together. Honestly, I was unaware of “Kaizen” till today. I have been doing all sorts of reading on Kaizen, Toyota’s model and others.
I also read an article on how GM should have adopted Toyota’s philosophy, instead of their “command & control” approach. Apparently they have been having problems with their model since early 90s, and did little to change it. On the contrary, Wipro, an IT company based out of India, adopted the model and has seen success & growth (improvement to the tune of 43%).
I’m quite sure Kaizen is not meant for a one man s/w team (my case), but I plan to learn & master it, and adopt it for life itself.

Thank you.

By: James Waletzky

James Waletzky — Tue, 16 Jun 2009 15:24:59 +0000

Nice article, Cory! Great introduction to Lean/Agile in software development. I generally focus on the principles behind lean and agile, with their intersection creating my rules of software development. There are great ideas in both camps, and it makes total sense to combine those, IMHO. As long as I focus on the principles, I can leverage the practices that abide by those principles, or even invent my own and be successful.

Thanks again!

By: Alik Levin | PracticeThis.com

Alik Levin | PracticeThis.com — Mon, 15 Jun 2009 18:54:25 +0000

I think these principles are universal:
* Eliminate Waste
* Create Knowledge
* Build Quality In
* Defer Commitment
* Deliver Fast
* Respect People
* Improve the System
It resonates a lot with Kaizen practiced by Toyota.
Love these principles, love Kaizen!