Myth: Scrum is more important than common sense
Well to be honest, no one actually suggests this, but in some cases (remarkably often) we actually have to go back and ask ourselves why we do things.
The problem normally comes from the fact that a new and inexperienced organization can act confused in a situation of change and dogmatically cling to irrelevant fragments of wisdom (or belief) simply because they can’t tell that it is irrelevant. (Or no one actually is willing to take the responsibility for saying it.)
Never ever should anything be adopted in a way that is counter-productive to the real goal which is to improve effectiveness! And we must also remember that Scrum is a framework. It gives us tools, but we need to figure out how they should be applied in our environment.
We must however also be able to motivate the deviations we do. The similar pitfall on the other end of the scale is that we don’t adopt to the things in Scrum that actually will affect our organization (cheating in the change process) and thus will not get any improvement at all.
Just use common sense and ask the simple questions: Why does Scrum want us to do this? Are we achieving that goal?
1. Fact: Scrum is not a project methodology 2. Fact: Scrum is not a development issue 3. Big Question: Where will the improvement come from? 4. Fact: Scrum does not remove all problems in an organization. 5. Myth: The Scrum Master is key 6. Myth: Scrum is more important than common sense