Scrum is a prescriptive approach which formally imposes processes (mainly in terms of events, roles, and artifacts) to be created, deleted and modified. The Scrum Master must cause these changes.

1- The constitution and management of teams:

  • The number of people in the team
  • The composition of the team
  • Moreno's sociogram
  • Encourage the team in its quest for improvement
  • Manage the team by trusting it
  • Focus on the “why”

2- The product vision:
The Product Owner can take operational decisions in complete autonomy and they will be respected
only if his/her vision for the product is widely shared by decision-makers in the organization.

3- Establish a strategy:
Remember, to help the organization better adopt Scrum, you use the same practices as the Product Owner. So you need to identify goals and have a vision.
Ask yourself the following question:

  • Why is this organization seeking to adopt Scrum?"
  • Why not Kanban or SAFe?
  • What goal is the organization trying to achieve?

4- Proceed step by step:
Ideally, the Scrum Master should have performance indicators, accepted as reliable and representative
by the majority of stakeholders, from the start of its mission. If not, then create them as quickly as possible and make sure there is consensus. It is only on the basis of these indicators that the Scrum Master will be able to inspect and adapt his planning for the deployment of Scrum.

5- Follow up regularly