There are those who seem to confuse Scrum, and the various problems that Scrum has, with Agile.
Actually, I have some sympathy here. Very often, Scrum is presented to developers as if it were an incarnation of everything Agile is. Although the distinction has been discussed and expounded on quite a lot in recent years, it's worth stating again ( and perfectly obvious to anyone who actually reads the Agile Manifesto ) :
It seems to have become fashionable of late to put Scrum down, but this is mostly just a GIGO problem - if people approach Scrum with the idea that 'if we do sprints and retrospectives a la Scrum, then we are Agile', they may be disappointed. If instead they say :
3. Scrum is an interface between Agile developers and the business.
then they will be closer to the mark.
Scrum per se is focused on deciding what work shall be done, and how that work is managed and measured, not on how an individual Agile team member works. For the purposes of product definition and product planning, Scrum formalises an interface between the business and the developers in the form of the Product Owner role. It isn't all of Agile, but it can play an important part.
Scrum is not, in fact, the only practice to use aspects of Agile. 'Extreme Programming' or 'XP' is another, which focuses a bit more on engineering practice than workflow.
© Mark de Roussier 2021, all rights reserved.