One of the problems with Scrum is that it describes something close to a process (Plan > Dailys > Review > Retro > Repeat), while the Agile Manifesto states 'Individuals and interactions over processes and tools'.

On the one hand, it is the reason why Scrum is so successful in corporate environments, on the other hand it is also somewhat non-agile. That is why I tend to call Scrum the least agile Agile Methodology and a good starting point for Agile transformations.

Just don't forget to keep moving on as your Retros lead you the way.