My Medium feed is *filled* with this.

In no small part due to the things you cite.

As others have said, there's a big difference between "we do agile" and actually being Agile, or "we do Scrum" and "being Agile".

Story pointing is a badly misused/abused system, it's well-known, and even the folks who originally evangelized it don't like what it has become.

That said, if you can't understand why estimates are important, that's a big concern. Companies need to know how much something will cost in terms of time and budget to determine ROI. Just like I can't walk into a car dealer and say "give me something 2 door, rear wheel drive, 400+ HP, and sporty" and they let me have a car and 6 years later when I am done driving it they hand me a bill for $60,000, I can't say "yeah, we're going to build this and if it takes 2 weeks or 2 months or 2 years it doesn't matter, it's done when it's done and it will cost what it will cost". Not every problem justifies the cost of the solution for it.

In addition, teams need to coordinate.

Team A: We can't build our requirement until the API that Team B is working on is done.

Team B: You'll get it when you get it.

Team A: ...

See?

Regardless how I personally feel about Agile (I think it's a fine approach for open ended product teams and any defined-end "project" is much less compatible with Agile), your analysis really seems to miss a lot... even if I agree with much of the actual points you make.

J.Ja