I often come across the question “Whats the difference between agile and lean, and how are they similar”. Big question!
There is an ongoing debate on the relationship of lean and agile methods and philosophies. Lean arose from Japanese production and is based on the two ‘pillars’ of continuous improvement and respect for people. It aims for elimination of waste, continuous, even flow and constant learning and striving for perfection (read innovation here). Agile arose from software development and focuses on emergent design, incremental delivery and continuous and disciplined planning. While lean has been highly developed for repeatable production tasks according to a preconceived design, it has also proved highly effective in development tasks where it aims to ‘outlearn the competition’. Agile has been used in development to create new designs and, as the name suggests, is specifically about change rather than repeatability.
These quite different lineages have been used to justify the stance that lean and agile are quite different approaches, and that even though Lean is now being applied to software development, they are mutually exclusive:
Kent Beck – “The values, principles, and practices of the two approaches are different, even though complementary.”
A contrary view is, however, emerging. Mary Poppendeick reflects the view that agile methods are an implementation of the lean philosophy in software development. Her seminal book “Lean Software Development: An Agile Toolkit” which first defined the lean approach to software development, reflects this in its title. This view is described well by Dean Leffingwell:
“I’ve been struck again and again by common principles – not just like principles or complementary principles – but virtually identical, fundamental, and immutable principles that provide the cornerstone values and philosophies of both lean and agile approaches. I’ve become more and more convinced that agile is a software instance of lean– purpose built for the unique challenges, intangibles and thought-based work of developing software as fast as efficiently as possible – but as lean as lean can be in that context.”
As this debate develops I hope to write a series of blogs exploring the issues and the debate, and do some ‘future-gazing’ as to how the emergence of lean will influence the evolution of agile development.
- Team Primer in Agile and Scrum (2 day)
- Team Primer in Lean and Kanban (2 day)
- Agile – Executive Briefing
- Leading a Lean/Agile Transformation (2 days)
- Preparation for ScrumMaster Certification with Scrum.org (2 day)
- Preparation for Product Owner certification with Scrum.org (2 day)
- SAFe® 4.0 for Teams with SP Certification
- Leading SAFe 4.0 with SA Certification
- SAFe® 4.0 Scrum Master with SSM Certification
- SAFe® 4.0 Advanced Scrum Master with SASM Certification
- SAFe® 4.0 Product Manager/Product Owner with PMPO Certification
- Agile Testing (2 day)
- Scaling Agile in the Enterprise – (3 days)
- no upcoming events