Many other industries are eyeing on how to harvest such benefits of Scrum in their context. Let's take a step back - PRINCE2 was originated for IT projects, PMBoK was initially meant for construction projects Now many non-IT, non-construction industries are using them.
Scrum is a Framework
Virtually all industries are able adopt Scrum without having to make it industry-neutral. Scrum is a framework and not a methodology. Allow us to have quick look on their differences.
Framework - it outlines the principles and generally answer "Why & How" and often challenges status quo.
- Why we need lengthy meetings? How to make meeting value-add to client?
- Why client not satisfy with our hard works? How to increase client satisfaction the simplest way?
- Why team are not performing? How to make the team self-organized?
Methodology - it prescribes the working mechanisms of an activity/ deliverable, i.e. "What" need to to be done by "Who" via "How" approach in the timing of "When".
- What are needed in a Project Charter? Who is responsible to create/ review/ approve it? When it is needed before next activity can start?
As a framework, it must be accepted as a whole. Any changes on it, may invite chaos if not catastrophe. When the Scrum framework is adhered, you can come out your own working mechanism based on your preferences.
Just like a house - its framework is solid foundation of everything in it, which make the occupants comfortable living in it. You can decorate it without worrying its safety. Any removal of the framework entails unexpected risks.
When you are planning to introduce Scrum in your team/ organization, it will be better to have someone knowledgeable in Scrum to be on your side. This is to ensure the Scrum framework is maintained and not omitted.
On the other side, if your Scrum does not deliver expected benefits, you may want to consider to re-inspect its framework. Hopefully after the inspection, you can restore the framework and reap its intended benefits.
Have fun decorating your Scrum framework.