The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.

A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.

The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.

Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.

In Scrum, the responsibilities related to the product are collective. There are no leaders.

The Scrum Team is responsible for all product-related activities

The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute time-box.

The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

What is a Daily Scrum?

Daily Scrum is a daily 15-minute time-boxed meeting in the Scrum framework where Developers briefly share their progress and plans for the day. The goal of Daily Scrum is to ensure that everyone is aligned on the goals of the Sprint, identify and address any obstacles, and improve communication and collaboration among the Developers.

It's rather the Kanban board (or other techniques) that helps the Scrum Team track the open work during a Sprint and identifies undone work that can be addressed in a separate Sprint.

The Scrum Guide™ of 2020 says :

" The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

The moment a Product Backlog item meets the Definition of Done, an Increment is born.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.

If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. "

If the team doesn't invest enough in Product Backlog refinement the Sprint Planning can take longer as the Product Backlog Items lack information such as description and estimation. The Scrum Team is therefore less likely to forecast the necessary work to deliver a valuable and usable increment that meets the Definition of Done.

The defect is from the work performed in the current Sprint.

Remember: 1 Product = 1 Product Owner = 1 Product Backlog.

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work.

In Scrum, the Scrum Team is allowed to interact with key stakeholders any time where it's valuable to have their input. The Scrum framework encourages regular communication and collaboration between the Scrum Team and key stakeholders to ensure that the product being developed meets their needs and expectations.

The Product Owner is responsible for engaging with stakeholders to gather feedback, clarify requirements, and prioritize the Product Backlog. The Developers may also interact with stakeholders to gain a better understanding of the product and ensure that the work being done aligns with the stakeholder's needs.

The Scrum framework provides several opportunities for stakeholders to provide input, including Sprint Reviews, Sprint Retrospectives, and Product Backlog Refinement sessions. However, stakeholders can also be engaged outside of these events if it's deemed necessary or valuable to the project. Ultimately, the Scrum Team should work collaboratively with key stakeholders throughout the project to ensure the success of the product.