I'd never been exposed to this term before and yet I feel as though all the companies I worked in over the past 7 years were basically doing Scrumban unintentionally.

In the disadvantages of Scrumban, I feel as though it adopts the downfalls of both in a way. For example, 1 planning meeting might not be enough and overrides to the Kanban limits will be needed. The team deciding on their own what needs to be down also hinges on their experience, so the "no project manager" is nice philosophically but that ask ends up falling on the Product Owner—which adds a lot of weight on that role.

The way this article is laid out is quite well done. My only complaint is that it feels like you are giving an official term for something that most people were probably doing without realizing. Think of all the people that use Trello and do planning meetings. I think it would be a much stronger piece if this reality was acknowledged.