
Balian — in part 1 — clearly knows two SAFe Principles:
SAFe Principle #1: Take an economic view
SAFe Principle #2: Apply systems thinking
Then, after having built a water well, he thought that walking with pails of water from the well to the vegetation is a very manual work and time consuming. So, he developed a system to provide a constant flow of water to the vegetation and to the villagers’ houses. It is via a continuous delivery pipeline — to ‘automate’ the manual delivery of water! He applied systems thinking… and slowly optimized the system … thinking of the system as a whole… not just optimizing pieces of it without thinking of the effect of the optimization to the whole.
A lot fail because they lack a system … a continuous delivery pipeline system. Even if they have a system, they do not know how to achieve a continuous flow of value. Even if they do have a flow, they do not know how to manage it… they clog the system… and it stops working. They are not aware of SAFe Principle #6: Visualize and limit work in process (WIP), reduce batch sizes, and manage queue lengths’. Yup, small batch size promotes flow; large batch size clogs and inhibits / stops flow.
To be continued… part III: The Continuous Delivery Pipeline in SAFe !
October 15, 2022: My new book, “SAFe Is Like …“, is now available on Amazon.
What our students think about the Lean Agile Guru (“Author of SAFe is Like …“) — click here
You will get a FREE SIGNED COPY if/when you register, pay, and complete a class by the Lean Agile Guru.

