> Which is why it's the product owner's responsibility to prioritise.
The company didn't seem to have issues prioritizing the authors tasks into no mans land. So they seem to have that part down great already. However I find the consistent two week deliveries early on a bit disturbing, in my experience two weeks is exactly one sprint and fixing deliverables to that time window means that you can't really do any agile planing with it, your team just has to accept that this work has to be done and can't give random work that seems to pop up every now and then the attention it deserves. To be really agile and allow your sprint planing to reflect that you shouldn't promise anything in time spans less than two months.
The whole point of agile is that you deliver something every two weeks. Whatever it is you're suggesting, it's not agile.
Delivering "something" and delivering specific items at a fixed rate are different things.
They probably said the word "agile" a lot and then continued doing something else, that seems to be the usual pattern.
> Agile is not a guarantee of deliverables you care about. There is a lot of useless stuff you can deliver.
Which is why it's the product owner's responsibility to prioritise.