Agile can be disastrous

Don't mess up with Agile.

Agile is simple, flexible and easy to start practicing. Few teams start "custom" Agile, some other teams customize on the go!!. No documentation, change anything/anytime, no timeline commitment, small iterations. Moreover anything you find difficult, just call out as a blocker and remove it... just like that, ugh?

Business, technology, operations, everyone is happy.... Japs you are great.

Because of the above mentioned simplicity and flexibility, many teams confused with Agile practices and start wrong. Since teams run their own custom practices, different teams follow it differently. Everyone thinks what they do is right, but many follow wrong agile practices. Usually, some organizations deeply affected with these wrong practices and it is too difficult to correct. Most of the time, this happens because of no adoption strategy or unavailability of an experienced coach.

Agile Adoption Strategy

Organization should have a strategy to adopt agile and drive to maturity. Agile is going to transform the organization, so invest like any other similar project. Continuously review the improvement and validate your strategy.

Cultural transformation would be visible in different stages of adoption.

Agility : Teams bring agility in everything they do, it starts with delivering story, then improved turnaround of story, continuous deployment, unblocking, developing MVP(Minimum Viable Product),etc. Now teams start thinking in terms of speed or how quickly they could "done" something.

Reduce dependency : To bring speed, teams need to unblock themselves. They learn, not to wait for anybody or anything, instead "do it yourself". Now teams become quicker than before and have a wider knowledge in the domain.

Accountability : While teams reduce dependency and move fast, accountability becomes their mantra. Team "own" everything they do, let it be quality, performance or deployment. Now teams are ready to adopt the DevOps culture.

Continuous Improvement : In Agile, everything is iterative. Example, you build product by continuously improving it. Retrospective, it is also about thinking improvements. At this stage, team thinks about improving the current state.

If you follow Agile, then think to improve continuously ...