Isn't that quite well in accordance of Agile Manifesto's "Responding to change over following a plan"?
Sprints and backlogs and grooming, all those sound they're straight from the Scrum Book. And while I understand that for many Scrum == Agile, actually it's not.
Note that I'm not saying anything about what's the best way to do software. Only that "responding to change" sounds very much agile.