During the sprint product owner and development team collaborate to understand functional requirements and value. There is no specialist in the development team; all are having a mix of skills to meet the goal. Each sprint should deliver at least one Business Functionality which has value.

During the sprint product owner and development team collaborate to understand functional requirements.
The product owner is responsible for maximizing the value of the product and the work of the development team. Value is maximised toward business objectives. If product owner is not involved then sprint may not meet the expectations.

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. Value is maximised toward business objectives.

The product owner is responsible for maximizing the value of the product and the work of the development team.
A scrum master is a servant-leader for the development team. Facilitation and removing impediments serves a team in achieving the best productivity possible.
Product owner role more towards maximize business value and the scrum master role more towards people development. Both roles have conflict in mind set.

The scrum team consists of a product owner, the development team, and a scrum master. In the review, SM is needed to facilitate the discussion. Product and development team has to collaborate to negotiate the work while keeping the business value as well. Every sprint delivers at least some business value.

Yes, the scrum master is the servant leader for the development team. Facilitation and removing impediments serves a team in achieving the best productivity possible. But it should not be considered that only scrum master is involved in removing the impediments. Sometimes the team members also involved removing impediments. The scrum master is mainly responsible for developing a productive team. Removing impediment becomes important for scrum master as it can be hindrance for a productive team.

According to the scrum guide:

The scrum master is responsible for ensuring scrum is understood and enacted. Scrum masters do this by ensuring that the scrum team adheres to scrum theory, practices, and rules.

Product owner role more towards maximize business value. The Product Owner is one person who owns the Product Vision. If the Product Owner is also doing some other work which does not directly come in maximizing the business value, he/she should be relieved from those responsibilities.

Product owner role more towards maximize business value. The Product Owner is one person who owns the Product Vision. He is one person who takes the final call what scope can be delivered in a given time frame.

Scrum Guide says: The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

The key purpose of Sprint Review is the collaboration in reviewing the product increment and to see on next items that could be done to optimize value. It is not a status meeting, and actual purpose is to elicit feedbacks and foster collaboration.

The Agile principle 11 says:
The best architecture, requirements, and designs emerge from self-organizing teams.

Scrum is suited for the complex project where requirements are abstract, and these are evolved using continuous inspect and adapt.

Scrum is a simple framework which talks about three role, four ceremonies, and three artifacts. It does not say anything about how the team members are selected for the development team. This is a process which you need to adapt as per your need.

The key reason of Daily Scrum is to know how the team is moving towards the Sprint Goal. The Development Team owns the Sprint Backlog, and all prioritization decisions are taken by them only. Development Team is self-organized to inspect the progress and to make sure they are on target to meet its Sprint Goals.

Product Owner can support for requirement clarifications if needed.

According to the scrum guide:

The scrum master is responsible for ensuring scrum is understood and enacted. Scrum masters do this by ensuring that the scrum team adheres to scrum theory, practices, and rules.

A product vision gives an ability to see the future as it communicates the goal of making the product and why you need it. It gives the answers of following questions:

• What positive changes the product will bring?
• How will it shape the future?

The product vision guide everyone involved in making the product success.

Scrum Master comes forward for facilitation whenever needed. A good facilitation is needed to make sure that goal of the meeting is achieved and the meeting is on track to meet the goal and everyone participates in some form.

Sprint Review happens at the end of Sprint, and it is four-hour time boxed meeting for one month Sprint. For shorter Sprints, the event is proportionally shorter.

Agile Manifesto has following four values:

• Individuals and Interactions Over Processes and Tools
• Working Software Over Comprehensive Documentation
• Customer Collaboration Over Contract Negotiation
• Responding to Change Over Following a Plan

To know more about Agile Manifesto, you may watch following video: https://www.youtube.com/watch?v=hwEpYnPkvNE

The Development Team selects the amount of work (stories) as per their capacity, and this work comes from the Product Backlog which is prioritized as per value. Thus, Product Owner presents stories he/she would like the Development Team to complete during the Sprint.

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.

The Sprint Planning Meeting is time-boxed to eight hours for a one-month Sprint.
For shorter Sprints, the event is proportionately shorter. For example, two-week Sprints have four-hour Sprint Planning Meetings.

Daily Scrums improve communications, eliminate other meetings, identify and remove impediments to development, highlight and promote quick decision-making, and improve the Development Team’s level of project knowledge. This is a key inspect and adapt meeting.

Scrum Master serves the Development Team by removing impediments that are getting in their way and helps to become high performing team.
Development Team is self-organized for other options.

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

According to the Scrum Guide: The purpose of the Sprint Retrospective is to:

Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, create a plan for implementing improvements to the way the Scrum Team does its work.

Only the Development Team can change its Sprint Backlog during a Sprint.

The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality.

Sprint Backlog is owned by Development Team and include all development related work.

No one wants to get late intentionally; the team is self-organized to discuss and to see what can be done for the problem team member is having.

A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so as per opinion received from the stakeholders, the Development Team, or the Scrum Master.

The product owner is responsible for maximizing the value of the product and the work of the development team. Value is maximized toward business objectives. If product owner is not involved then sprint may not meet the expectations.

The key reason of Daily Scrum is to know how the team is moving towards the Sprint Goal. The Development Team owns the Sprint Backlog, and all prioritization decisions are taken by them only. Development Team is self-organized to inspect the progress and to make sure they are on target to meet its Sprint Goals.

Product Owner can support for requirement clarifications if needed and his presence is optional.

Agile believes in the wisdom of the crowd, instead of an individual contribution. The Development Team is self-organized to meet the print Goal, and they work together by taking advantage of collective knowledge and experience.

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the Definition of “Done” as appropriate.

As a result of lessons learned while working together, team learns to collaborate. When Team is added, their environment is changed and initially productivity is likely to decrease.

Agile values more face to face communication and individual interactions. The problem is within the sprint goal, which is owned by the development team and a discussion has to be done after the daily scrum meeting as daily scrum is team synchronization meeting. It is not a detailed problem resolution meeting.