The product backlog is a list that contains and prioritizes the details of every little task you require to include in your product. If you want to make any changes to your product, then product backlog is the only source of requirements. A product backlog never completes; you have to work on the product backlog list continually. The product backlog continuously evolves to recognize what your product requires to be perfect, useful, and worth the competition.

The product owner is the only owner of the product backlog. When it comes to maintaining and organizing the product backlog, the product owner holds complete accountability. While ordering the backlog, the product owner may get influenced by customer priority, difficulty in relative implementation, the urgency of receiving feedback, etc. An efficient product owner will look for feedback from the development team, customers, and designers to optimize product delivery.

The Scrum Master, the Scrum Team, and other Stakeholders contribute to having a broad and complete To-Do list. You can allow other cross-functional team members to contribute items to the product backlog.

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.

These five events are:
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
The Sprint

Trust is the bedrock of self-organizing agile teams. Trust allows agile teams to communicate quickly and respond rapidly to changes as they emerge. Without sufficient trust, team members can waste effort and energy hoarding information, forming cliques, dodging blame, and covering their tracks. A climate of trust provides the foundation for effective team processes, adaptability, and high performance.

Only the Development Team can change its Sprint Backlog during a Sprint. If the Product Owner wants to change the work planned, he has to do this per the Development Team.

The Sprint Backlog is, ultimately, a plan for the Sprint. The development team executing work inside of a Sprint creates a Sprint Backlog. The creation occurs during the Sprint Planning. The central question is, how does this work get done? The Product Owner presents a list of prioritized items from the Product Backlog. The team will analyze the list, do capacity management, figure out what they can do, and make a plan to execute. The Sprint Backlog is a plan to achieve the overall goals of the Sprint.

Empiricism in Scrum is an approach whereby the team continuously learns and improves from mistakes. In Scrum, empiricism means that the team makes decisions and changes based on what the customer is experiencing, rather than what the developers intended them to experience. Additionally, the empiricism meaning in Scrum is the concept that customer feedback directly impacts the team’s actions.