Is the world of software testing changing?

Is the world of software testing changing?

In 2005 I started software testing at a Dutch bank (Postbank). They used ITIL and Waterfall and so, that was consequently our way of testing. Waterfall and ITIL were in my world for about 5 years.
Then the year 2010 started and people were more and more scoping towards an Agile way of working.

Ofcourse, Agile makes it more flexible to adjust and takes into account new insights. But when the years passed by, people fell that Agile was not perfect either (at least that was my experience and I am not the only one...).

There were days that I missed reading the specs from a good thick staple of A4's.
I hated developer A. on monday stating a requirment that was the exact opposite of the requirement that developer B. was stating on tuesday and
even worse, the product owner stating the same requirement differently on thursday.

Yeah, that's really flexible testing. My Excel tables where exploding in my head. Agile ruled (not so much).

So what is it that changes in our software testing world? People like James Bach and Michael Bolton kept writing about "A tester should do this... a tester should do that!' Blog after blog, but somehow I tended to disagree with them from time to time. I wonder why that was...(?)
(By the way: even their blogs are changing in a certain direction lately (which is a good I think)).

Could it be because REALLY GOOD software testing is only possible when a group of persons is testing in synergy? instead of 1 person following "certain  rules"? Is that what is changing?

Could it be that finally companies are realizing that there are many aspects of software testing and only if all are of a certain high quality level, that software testing works?

---