Sprints are the Scrum equivalent of an Agile iteration, which is a short period in which a team works to produce an end deliverable.

Within each sprint, there are Scrum inspect and adapt events, also known as ceremonies. These events or meetings are specifically designed to enable critical transparency and inspection.

There are four Scrum inspect and adapt events:

• Sprint Planning
• Daily Scrum (Daily Standup)
• Sprint Review
• Sprint Retrospective

Scrum events create an empirical behavior amongst teams if done in the right spirit. The Scrum Master should ensure the team understands each event's why what, and how. These events also help to create a flow of communication and provide transparency at every level.

Sprint planning is a collaborative effort involving a ScrumMaster, who facilitates the meeting, a Product Owner, who clarifies the details of the product backlog items and their respective acceptance criteria, and the Entire Agile Team, who define the work and effort necessary to meet their sprint commitment.

A stakeholder is "a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.

The Scrum Master ensures that the meeting happens, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches them to keep the Daily Scrum within the 15-minute time-box.
The Daily Scrum is an internal meeting for the Scrum Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

The daily scrum is designed for the team to coordinate and adapt its progress within the sprint. At a minimum, the product team should be in attendance. Typically, the invite list should also include the product manager and scrum master or delivery manager.
Although stakeholders and others outside of the team are generally welcome to attend, the intended audience is the team. Any attendees outside of the team should be observers only.

Attendance is not limited to the Scrum Team. When it’s needed, for example, for refinement, the Scrum Team can invite SMEs to provide additional information. This could also include users, the client, or any other stakeholder. This makes the event more engaging, as well as shows you value the opinion of others.