Know agile. Not habit. (जानामि Agile न च मे प्रवृत्तिः)

I follow  Allen Holub  in twitter and engage in some of his conversations. He believes it is possible to achieve full agility.  It does exist: SalesForce, Home Depot, Ford, Spotify, ING Bank, Zappos, Hunter, Petco, Shopify, Alaska Airlines, Tesla, Pluralsight, Peloton, even parts of IBM and Microsoft. I believe that you haven't seen it, but it's not a mirage. — Allen Holub (@allenholub) May 1, 2022 I think he is right and it is possible. Same time I also realized it is your mindset which needs to adapt to the agile working.  Let us for a moment forget the agile framework and think about business need. Change is part of life. In business too changes happen often. For a business to survive software needs to be in sync with the change to business. But the duration by which this sync should happen is different. If you consider a retail company, they do lot of sales campaigns. Their software should be ready for this campaign other wise they lose sales. But a company engaged in cons

Many times in software development, we are not able to deliver on time. Everyone in the team works hard. But the team is not able to cross the hurdle and push the product to production. Everyone is stressed and worried. At some point blame game will start.  There is a novel written by Eliyahu M Goldratt called "The Goal". It introduces you to theory of constraints (TOC). It is a good read.  Let us take Inventory concept and apply it to software development. What is inventory in software development. All the work in progress (WIP) is inventory. When you hold lot of inventory your delivery speed is reduced. This is a proven fact in manufacturing and same is true in software development. All the WIP needs integration before product is complete. When number of WIP items increase integration becomes complex and takes lot more time. Another concept of interest is bottleneck. Even in software development there is bottleneck. Usually it is resource capacity. In some cases it is speci