Yes, Scrum violates the first value: “Individuals and Interactions over processes and tools”: By not being able to say “but”, one is locked into the Scrum process — whether it works well for them or not! The Scrum community is arrogant and insists that if Scrum is not working for you, then you must not be doing it right. They shun “Scrum but” — i.e., they insist that you stick to the process — violating an important Agile value.

Scrum stole Agile, and almost destroyed it. Organizations found that Scrum does not scale, and to use it one must insert a whole raft of additional things. The worst parta are that (1) Scrum breeds inflexibility, and (2) Scrum shifts the attention to things that don’t actually matter that much — things like how the standup is done, story size, retro format, etc. These things matter a little, but not a-lot; other things — such as how and when integration tests are done — matter hugely more. But Scrum Masters ignore technical practices such as how integration tests are done, or how coverage of those is managed, or how and when merges affecting multiple repos happens, and so many other things. The result is that Scrum teams tend to underperform because their de-facto leader — the Scrum Master — steers conversation toward touchy-feely topics instead of the topics that affect quality and speed.

It took DevOps to save Agile. And by the way, the Behavior-Driven Development (BDD) process does not fit well into Scrum: BDD is an inherent sequential workflow, which Scrum is not. Agile teams would be better off saying goodbye to Scrum and thinking for themselves.