TKB 15: Scrum vs Lean
Scrum is a lightweight agile framework for product development. It is a simple framework to understand with three pillars of empiricism and five values. You can adopt it as it is without much hard thinking if you are satisfied with the output. One thing to be alert about while using such frameworks is not just ending up on the physical process without gaining the underlying output that this framework demands. Scrum calls it “Mechanical Scrum” where you do all the ceremonies but the output is not there.
Lean is focused on reducing waste, continuous learning, and optimizing the value stream. It is primarily targeted for the manufacturing industry, but its rules are so universal that it can be applied to software development as well. Lean is more open, and its focus is only on the one goal that your organization as a whole has decided. Any other work that directly or indirectly does not affect this goal is a waste. You have to abolish local efficiency as that is a bigger trap that engages us in non-priority tasks first, then the higher priority ones.
Anytime we deal with a framework, we must recognize that it is preconfigured based on general needs. It's like playing with Lego pieces; the bigger ones reduce flexibility but allow for faster progress compared to the smaller pieces, which require more dedication. This is a good way to start, as we get a proven technique to initiate the work.
Most agile frameworks do come with their principles (by inheriting 12 principles from Agile Manifesto ) and core values. This is a reminder for us by the creator that what they developed is based on these principles as per universal needs. You are free to anytime tailor the framework and add your own artifact in the process.
If you follow the Scrum framework and have a Lean mindset, that may give you the best of both. After learning and applying the framework, you end up looking through the framework and its output while still thinking about how you can go further than this. Lean will allow you to find new constraints and overcome them to improve efficiency.
It reminds us of the famous Japanese concept Shuhari, which describes the stages of learning and mastery. First, you obey(Shu-) the framework as it is, then you break(ha-) the framework by adding your artifact as per your organization's needs, and then you leave(ri) it by creating your framework. The last step is where the magic happens as you realize how that core values and principles are taking shape in a given environment.
If Scrum is a framework meant to be broken, then Lean is a driver that can tell us the direction to break it. In the end, it is just your goal and your process to achieve what matters. Along the way, you leverage the minds of people who have already solved the problem at one level.