The Scrum Guide covers the Rules of Scrum, Artifacts, Commitments, Events, Accountabilities, and the Scrum Values.
Using examples from your own experience, select three topics from the list above and describe how each element you selected will help a Scrum Team become self-managing.

The Developers have decided to skip the Daily Scrum, since they are part of a self-managing Scrum Team. As a Scrum Master for the team how would you approach this?

Describe the difference between feature and component teams, and how they hold up when viewed from the perspective of the Scrum Guide.

Scrum Teams often use velocity as a technique to measure historical output.
How useful is historical velocity to a Scrum Team for predicting future velocity, even of the next Sprint?
Provide two examples of what might cause velocity to be unreliable.

As per the Scrum Guide, “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.”
Provide an example where your own experience demonstrates the meaning of the previous statement, and explicitly call out where the core areas of Scrum are demonstrated in your example.

Product Goal, Sprint Goal, and the Definition of Done are Commitments in Scrum.
What is the purpose or value of having artifact commitments in Scrum?
For each commitment, explain why it is an important part of Scrum.