At a recent meet up of the Bay Area Agile Managers Support Group. Alan Shalloway presented on Lean-Agile for Managers. He explained that agile is about small batches, lean about managing the flow. The key is to speed the time between any work and the corresponding feedback. Delays cost more than time. They almost always cause additional work. In software development, it’s very easy for a developer to fix a bug that he just introduced. It’s hard to fix a bug that was introduced weeks or months ago. And it’s easier to implement requirements that have just been collected rather than requirements that have gone stale and lost their meaning. Writing down requirements helps, but that is extra work. And regardless, meaning still gets lost over time.
While I had thought that lean only applies to manufacturing, Alan Shalloway made a strong case. Managers must better coordinate flow, moving as quickly as possible from concept to consumption. Delays cost more than is often realized.
Does anybody have any experience using Lean with software development?
We’ve been using Kanban during 1.5 years already at TargetProcess and it works better than Scrum for our team. We are using small batches, minimizing wait cycles, develop by feature and so on. Lean can be very helpful in software development.
Thanks for the comment. I’m just doing some reading about Kanban. I had never heard of it before Alan Shalloway’s presentation. I’ve come across the following resources:
Click to access KanbanAndScrumInfoQVersionFINAL.pdf