This is more a large human organisations thing.

The author makes it clickbaitier by not counting meetings and pointless work as "work".

Once you add those back in then it's basically repeating Dilbert from decades ago.

Agile itself was introduced because large million dollar projects were stalling out and getting cancelled before deploying (or even writing) a single line of code.

Last year I started my first full time job as a front end web developer, I have a fair workload, learning a lot, and enjoying the work.

Is it actually common for devs to have no work to do and be bored? If so could it be the reason behind all the layoffs?