"Focusing on behavioral changes and mental models is more important than discussing which framework is better or worse."

Yes. Each of Scrum's practices is a reminder for an issue, but there is actually a better way to address each of those issues than what Scrum prescribes!

The key is to think for yourself - don't follow someone else's workflow. E.g. yesterday in the Agile 2 Foundations class someone told me that his team was operating in a silo, so he invited some members from another team to the standup. Soon the two teams were collaborating - breaking the silo.

Now imagine that if, instead of starting with Scrum, they had asked themselves, How can we best develop this product? To answer that question, they would have realized that there are issues that extend beyond a given team. They would have thought about that issue early, and felt a sense of ownership of the issue - a sense of ownership of "how can we create this product?"

But too often, teams that follow a framework like Scrum don't start out with that attitude - they assume that Scrum "handles it somehow".