So it's hard not to explain the values of scrum (process improvement, project management framework) without sounding like a snake oil salesman to management. It happens all too often that the word scrum or agile gets thrown around with little, no, or misunderstood meaning.

One interesting misinterpretation I had used against me when arguing that the customer was taking advantage of scope and violating the simple principles of scrum's sprint framework by asking the team to take more than it had committed to. They said that I needed to be more "Agile".

What they had interpreted "Agile" as was that I needed to do more "What the customer wants".

I found an interesting article on some scrum misinterpretations (by no means a complete list, but some less common ones than i've seen) 

Now, i don't totally agree with any of these things, but what WAS interesting and I do fully agree with is this statement:

Scrum, when done properly, is wonderful.  It creates a way to learn and move forward.  When it is thought to be an answer beyond the agile project management method that it is, it can be counter-productive.  Scrum should be used appropriately and by people who understand why it works. 

This is a pretty powerful and true statement. I've seen so many misinterpretations... like "War rooming" being used to pressure developers into hurrying up (instead of for it's collaborative benefits). Or scrum meetings being used for control-freak directors (or managers or project managers) to get all of their information in one 15minute shot to the arm (instead of a meeting FOR the team members).

And i'd love to hear what scrum Misinterpretations YOU have faced in your organization :)