Myth: Scrum Master is the Key
When scrum is presented as a change in the development department, most of the time, the Scrum Master immediately is presented as the person to drive through the changes. The Scrum Master is a key player of course, but the powers of the Scrum Master is quite limited if we are looking in a bigger organizational perspective.
Some of the key elements defining the success of introducing the Scrum methodology will be outside of the scope of the Scrum Master and actually the entire development department. To address these components in the change process (like direction, strategy, prioritization, requirements process, project portfolio etc.) you really need to involve the product management in the change process.
The key to success in the introduction of Scrum is really the partnership of the Product Owner and the Scrum Master. Together they can make it work. But limiting the changes to the development department will not bring the success. There will be improvement, true, but not to the levels that actually are possible.
This all brings us to the final section. Myth or Fact? Scrum is more important than common sense!
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