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.

Value is likely to vary across products and organizations.

All Scrum Team members together compose the Sprint Goal during the Sprint Planning.

The main purpose of Daily Scrum is synchronization of the Developers.

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.

Product Owner is a functional position.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists.

The Product Backlog is a living artifact which is continually kept up to date with the most recent insights.

All Scrum events are necessary; they should never be removed.

Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.

As stated in the Scrum Guide, the Product Backlog is an ordered list. This means that the ordering has a logical sequence. The Product Owner orders the Product Backlog to maximize the flow of value. value is only one attribute to take into consideration when ordering the Product Backlog items. Others may include software dependencies, other items in the Product Backlog, availability of the team members, skillset and level of expertise, other products, urgency, size, etc. For example, if a high priority item depends on a lower priority item. Then the lower priority item would be ordered higher.

Lessons learned are always captured but the main purpose of Sprint Retrospective is capturing and planning for lessons learned.