Writing about Scrum, regardless if it's praise, complaints, references, howtos or just plain descriptions without referencing the agile manifesto is kinda... missing the point? The content of the article is good, but perhaps quoting the founding principles of agile would make it even better? Implementing Scrum (including org-specific adaptations) without understanding the idea behind 'agile' is what a PHB does.
This. Scrum is just a way of operationalizing the basic principles behind the Agile Manifesto while putting them in a way that can be communicated and understood outside of dev/product organizations. No Scrum Master/Agile Coach/Product Owner, etc. worth his/her salt will tell you to slavishly stick to every piece of Scrum as long as you get the basics (see the manifesto) right.
It is, however, a somewhat useful tool for helping you get this running in the first place (especially in organizations where there is a lot of chaos to begin with, i.e., upper management regularly changing the product scope and release timeline based on the color of their coffees, etc.).
> Scrum is just a way of operationalizing the basic principles behind the Agile Manifesto while putting them in a way that can be communicated and understood outside of dev/product organizations.
Scrum in practice is processes and tools over individuals and interactions.
> No Scrum Master/Agile Coach/Product Owner, etc. worth his/her salt will tell you to slavishly stick to every piece of Scrum as long as you get the basics (see the manifesto) right.
https://agilemanifesto.org/