We take initiative and ask for forgiveness instead of permission.
The scrum master role is a very important part of scrum and the KSP. Although you do not stand between the team and the customer, you have a responsibility about managing expectations, tracking and reporting progress, arranging and facilitating meetings and most important of all; make sure the customer as well as the team follows the guidelines of the Kabisa Success Process.
The scrum master is the one that arranges the planning meeting and makes sure everybody is attending. Also you have a responsibility about managing expectations, as in making sure the commitment factual and the stories that are taken into the sprint planning meet the definition of ready and are actionable.
Although the scrum master is not the one facilitating this meeting, he is the one that makes sure there is a review / demo meeting. Also he should be checking with the product owner which stakeholders should be present. Inviting stakeholders is part of the job of a product owner.
This is your thing… We won’t say your life should evolve around scrum and the Kabisa Success Process but, in your role as a scrum master, you should always strive to make things better. You are facilitating and controlling this meeting and you are also the one that should make sure things actually get better and coach your team members, or request help from your KSP Captain.
In the week when there is no planning, review & retro meeting there should be a refinement meeting. Besides making sure that this meeting takes place, you should also monitor and, if its needed, report or even escalate the results.
Every day there should be a daily stand-up with the team. At least every developer that is working on the project that day should be attending, but you might also want the product owner there. The scrum master makes sure everybody follows the ground rules of the daily stand-up.
In the end, the whole success of a project heavily depends on the expectations of a customer versus the delivered results of a team. The scrum master has a role in managing expections during sprints. You should make sure the commitment that is given is reasonable and can actually be delivered. Also you should be the one to identify, handle and report impediments. When the commitment of a sprint is at risk, you should immediately report this to the product owner, but you should also make sure the impediment is handled (e.g. making sure it is handled is not the same are actually being the one that is handling it). At the daily stand-up, you should tell the team about the progress during the sprint and challenge the team about the commitment (e.g. is it stil realistic?) and report back to the product owner when its not!
For more information about (giving) commitment, see here.