A colleague and Lean-Master at a large financial institution gave me a copy of Lean Kaizen: A Simplified Approach to Process Improvements by George Alukai & Anthony Manos. More than anything else, this book drove home to me the similarities and differences between Scrum and Lean (at least Lean, outside of Software Development).
‘The heart of Lean is the Kaizen Process.’ Kaizen means ’change for the better’ and is loosely translated at Continuous Improvement. This is actually a misleading translation, because Kaizen does not imply an iterative repeated process.
The core Kaizen event is nothing else than a Scrum Retrospective. In fact, the descriptions of how to run the meetings are so similar, I suspect they have a common source.
Two differences become quickly apparent:
By following the approach in this book, one group might get 6 Kaizen events per year, but probably more like one to two, because of the effort involved.
The more subtle difference is that management organizes & choreographs the process. The advantage of the Lean approach is that management is more committed making the suggestions happen. I have experienced that this can be a problem for Scrum teams…
Under Scrum, each team sends a filtered, prioritized list of improvements, usually one or two top issues to management after every sprint. When management supports the Scrum teams, wonders can happen. Would you like to be one of the companies which discovered ‘we got more lean doing 6 months of Scrum than doing 3 years of lean with traditional management’?
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|mailchimp_landing_site||1 month||The cookie is set by MailChimp to record which page the user first visited.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_42152348_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|NID||6 months||NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|COMPASS||1 hour||No description|
|cookies.js||session||No description available.|
|S||1 hour||No description available.|
I don't agree on your last sentence.
Lean methodology prone to remove everything that is not needed or, depending where you come from, to optimize the flow of production.
IMHO Scrum aims at giving release of softwares at every release, it has nothing to do with lean.
Moreover, Knaban doesn't necessarily involve an heavy change in project management. So, if the firm isn't really involved in, it won't change anything from the outside point-of-view.
As Scrum have a global vocabulary and special artifacts, its changes are more visible from the outside. It's like if you decide to get CMMI approval or to move on the RUP, you'll have significant changes, very visible.
(This is not very clear, but the idea lies somewhere)
IMHO the focus of Scrum is on identifying organizational dysfunction. Make the problem visible, then you can deal with it.
"Lean Software Development" is so far removed from what, say, the Lean Management Institute, would tell you about Lean that it's not funny. I would call Kanban an Agile Framework that draws heavily on Lean Principles. And even Kanban can cause real conflict with management.
You right about one thing though: Scrum does not give you VSD's and the many tools of Lean. It does apply the principles consistently (if less explicitly in some cases than Kanban).
Still, I have seen enough companies unable to break out of their sclerosis using top down "lean" management. I have watched these same companies make tremendous progress in just 6 months doing Scrum.
So I am convinced that if you set out to do Lean, and use Scrum as your means to accomplish that goal, you will be far more effective than if you just apply Lean Principles and Tools using traditional management practices.